Skip to content
Skills Library
AI & agents · Automation

extract-pattern

/extract-pattern

Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.

Repository
maestro ↗
Licence
MIT
Last repository change
29.04.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.04.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.

Arguments

/extract-pattern [source workflow or area]
Original author description

Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.

How it works

  1. MANDATORY PREPARATION
Original SKILL.md headings · 61 lines, 345 words
SKILL.md preview
---
name: extract-pattern
description: "Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows."
argument-hint: "[source workflow or area]"
category: utility
version: 2.0.0
user-invocable: true
---

## MANDATORY PREPARATION

Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.

---

Turn working solutions into reusable patterns. Every successful workflow contains patterns that are applicable beyond their original context.

### Step 1: Identify What Worked

Review the workflow and identify components that:

- Solved a common problem in a particularly effective way
- Would be useful in other workflows or projects
- Required significant iteration to get right
- Represent a non-obvious solution

### Step 2: Generalize the Pattern

Transform the specific solution into a reusable template:

**From specific** → **To general pattern**:

```markdown
## Pattern: [Name]
**Problem**: What recurring problem does this solve?
**When to use**: When is this pattern appropriate?
**When NOT to use**: When is this pattern inappropriate?
**Template**: Copy-pastable starting point with customization markers.
**Variants**: Common variations for different contexts.
**Pitfalls**: What went wrong during development and how it was fixed.
**Examples**: 1-2 concrete examples.
```

### Step 3: Test Reusability

- Apply the template to a different but analogous problem
- Confirm the customization points are sufficient
- Verify the documentation is clear enough for someone unfamiliar with the original

| Workflow Element | Extract As |
|-----------------|-----------|
| Effective prompt structure | Prompt template with customization points |
| Tool chain that works well | Pipeline pattern with data flow diagram |
| Error handling strategy | Resilience pattern with implementation guide |
| Evaluation approach | Quality assurance pattern with scoring rubric |
| Context management technique | Context pattern with budget guidance |
| Agent coordination protocol | Orchestration pattern with handoff templates |

### Recommended Next Step

After extracting patterns, run `/calibrate` to ensure the new patterns are consistent with existing project conventions.

**NEVER**:

- Extract patterns from workflows that don't work reliably
- Over-generalize (if it only applies to one case, document it as a solution, not a pattern)
- Skip the "when NOT to use" section
- Extract without testing reusability

Versions

The database has no other skills named extract-pattern.

Database snapshot: 13.11.2026 · package version ccd37e69da66 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100pattern-learn
    Use when the user wants to extract a reusable pattern from recent work and store it for future use. "Save this as a pattern", "remember this approach", "learn from this commit".
  • 100authoring-patterns
    Convert validated playground templates or HTML compositions into reusable pattern files (*.examples.ts) in the pattern library. Use this skill whenever the user wants to save, persist, store, or catalog a template, prototype, composition, or playground result as a reusable…
  • 100extract
    Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples. Use when the user runs /si:extract or asks to package a recurring solution from memory into a skill.
  • 100skill-builder
    Create new Claude Code skills with best practices. Use when user wants to create, extract, or build a new skill. Provides templates and GitHub automation. Trigger phrases include "create a skill", "build a skill", "extract a skill", "new skill", "/skill-builder".
  • 100self-improving-agent
    Curate Claude Code's auto-memory into durable project knowledge. Analyze MEMORY.md for patterns, promote proven learnings to CLAUDE.md and .claude/rules/, extract recurring solutions into reusable skills. Use when: (1) reviewing what Claude has learned about your project, (2)…
  • 100pattern-search
    Use to find captured patterns relevant to current work. "Have we got a pattern for X", "show me how we usually do Y". Searches memory for kind:pattern entries.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.