skill-extractor — Claude Code skill: what it does, how to install
skill-extractor turns a finished session into a reusable Claude skill: the cause of a failure, a workaround, the symptom that points to it.
CC-BY-SA-4.0 ★ 540 updated 2026-07-14
/plugin marketplace add trailofbits/skills-curated
/plugin install skill-extractor@skills-curatedWhat skill-extractor does
Point it at the session you just finished and it pulls out what deserves a second life: the cause behind a non-obvious failure, a workaround found by trial and error, the symptom that leads to either. Output is a SKILL.md file. It lands in ~/.claude/skills/[name]/SKILL.md by default, or in .claude/skills/[name]/SKILL.md when you pass --project, which means it ships with the repo.
The process is ordered. First it looks through both skill directories with ls and grep for an existing skill that already covers the topic, because updating beats piling up duplicates. Then it names the problem, the insight and the trigger conditions, scores the candidate against a criteria table and asks you to confirm. A kebab-case name and a scope come next. Research through web search or Context7 MCP is optional and only for library or framework topics. Template, validation, save.
Nothing fires by itself: there are no hooks or automatic triggers, and /skill-extractor is the only way in. Tool access stops at Read, Write, Glob, Grep, WebSearch and AskUserQuestion. It also declines thin material — trivial fixes, one-off project config, anything already covered elsewhere, and fixes that have not been shown to work.
What it helps with
- capture a hard-won bug fix as a reusable skill
- document a workaround that took trial and error
- record the exact error text that should trigger the knowledge next time
- update an existing skill with a new edge case instead of adding a duplicate
- filter candidates through a quality checklist before saving
Example prompts for the agent
/skill-extractor— turn the AST recursion crash we just fixed into a skill/skill-extractor --project— keep this one in the repo next to the code/skill-extractor— check whether a retry skill already exists and update that one
How to install skill-extractor
1Plugin marketplace
/plugin marketplace add trailofbits/skills-curated/plugin install skill-extractor@skills-curatedThis installs the whole skill-extractor plugin with all its skills
2Skills CLI (Vercel)
npx skills add trailofbits/skills-curated --skill skill-extractor -a claude-code3Manually: put the files in place
~/.claude/skills/skill-extractor/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/skill-extractor/
1Skills CLI (Vercel)
npx skills add trailofbits/skills-curated --skill skill-extractor -a codex2Manually: put the files in place
.agents/skills/skill-extractor/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add trailofbits/skills-curated --skill skill-extractor -a cursor2Manually: put the files in place
.cursor/skills/skill-extractor/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install trailofbits/skills-curated plugins/skill-extractor/skills/skill-extractor2Manually: put the files in place
.github/skills/skill-extractor/SKILL.md1Skills CLI (Vercel)
npx skills add trailofbits/skills-curated --skill skill-extractor -a gemini-cli2Platform CLI
gemini skills install https://github.com/trailofbits/skills-curated --path plugins/skill-extractor/skills/skill-extractorManually: put the files in place
.devin/skills/skill-extractor/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about skill-extractor
How do I install skill-extractor in Claude Code?
From the marketplace: run /plugin marketplace add trailofbits/skills-curated, then /plugin install skill-extractor@skills-curated.
What does skill-extractor do?
It reads the current session, finds the part worth keeping and writes it to SKILL.md along with the trigger conditions and the reasoning behind the fix.
Can I keep the generated skill in the project?
Yes. The default path is ~/.claude/skills/[name]/SKILL.md; add --project and it goes to .claude/skills/[name]/SKILL.md inside the repository.