playbooks

home / skills / leegonzales / aiskills / skill-extractor

skill-extractor skill

/SkillExtractor/skill-extractor

This skill transforms repeated conversation patterns into reusable SKILL.md files by extracting triggers, inputs, transforms, and outputs.

npx playbooks add skill leegonzales/aiskills --skill skill-extractor

Review the files below or copy the command above to add this skill to your agents.

Files (6)
SKILL.md
2.6 KB
---
name: skill-extractor
description: Extract reusable skills from conversation patterns. Use when asked to "turn this into a skill," "extract a skill," or "I keep doing this task repeatedly."
---

# Skill Extractor

Transform repeated conversation patterns into reusable SKILL.md files.

## Workflow

### 1. Gather Evidence

Ask: "Share a conversation excerpt where Claude did this task well, or describe a task you do repeatedly."

Accept:
- Pasted conversation excerpts
- Task descriptions with examples
- Multiple examples to find common patterns

### 2. Identify the Pattern

Analyze for these elements:

| Element | Find This |
|---------|-----------|
| **Trigger** | What phrase starts this workflow? |
| **Input** | What does user provide? |
| **Transform** | What does Claude do with it? |
| **Output** | What format/structure results? |
| **Quality** | What separates good from bad? |

### 3. Validate

Confirm: "It sounds like you want to [workflow]. Is that right?"

Refine: "What would you change? What context made it work?"

### 4. Generate SKILL.md

Output a complete skill file following the format in `references/skill-template.md`.

### 5. Test

Run the extracted skill on fresh input. Iterate until it works reliably.

## Skill Archetypes

| Type | Pattern | Example |
|------|---------|---------|
| **Transformer** | Format A → Format B | Notes → Email |
| **Analyzer** | Input → Assessment | Code → Review |
| **Generator** | Parameters → Content | Topic → Blog |
| **Synthesizer** | Many → One | Feedback → Themes |

## Viability Check

**Strong candidates:**
- Done 3+ times with similar structure
- Clear input → output transformation
- Required specific prompting to work
- Explainable to a colleague

**Weak candidates:**
- One-off creative tasks
- Simple Q&A (no workflow)
- Requires external data
- Too vague to define success

## Output Deliverables

Provide:
1. **SKILL.md** — Complete, ready to use
2. **Test prompt** — Verify it works
3. **Usage examples** — How to invoke
4. **Refinement notes** — Next iteration

## Example Extraction

**User says:** "I keep asking Claude to turn meeting notes into weekly updates."

**Extracted pattern:**
- Trigger: "write weekly update" / "summarize this week"
- Input: Bullet points from meetings
- Transform: Organize by Accomplishments/In Progress/Blockers
- Output: Professional email format
- Quality: Outcome-focused, not activity-focused

**Result:** See `references/example-extractions.md` for the full `weekly-update-writer` skill.

## References

- `references/skill-template.md` — Standard skill format
- `references/example-extractions.md` — Before/after examples

Overview

This skill extracts reusable automation skills from repeated conversation patterns. It guides you from example conversations through pattern identification to a ready-to-use skill file and test prompt. The goal is a reliable, repeatable workflow that others can apply without re-teaching the steps.

How this skill works

You provide one or more conversation excerpts or descriptions of a repeated task. The extractor identifies trigger phrases, inputs, transformations, outputs, and quality criteria. It validates the inferred workflow with a confirmation prompt, generates a complete skill file plus a test prompt and usage examples, then recommends iterative tests and refinements.

When to use it

  • You keep asking the assistant the same thing multiple times
  • You want to convert a manual prompt sequence into a reusable skill
  • You have several examples and want a generalized workflow
  • You need clear triggers and success criteria for automation
  • You want a testable prompt and usage examples for handoff

Best practices

  • Provide 3+ high-quality examples to surface consistent patterns
  • Include both successful and failed examples to define quality boundaries
  • Describe explicit trigger phrases users use to start the task
  • State precise input formats and expected output structure
  • Run the generated test prompt on fresh inputs and iterate quickly

Example use cases

  • Turn meeting note excerpts into a weekly update generator with Accomplishments/In Progress/Blockers sections
  • Convert repeated code review requests into an analyzer that lists issues and suggested fixes
  • Extract a content brief generator from multiple blog-outline requests into a parameters→draft generator
  • Synthesize many customer feedback snippets into a themes-and-priority synthesis skill
  • Create a transformation that turns raw research notes into a structured summary and action list

FAQ

What input formats do you accept?

Paste conversation excerpts, describe the repeated task with examples, or supply multiple variants; both free text and bulleted examples work.

How do I know a pattern is viable to extract?

A strong candidate appears 3+ times with the same structure, has clear input→output mapping, and produces repeatable quality when prompted.