agentleFS
Sign inStart free
cwinvestmentscwinvestments/memstack/skills/forge/SKILL.md

forge

Skill425 starsChanged 5 months agoMITView on GitHub

Use when the user says 'forge this', 'new skill', 'create enchantment', or wants to create a MemStack skill.

78 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use forge-ship, forge-review and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • redteamlifeSkill

    forge-ship

    Use when the user asks to merge, release, promote, reconcile, or close out work in a repo containing `docs/forge/` or governed by FORGE. Not for per-task commits; those complete inside forge-execute-task.

    Also in 6 projects that use this

  • tonmoy007Skill

    forge-review

    Run a multi-dimensional parallel code review over the current change.

    Also in 8 projects that use this

  • weselbenSkill

    forge-docs

    Load before code changes, before writing docs or an ADR, when a user question exposes a missing how-to, and when closing a chunk of work; also loaded by forge after each squash-merge and by deep-research after a report.

    Also in 3 projects that use this

  • DailenGSkill

    forge-design

    Design, UX, and polish discipline for the forge lifecycle. Covers the design tier, the design brief in docs/DESIGN.md, UX requirements and their verification methods, the per-slice design pass, the UX defect register, and the release polish pass. Load whenever work touches a user-facing surface (GUI, terminal, library API, or operated service), whenever a UX observation needs disposing of, and whenever a release is in reach.

    Also in 3 projects that use this

  • DshamirSkill

    forge-plan

    Takes analysis.json + budget cap → derives the full phase sequence, hyperparameters, instance type, cost estimate, and acceptance thresholds. Emits plan.md (the single human gate document) and plan.json (the machine-readable spec that dispatch-v2 consumes). Refuses to plan if estimated cost exceeds budget×1.2.

    Also in 4 projects that use this

  • tonmoy007Skill

    forge-build

    Run Stage 6 of the Forge pipeline — implementation. Use when the user says

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 67 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill activates, output:

    line 13
  2. Very specific:

    Update MEMSTACK.md: add a new row to the Skill Index table

    line 39

“Common” is measured: kept by at least 6 in 10 of the 67 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

🔨 Forge: Creating New Enchantment...

Create new MemStack skills or improve existing ones.

Activation

When this skill activates, output:

🔨 Forge: Creating new enchantment...

Then execute the protocol below.

Protocol

Creating a new skill:

  1. Ask the user:
    • What should the skill do?
    • What trigger keywords should activate it?
    • What inputs does it need? What should it output?
  2. Generate the skill file with v2.1 format:
    • YAML frontmatter with name and description ("MUST use when..." format)
    • Activation message (pick an appropriate emoji)
    • Context guard (if the skill could have false positives)
    • Protocol steps
    • Inputs/Outputs
    • Example usage
    • Level history starting at Lv.1
  3. Write the file to $MEMSTACK_PATH/skills/{name}.md
  4. Update MEMSTACK.md: add a new row to the Skill Index table
  5. Confirm creation: show the skill summary

Improving an existing skill:

  1. Read the current skill file
  2. Apply improvements based on user feedback
  3. Increment the level in Level History
  4. Update the file

Inputs

  • Skill concept description, trigger keywords, desired behavior

Outputs

  • New skill .md file in skills/
  • Updated MEMSTACK.md index

Example Usage

User: "forge a new skill called Beacon for health check pinging"

🔨 Forge: Creating new enchantment...

Creating: Beacon
Emoji: 🔔 | Type: Passive | Triggers: "health check", "ping", "uptime"

Writing: skills/beacon.md ✓
Updating: MEMSTACK.md: added row #N ✓

Beacon is ready. Triggers: "health check", "ping", "uptime"

Level History

  • Lv.1: Base: Skill file generation and index updates. (Origin: MemStack v1.0, Feb 2026)
  • Lv.2: Enhanced: Added YAML frontmatter, v2.1 format generation, level tracking. (Origin: MemStack v2.0 MemoryCore merge, Feb 2026)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free