extract

Topics in the source

• /si:extract — Create Skills from Patterns
• Usage
• When to Extract
• Workflow
• Step 1: Identify the pattern
• Step 2: Determine skill scope
• Step 3: Generate skill name
• Step 4: Create the skill files

Transforms a recurring pattern or debugging solution into a standalone, portable skill that can be installed in any project. 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" | Read the user's description. Search auto-memory for related entries: If found in auto-memory, use those entries as source material. If not, use the user's description directly. Ask (max 2 questions): "What problem does this solve?" (if not clear) "Should this include code examples?" (if applicable) Rules for naming: Lowercase, hyphens between words Descriptive but concise (2-4 words) Examples: docker-m1-fixes, api-timeout-patterns, pnpm-workspace-setup Reserved fragments — must NOT appear in the skill name: claude anthropic For skills about Claude Code itself, use the cc- prefix instead: ❌ claude-code-settings → ✅ cc-settings ❌ claude-code-maintenance → ✅ cc-maintenance ❌ claude

This is an excerpt. Refer to the complete source and its current requirements.