write-a-skilllisted

# Write a Skill A skill is an onboarding guide for an agent: a folder with a SKILL.md that loads on demand and teaches Claude a repeatable behavior. This meta-skill converts "here's what I want" into that document, correctly structured, so the user doesn't need to know the format, the YAML rules, or the triggering mechanics. The stakes are asymmetric. A skill gets invoked hundreds of times by someone who will never read its source, so an hour of care at authoring time is amortized across every future invocation, and a flaw (a description that never triggers, an instruction that overfits) is paid on every one. ## Step 1: Extract the intent From the user's description, and from the conversation itself if they said "turn THIS into a skill" (mine the thread for the workflow, the corrections they made, the output format they accepted), establish: 1. What behavior should the skill produce? 2. When should it fire: what would the user actually type? 3. When must it NOT fire: the near-miss cases? 4. What does a good output look like: is there a fixed format? 5. Does anything need to be deterministic (a script) rather than generated fresh each time? Ask only for what's genuinely missing, 3-5 questions at most. The questions about anti-triggers (#3) and output format (#4) are the ones users never volunteer and always have opinions about. ## Step 2: Write the frontmatter **Name**: lowercase, hyphens, max 64 chars, matching the folder name. Verb phrases or clear nouns: `fact-ch