write-great-skill

Workflow + quality bar for skills and agent-loaded docs. Project CLAUDE.md/AGENTS.md may add rules (eval prompt language, commit style, post-ship steps); project wins on conflict.

Eval rules

• Ship evals/evals.json per skill-creator schema; fixtures under evals/files/, built by script (init.sh, gen_fixtures.py) once beyond a handful of files, so every run starts from identical state.
• Cover every branch and guardrail with ≥1 eval with checkable expectations.
• Aim expectations at what skill adds: behavior model misses without it, observable in output files or run's action log. Eval passing both ways stays only as regression guard, marked so in benchmark.md.
• ≥1 eval triggers skill in natural language, no /<skill> command.
• Update evals in same change that alters behavior.
• Record every run in evals/benchmark.md (format). Doubles as baseline cache: no-skill scores depend only on eval prompt, fixtures, model, never on skill text.

Gates