writing-skillslisted

# Writing Skills Write a skill for another agent to use under pressure. Context is a shared budget, so every paragraph must earn its place. ## Design the boundary 1. Collect concrete prompts that should and should not activate the skill. 2. Name the responsibility in plain language and use a short verb-led name. 3. Put all activation conditions in frontmatter `description`; the body loads only after activation. 4. Keep `SKILL.md` procedural and under 500 lines. 5. Move detailed rules, variants, schemas, and examples into one-level-deep `references/` files. 6. Add a script only for deterministic repeated work, with `--help` and tests. Use [skill-checklist.md](references/skill-checklist.md) before opening a PR. ## Write and test - Use Agent Skills-compatible `name` and `description` frontmatter. - State when to use, when not to use, safety boundaries, workflow, handoffs, and completion evidence. - Avoid copying a reference repository's text, names, examples, or scripts; rewrite principles and record provenance. - Add at least three positive and two negative routing cases, including close neighbors that must not activate. - Create two or three realistic behavior cases with observable outputs and edge conditions before expanding the suite. - Run each case in a fresh context with the candidate skill and with no skill or a frozen previous version. Keep prompts, fixtures, model settings, and output locations identical. - Capture artifacts, public trace/tool s