| name | skill-forge |
| description | Use when the user asks to forge, scaffold, author, or ship a new skill or agent — the skill-creator's own namesake artifacts. Drives the skill-forge loop (create → fill → validate → critique → ship → publish) via the skill-creator CLI. |
| description-frequency | on-demand |
| user-invocable | true |
| version | 1.0.0 |
| format | 2025-10-02T00:00:00.000Z |
| triggers | ["the user asks to create, scaffold, or author a new skill or agent","the user wants to ship or publish a skill through its quality gates"] |
| updated | 2026-07-12T00:00:00.000Z |
| status | ACTIVE |
Skill Forge
Forge a new skill or agent end-to-end using the skill-creator
CLI. The forge is the toolchain that scaffolds, validates, and
ships skills and agents; this skill is the playbook that drives it.
When to invoke
Trigger on any of:
- "create a skill for X" / "author a new skill"
- "scaffold a skill" / "make me a skill that …"
- "add an agent" / "author a subagent for X"
- "ship this skill" / "run the skill through its gates"
Do not trigger for:
- Editing an existing skill's guidance — that is
skill-creator refine <name> (corrections, not a new artifact).
- Retiring a skill — that is
skill-creator skill retire <name>
(suggest-first, reversible).
- Forging a cartridge (content / department / chipset bundle) —
that is the
cartridge-forge skill.
Prerequisites
docs/SKILL-FORMAT.md is the normative frontmatter/format
reference; docs/skill-authoring/skill-md-quality-checks.md
lists the hard defects the gate rejects; docs/authoring-tools.md
maps the CLI surface. Read them once per session if the context
is not already loaded.- Pick the slug (kebab-case, matches the skill
name:). Keep it
specific — the description and triggers must not collide with an
existing skill's activation.
- Decide skill vs agent. A skill is auto-loading guidance
(a
SKILL.md); an agent is a delegated subagent with its own
tool set (an agents/<name>.md). Author the one the task needs.
The Forge Loop
create → fill → validate → critique → ship → publish
Every step is idempotent. skill ship is the gate — if it exits
non-zero, the skill is not ready to publish.
1. Create
skill-creator create
The wizard scaffolds a spec-valid SKILL.md: repo-canonical
frontmatter (version / format / status: ACTIVE) plus a body
seeded from a template preset (workflow-guide / reference /
checklist) rather than a blank prompt. It prints a
Next: validate → critique → ship footer.
For an agent instead of a skill:
skill-creator agents create --name=<slug> --description="…"
