skillizelisted

# /skillize -- Session to Skill A devlog captures *why* you made decisions. A skill captures *how* to repeat the workflow. Skillize extracts the repeatable pattern from a session and packages it as a Claude Code skill. The test: if someone invokes this skill six months from now on a similar problem, does it reproduce the quality of today's session without re-discovering the process? ## When to skillize vs. when NOT to **Good candidates:** - Multi-step workflow that took 10+ minutes and would recur - Process where you discovered non-obvious tool sequences - Workflow with user corrections that became stable rules - Domain-specific knowledge that required research to find - Pattern where Claude kept going wrong until guided right - Recurring diagnostic workflows (incident triage, leak hunting) **Bad candidates:** - One-off investigation (use /reflect instead) - Simple task Claude handles well without guidance - Workflow that depends entirely on specific data or context - One-off debugging whose fix lives in code (not the process) - Process that changes every time (no stable pattern) ## Process ### Phase 1: Survey Reconstruct the session. Don't rely on memory -- check the evidence. 1. **Conversation scan**: Walk the conversation for tool calls, user corrections, repeated patterns, and stable decisions. 2. **Artifact check**: If inside a git repo, run `git diff` and `git log` to see what actually changed. If not in a git repo, inspect the conversation for files