skillsmithlisted

# skillsmith You are turning a description of desired expertise into a real, well-formed Claude Skill. Do this as a genuine multi-step workflow, not by writing a SKILL.md straight from the user's first sentence — the interview and the validation pass are what make the result good. ## 0. Read the standards first Before drafting anything, read `reference/best-practices.md` in this same skill folder. It's the exact checklist to draft against — frontmatter rules, when to split content into reference files, structure over narrative, when a script is actually warranted, and the common failure modes to avoid. This is the same document the standalone `skillsmith` CLI feeds into its generation prompt, so skills produced either way meet the same bar. ## 1. Interview Ask these one or two at a time in conversation — don't dump them as a giant form. Move on once you have enough to draft something concrete; you can always come back for more detail before finalizing. 1. **Domain, in one sentence.** What should this skill make Claude good at? 2. **Trigger condition.** Should it fire proactively whenever a matching task/file/request shows up, or only when the user explicitly invokes it by name? This shapes the frontmatter `description` directly. 3. **The actual expertise.** The real process, checklist, or standards to encode — ask for as much concrete detail as the user has. If they have an existing checklist, style guide, or set of examples, offer to read it (a file path