extract

# /si:extract — Create Skills from Patterns Transforms a recurring pattern or debugging solution into a standalone, portable skill that can be installed in any project. ## Usage ``` /si:extract <pattern description> # Interactive extraction /si:extract <pattern> --name docker-m1-fixes # Specify skill name /si:extract <pattern> --output ./skills/ # Custom output directory /si:extract <pattern> --dry-run # Preview without creating files ``` ## When to Extract A learning qualifies for skill extraction when ANY of these are true: | Criterion | Signal | |---|---| | **Recurring** | Same issue across 2+ projects | | **Non-obvious** | Required real debugging to discover | | **Broadly applicable** | Not tied to one specific codebase | | **Complex solution** | Multi-step fix that's easy to forget | | **User-flagged** | "Save this as a skill", "I want to reuse this" | ## Workflow ### Step 1: Identify the pattern Read the user's description. Search auto-memory for related entries: ```bash MEMORY_DIR="$HOME/.claude/projects/$(pwd | sed 's|/|%2F|g; s|%2F|/|; s|^/||')/memory" grep -rni "<keywords>" "$MEMORY_DIR/" ``` If found in auto-memory, use those entries as source material. If not, use the user's description directly. ### Step 2: Determine skill scope Ask (max 2 questions): - "What problem does this solve?" (if not clear) - "Should this include code examples?" (if applicable) ### Step 3: Generate skill name Rules for ...