agentleFS
Sign inStart free
shivae372shivae372/claude-bootstrap/.claude/skills/forge/SKILL.md

forge

Skill1 starsChanged 7 months agoApache-2.0View on GitHub

Authors a NEW, project-specific Claude Code skill from scratch when the ecosystem has nothing that fits. Use after `augment` finds no good match, or when the user wants a custom workflow captured as a reusable skill. Produces a detailed, validated skill — never a generic stub. Triggers: 'make a skill for…', 'turn this into a skill', 'I keep doing X, automate it'.

78 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 9 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

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

  • 0

    Common

    Most of the 67 edited versions we read keep these.

  • 3

    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. Distinctive:

    Before writing anything, learn how this project actually does the thing:

    line 19
  2. Very specific:

    Read the relevant files (configs, scripts in package.json/Makefile/pyproject, existing patterns).

    line 20
  3. Very specific:

    If the skill needs a helper, write it into scripts/ and call it from the steps.

    line 42
  4. Distinctive:

    Run the new skill once on a real (safe) case to confirm it works.

    line 51
  5. Distinctive:

    Never ship a skill that still contains skeleton placeholders (the validator blocks this).

    line 62
  6. Very specific:

    Keep the body lean; push detail into references/.

    line 64

“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

Purpose

Capture a capability as a durable, high-quality skill tailored to THIS codebase. The deterministic scaffolder guarantees structure and validity; you supply the real, specific substance. A generic skill is a failed skill.

When to use this

  • augment searched the ecosystem and nothing good fit.
  • The user has a repeatable, project-specific workflow worth making one-command.

Steps

1. Understand the task deeply FIRST

Before writing anything, learn how this project actually does the thing:

  • Read the relevant files (configs, scripts in package.json/Makefile/pyproject, existing patterns). Use the explorer agent for big repos.
  • Identify the EXACT commands, file paths, env vars, and success checks involved. Specificity here is the whole point.

2. Scaffold a valid skeleton

python3 .claude/engine/skill_forge.py scaffold \
  --name <kebab-name> \
  --description "<what it does> + Use when <concrete triggers>" \
  --allowed-tools "Bash, Read"

This writes .claude/skills/<name>/SKILL.md with the right frontmatter and the section skeleton (Purpose / When to use / Steps / Output / Guardrails / References), plus scripts/ and references/ dirs.

3. Fill it with REAL detail (replace every placeholder)

Edit the SKILL.md so the Steps are the actual procedure for this project:

  • Real commands with the real flags (pnpm test --filter web, fly deploy --remote-only…).
  • Real file paths and expected outputs.
  • A concrete success check and explicit guardrails (what it must never do).
  • Long reference material → drop into references/ and link it (progressive disclosure).
  • If the skill needs a helper, write it into scripts/ and call it from the steps.

4. Validate — the quality gate

python3 .claude/engine/skill_forge.py validate .claude/skills/<name>/SKILL.md

It FAILS if placeholders remain or the body is too thin. Do not finish until it passes.

5. Prove it, then learn

Run the new skill once on a real (safe) case to confirm it works. Then record it:

echo '{"category":"workflow","text":"Forged skill <name>: <one-line what it does>","tags":["forge"]}' \
  | python3 .claude/engine/learn.py add

Output

A validated .claude/skills/<name>/SKILL.md (plus any scripts/), specific to this project, ready to auto-invoke — and a note to the user on how to trigger it.

Guardrails

  • Never ship a skill that still contains skeleton placeholders (the validator blocks this).
  • One skill = one job. If it's growing two jobs, forge two skills.
  • Keep the body lean; push detail into references/.

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