skillifylisted

# Skillify Transforms a useful concept observed in an external tool / framework / methodology / article into a self-contained Claude Code skill — without adopting the source tool itself. ## When to use this skill **Use skillify when**: - A tool has a great idea but its full install is too invasive (Ruflo's SPARC, plugin systems, hook patterns, memory architectures…) - A blog post / paper describes a workflow worth keeping (Hamel's eval rubric, an Anthropic engineering pattern, a SPARC-like methodology…) - The user says "I want to keep this idea but not the whole tool" **Don't use skillify when**: - The concept is already trivially covered by an existing skill (check first) - The concept needs runtime/daemon/database (it's a service, not a skill) - The user wants to actually adopt the tool itself (just install it then) ## Heuristic: skillify vs adopt-as-tool | Skillify | Adopt as tool | |----------|---------------| | Concept fits in 100-300 lines of SKILL.md | Needs runtime/daemon | | Source tool has friction you want to skip | Source tool is mature & cohesive | | You want reversibility | You want fail-fast on the whole thing | | 1-2 users (you) | Team adoption | If the user is unsure, ask via AskUserQuestion before proceeding. --- ## The 5-step procedure Track each step with TodoWrite from the start. Don't skip — each step de-risks the next. ### Step 1 — Spot Confirm what concept the user wants to skillify. If `<argument-hint>` is vague, ask: - What's the **idea**