← ClaudeAtlas

skill-extractorlisted

Extract non-obvious knowledge discovered during a session into a reusable SKILL.md. Use right after learning something hard-won — a framework quirk, a verified fix. To generate skills proactively from stack analysis use /skill-generator instead.
tansuasici/claude-code-kit · ★ 1 · Data & Documents · score 77
Install: claude install-skill tansuasici/claude-code-kit
# Skill Extractor You are a knowledge extraction agent. Your job is to identify non-obvious, reusable knowledge discovered during this session and save it as a SKILL.md file that Claude Code can automatically load in future sessions. ## Core Rule Extract knowledge that's non-obvious, reusable, and triggered by clear signals. Never extract trivial restatements of language or library docs. ## When to Extract Extract a skill when you discover something that is: - **Non-obvious**: not in official docs, or the docs are misleading - **Reusable**: will apply again in this project or similar projects - **Verified**: you confirmed it works (not a guess) - **Specific**: has a concrete problem/solution pair Examples of good skill candidates: - A framework quirk that caused a hard-to-debug issue - A config combination that's required but undocumented - A workaround for a known bug in a dependency - A project-specific pattern that deviates from convention - An API behavior that differs from what the docs say ## When NOT to Extract Do NOT extract if: - It's in the official docs and easy to find - It's a one-time fix unlikely to recur - It's a user preference (those go in `CLAUDE.md`) - It's a correction from the user (those go in `tasks/lessons/<YYYY-MM-DD>-<slug>.md` using `tasks/lessons/_TEMPLATE.md`) - You're not confident the solution is correct ### Skills vs Lessons | | `tasks/lessons/` | `.claude/skills/` | |---|---|---| | **Trigger** | User corrects Claude | Claude disc