A Skill is a repeatable procedure: a goal, the steps to get there, the examples that show "good", and the checks that catch bad. Skill Forge is where you build them — not as one-shot prompts, but as small packages that hold up across runs and across colleagues.
A single prompt is fragile. A Skill Package separates the instructions from theexamples from the checks, so each piece can be improved without breaking the others.
What's inside a Skill
Instructions
The procedure, in your words: what to do, in what order, and what good looks like.
Examples
Real before/after pairs. The single biggest lever on output quality.
Checks
The handful of things that must be true before the output is acceptable.
Notes for future-you
What you learned the hard way so you don't learn it again.
How to forge one
Start from a real run
Pick a task you've already done well in the Composer or Lab. Skills crystallise existing wins, they don't invent new ones.
Let Forge draft the package
Skill Forge streams a first draft of all the files. Read them, don't just accept them.
Add 2–3 strong examples
One good example beats five weak ones. Pick the runs you'd be happy to show a colleague.
Write the checks
Two or three is enough. "Tone matches our brand", "all numbers cross-check", "no client name left in".
Test, then save to the Library
Run the Skill on a fresh task. If it holds, save it. If not, edit the file that broke — not the whole thing.
Skills are powerful when shared, but they carry your standards. Before you gift a Skill to a colleague or your org, run it once more on a fresh example.