skill extractor

Data Community

Skill notes

When to Use

Just solved a non-obvious problem through investigation Discovered a workaround that required trial-and-error Found a debugging technique that would help in similar situations Learned a project-specific pattern worth preserving Fixed an error where the root cause wasn't immediately apparent

When NOT to Use

Simple documentation lookups (just bookmark the docs) Trivial fixes (typos, obvious errors) One-off project-specific configurations Knowledge that's already well-documented elsewhere Unverified solutions (wait until it actually works)

Finding Extraction Candidates

Use these prompts to identify knowledge worth extracting: "What did I just learn that wasn't obvious before starting?" "If I faced this exact problem again, what would I wish I knew?" "What error message or symptom led me here, and what was the actual cause?" "Is this pattern specific to this project, or would it help in similar projects?"

Command

Default: saves to ~/.claude/skills/[name]/SKILL.md --project: saves to .claude/skills/[name]/SKILL.md Context hint helps focus extraction (e.g., /skill-extractor the cyclic data DoS fix)

Step 0: Check for Existing Skills

Before creating a new skill, search for existing ones that might cover the same ground: If a related skill exists, consider updating it instead of creating a new one. See skill-lifecycle.md for guidance on when to update vs create.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 0: Check for Existing Skills

Before creating a new skill, search for existing ones that might cover the same ground: If a related skill exists, consider updating it instead of creating a new one. See skill-lifecycle.md for guidance on when to update vs create.

02
Step 1: Identify the Learning

If `$ARGUMENTS` contains a context hint (e.g., "the cyclic data DoS fix"), use it to focus the extraction on that specific topic. Analyze the conversation to identify: What problem was solved? What made the solution non-obvious? What would someone need to know to solve this faster next time?

03
Step 2: Quality Assessment

Evaluate the candidate skill against these criteria: Criterion · Pass? · Evidence Reusable - Helps future tasks, not just this instance · [Why] Non-trivial - Required discovery, not docs lookup · [Why] Verified - Solution actually worked · [Evidence]

04
Step 3: Gather Details

Ask the user: Skill name - Suggest a kebab-case name based on context, let them override Scope - User-level (default) or project-level (`--project`)

05
Step 4: Optional Research

If the topic involves a specific library or framework: Use web search to find current best practices Use Context7 MCP (if available) for official documentation Include relevant sources in the References section Skip research for:

06
Step 5: Generate the Skill

Use the template from skill-template.md. Quality standards: Follow quality-guide.md to ensure the skill provides lasting value. Key points: Behavioral guidance over reference dumps Explain WHY, not just WHAT Specific triggers that compete well against other skills

07
Step 6: Validate Before Saving

Run through the validation checklist in skill-template.md. If validation fails, fix the issues before saving.

08
Step 7: Save the Skill

Create the directory and save: User-level: `~/.claude/skills/[name]/SKILL.md` Project-level: `.claude/skills/[name]/SKILL.md` Report success:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.