agentleFS
MetalLegBobMetalLegBob/solana-vibes-kit/forge/SKILL.md

Forge

Skill19 starsChanged 9 months agoMITView on GitHub

Forge: SVK Skill Builder. A 5-phase pipeline for building SVK skills with automated convention enforcement and shipping checklist validation. Run /Forge:brainstorm to start designing a new skill.

79 other projects use a version of this.

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

  • Other versions79 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 79

    1. cwinvestments/memstack★ 425same name
    2. ansari-project/codev★ 298same name
    3. cluesmith/codev★ 298same name
    4. swyxio/skills★ 194same name
    5. simota/agent-skills★ 96same name
    6. alp82/forge★ 36same name
    7. TT-Wang/forge★ 34same name
    8. emiliosheinz/agent-skills★ 20same name
    9. kecoma1/MQL5-SKILLS★ 17same name
    10. yz5e/agent-skills★ 17same name

    69 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Look for .claude/svk-meta.json in the current project.

    line 25
  2. Very specific:

    Read the svk_repo path and installed_version from the metadata file.

    line 26
  3. Very specific:

    Run: git -C <svk_repo> tag --sort=-v:refname | head -1 to get the latest tag.

    line 28
  4. Distinctive:

    If they match, skip — the user is up to date.

    line 30
  5. Distinctive:

    If the latest tag is newer, show this message ONCE (never repeat in this session):

    line 31
  6. Distinctive:

    If the git commands fail (offline, repo moved, etc.), skip silently.

    line 37
  7. Distinctive:

    Important: Do NOT block or delay the user's actual command.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 68 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
<!-- SVK Version Check — runs once per session on first skill invocation --><svk-version-check> **On first invocation this session**, silently perform a version check:
  1. Look for .claude/svk-meta.json in the current project. If it doesn't exist, skip this check entirely.
  2. Read the svk_repo path and installed_version from the metadata file.
  3. Run: git -C <svk_repo> fetch --tags --quiet 2>/dev/null
  4. Run: git -C <svk_repo> tag --sort=-v:refname | head -1 to get the latest tag.
  5. Compare the installed version against the latest tag (strip the leading v).
  6. If they match, skip — the user is up to date.
  7. If the latest tag is newer, show this message ONCE (never repeat in this session):

SVK Update Available: v{latest} is available (you're on v{installed}).

  • Update now: I can pull and reinstall the changed skills in this session
  • Update later: Start a new chat and run /SVK:update
  1. If the git commands fail (offline, repo moved, etc.), skip silently. Never show errors from version checking.

Important: Do NOT block or delay the user's actual command. Perform this check, show the notification if needed, then proceed with the command they invoked. </svk-version-check>

Forge — SVK Skill Builder

A meta-skill for building SVK skills. Wraps Superpowers skills with SVK-specific context injection and enforces a 21-item shipping checklist.

Commands

CommandDescription
/Forge:brainstormPhase 1 — Design a new skill (wraps superpowers:brainstorming)
/Forge:planPhase 2 — Write implementation plan (wraps superpowers:writing-plans)
/Forge:buildPhase 3 — Execute the plan with scaffolding (wraps superpowers:executing-plans)
/Forge:validatePhase 4 — Two-pass validation against shipping checklist
/Forge:shipPhase 5 — Commit, test install, and clean up

Pipeline

/Forge:brainstorm → /Forge:plan → /Forge:build → /Forge:validate → /Forge:ship

Each phase is a separate command. You can enter at any phase if you already have the prerequisite artifacts (e.g., skip brainstorm if you have a design doc). Validate and ship enforce the full checklist regardless.

Resources

Load resources from resources/INDEX.md when needed — don't read them all upfront.

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.