write-skilllisted

# write-skill Create compact skills under `skills/<name>/` that load only the behavior needed at invocation time. ## Workflow 1. Clarify only missing essentials: capability, triggers, non-triggers, tool/script needs, and portability. 2. Pick a unique kebab-case name. 3. Draft `SKILL.md` as an operator card: what to run, when to run it, what output means, what traps matter. 4. Add helper files only when they remove repeated deterministic work. 5. Compress once; add one README row; do not commit unless asked. ## Template ````md --- name: <kebab-case> description: <Concrete capability.> Use when <real phrases, file types, tools, or contexts>. Do NOT use <negative triggers if broad>. --- # <name> <One-line operational contract.> ## Usage / Commands / Routing ```bash scripts/tool_or_helper.py <arg> ``` ## Notes - <What output shape means, or how to consume it.> - <Hard rule, setup failure, safety boundary, or common mistake.> ```` ## Description The description is the routing surface; optimize it first. - Use 1-3 sentences, third person, present tense. - Sentence 1 names the concrete capability. - Sentence 2 starts with `Use when ...` and lists actual trigger phrases, file types, tools, or contexts. - Add `Do NOT use ...` for broad domains such as review, search, docs, macOS, git, or browser work. - Avoid marketing words, time-sensitive claims, and duplicate "this skill should be used when" phrasing. ## Body Keep: - runnable commands or exact workflow steps; - setu