create-skilllisted
Install: claude install-skill vanducng/skills
# create-skill
A skill is a conditional prompt fragment: it costs context on every load and earns its place only by beating the base model. Proof is a pass rate.
## The bar
Say yes to all four or stop, and say so. Not writing a skill is a valid, common answer.
1. It recurs. 2. The base model gets it wrong unaided. 3. You can quote the phrases a user types for it. 4. It is narrow enough for firm rules.
## Rules
1. **Evals first.** Write `evals/` before `SKILL.md`: 3 or more scenarios, each with `prompt.md`, an optional `fixture/` and a deterministic `checks.sh` (exit 0 = pass, no judge model), and at least one clean case the skill must leave alone (`scenario.json`: `{"clean": true}`). Format: `references/eval-format.md`.
2. **Prove it fails.** Run each scenario without the skill. A non-clean scenario the base model already passes tests nothing: harden or drop it.
3. **Short body.** About 500 words, never past 800; depth goes in `references/`. The description is the router: what it does, the literal trigger phrases, up to 1024 characters.
4. **Fragile steps are scripts,** and the skill says when to run them.
5. **Fix at the highest layer.** Architecture, then types, then a script or lint, then a test, then prose last. Prose rules are the first thing dropped under load.
6. **Twice, not once.** Promote a failure to a rule or check after two evidence rows of the same class. One failure is a note: change nothing.
7. **A promoted check ships with the case it would have caught,