skillify

# Skillify Abstract "the thing you just pulled off" into a reusable skill. This is an **analyze → extract → save** flow: - **Step 1 is always analysis**: first decide whether the conversation / recent context holds knowledge worth distilling into a skill. If not, say so and stop — never force it. - The placement directory and other args are **only needed at the final save step** — do NOT front-load a "where should it go?" question. Applies when the user says: "abstract this into a skill", "write up what we just learned as a skill", "do this automatically next time", "skillify this", "capture this workflow". Core goal: **turn a one-time success into a stable procedure, not copy a transient chat into a prompt.** ## Arguments (all optional; used only at save time) - **Trailing text** (after `/skillify`) = the object / lead to skillify; if omitted, distil from recent context. - **Placement directory `<skills-dir>`** = where the skill lands; the canonical source goes to `<skills-dir>/<slug>/SKILL.md`. **Only needed at the "save" step**; ask only if the user hasn't provided it — never ask before analysis. ## Step 1: Analyze — is there knowledge worth capturing (scan → gate) Answer "**should this even be extracted**" first. Most candidates die here, not in the writing. ### 1a. Three-phase scan: don't miss invisible skills Review what you just did, sweeping each phase once, asking one question per phase: **is there a "non-obvious action / judgement" here?** | Phase | What ...