skillifylisted

# skillify Extract a procedure you keep repeating into a SKILL.md an agent can discover and follow. The input is a script, a shell history pattern, a runbook, or "the thing we just did"; the output is an installable skill. ## Is it worth a skill? Make a skill when the technique was not obvious the first time, will recur across projects, and involves judgment. Do not make a skill for one-off fixes, things a linter or script can fully enforce (automate those instead), or project-specific conventions (those belong in the project's CLAUDE.md or AGENTS.md). ## Extraction 1. **Find the procedure, not the instance.** Strip session-specific paths, names, and values. What survives is the reusable spine: triggers, steps, decision points, failure modes. 2. **Capture the gotchas.** The non-obvious parts are the whole value: the flag that silently resets state, the step everyone skips, the error that means something different than it says. Interview the user or mine the transcript for "the thing that bit us". 3. **Decide what stays executable.** A script the skill calls beats prose describing the script. Put reusable code in `scripts/` next to SKILL.md and have the skill invoke it; keep judgment in the prose. ## Format ```markdown --- name: verb-first-hyphenated-name # or the tool's own name when wrapping a named tool description: Use when [triggering conditions and symptoms only, third person, under 500 chars] --- # name One-paragraph overview: what this achieves and the core