SKILL.md
SkillForge
Create well-formed Skills quickly and consistently.
Workflow
- Restate the spec
- What problem does the skill solve? - Who/what will use it (Codex, Claude Code, humans)? - What inputs does it take and what outputs does it produce? - What is explicitly out of scope?
- Pick the skill type
- operational: narrowly-scoped, repeatable procedure (preferred default). - meta: orchestration / governance / decision-making. - composed: "manager" skills that chain other skills together.
- Name the skill
- kebab-case, short, verb-led if possible. - One responsibility per skill.
- Create the skill folder
- Recommended (project skills): skills/<type>/<name>/ - Optional (kit skills): forgeloop/skills/<type>/<name>/ only when you are changing the kit itself - Required: SKILL.md - Optional: scripts/, references/, assets/
- Write
SKILL.md
- Frontmatter: name + description only. - The description is the trigger surface: include what it does + when to use it. - Body: concise steps + crisp examples; link large details into references/.
- Sync skills into your agents
- After adding/updating skills, run: - ./forgeloop/bin/sync-skills.sh (Claude Code mirror + optional Codex install)
Minimal SKILL.md skeleton
---
name: your-skill-name
description: "What it does. Use when … (include triggers)."
---
# Your Skill Name
## Inputs
- …
## Outputs
- …
## Steps
1. …
## Examples
- …Guardrails
- Prefer small, reversible changes.
- Do not "over-forge": only create a new skill when it will be reused or it meaningfully reduces future context.