Agent skill

Extract

by alirezarezvani in alirezarezvani/claude-skills

Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples.

MITAuto-check passedDevelopment

Install Extract

skills CLI

$ npx skills add alirezarezvani/claude-skills --skill extract -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install alirezarezvani/claude-skills extract --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering-team/self-improving-agent/skills/extract .claude/skills/extract && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "extract" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/self-improving-agent/skills/extract into .claude/skills/extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extract", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/self-improving-agent/skills/extract

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add alirezarezvani/claude-skills --skill extract -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install alirezarezvani/claude-skills extract --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineering-team/self-improving-agent/skills/extract .agents/skills/extract && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "extract" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/self-improving-agent/skills/extract into .agents/skills/extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extract", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add alirezarezvani/claude-skills --skill extract -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install alirezarezvani/claude-skills extract --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineering-team/self-improving-agent/skills/extract .cursor/skills/extract && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "extract" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/self-improving-agent/skills/extract into .cursor/skills/extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extract", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/alirezarezvani/claude-skills.git --path engineering-team/self-improving-agent/skills/extract

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add alirezarezvani/claude-skills --skill extract -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install alirezarezvani/claude-skills extract --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineering-team/self-improving-agent/skills/extract .gemini/skills/extract && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "extract" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/self-improving-agent/skills/extract into .gemini/skills/extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extract", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install alirezarezvani/claude-skills extract

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add alirezarezvani/claude-skills --skill extract -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineering-team/self-improving-agent/skills/extract .github/skills/extract && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "extract" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/self-improving-agent/skills/extract into .github/skills/extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extract", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add alirezarezvani/claude-skills --skill extract -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install alirezarezvani/claude-skills extract --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineering-team/self-improving-agent/skills/extract .opencode/skills/extract && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "extract" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/self-improving-agent/skills/extract into .opencode/skills/extract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extract", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: extract
GitHub stars: 28k
Token cost: ~1.4k tokens
SKILL.md length: 412 words
Files: 1
Skills in repo: 342
Repo updated: Aug 30, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples.

Works in 7 steps: Identify the pattern → Determine skill scope → Generate skill name → …
The user runs /si:extract
SKILL.md covers Usage, When to Extract, Workflow and Examples, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Extract is an agent skill from alirezarezvani/claude-skills. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.

When your agent uses it

The user runs /si:extract
Asks to package a recurring solution from memory into a skill

Example prompts

“/extract”

Requirements

Docker

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Identify the pattern
Determine skill scope
Generate skill name
Create the skill files
SKILL.md structure
Quality gates
Report

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Extract loads about 1.4k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 412 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~58
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 412 words, ~1,414 tokens.

Download SKILL.mdSave it as .claude/skills/extract/SKILL.md (or your agent's skills folder).

name: extract
description: 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.

/si:extract — Create Skills from Patterns

Transforms a recurring pattern or debugging solution into a standalone, portable skill that can be installed in any project.

Usage

/si:extract <pattern description>                  # Interactive extraction
/si:extract <pattern> --name docker-m1-fixes       # Specify skill name
/si:extract <pattern> --output ./skills/            # Custom output directory
/si:extract <pattern> --dry-run                     # Preview without creating files

When to Extract

A learning qualifies for skill extraction when ANY of these are true:

Criterion	Signal
Recurring	Same issue across 2+ projects
Non-obvious	Required real debugging to discover
Broadly applicable	Not tied to one specific codebase
Complex solution	Multi-step fix that's easy to forget
User-flagged	"Save this as a skill", "I want to reuse this"

Workflow

Step 1: Identify the pattern

Read the user's description. Search auto-memory for related entries:

bash

MEMORY_DIR="$HOME/.claude/projects/$(pwd | sed 's|/|%2F|g; s|%2F|/|; s|^/||')/memory"
grep -rni "<keywords>" "$MEMORY_DIR/"

If found in auto-memory, use those entries as source material. If not, use the user's description directly.

Step 2: Determine skill scope

Ask (max 2 questions):

"What problem does this solve?" (if not clear)
"Should this include code examples?" (if applicable)

Step 3: Generate skill name

Rules for naming:

Lowercase, hyphens between words
Descriptive but concise (2-4 words)
Examples: docker-m1-fixes, api-timeout-patterns, pnpm-workspace-setup

Reserved fragments — must NOT appear in the skill name:

claude
anthropic

For skills about Claude Code itself, use the cc- prefix instead:

❌ claude-code-settings → ✅ cc-settings
❌ claude-code-maintenance → ✅ cc-maintenance
❌ claude-mcp-tools → ✅ cc-mcp-tools
❌ claude-plugin-development → ✅ cc-plugin-development

Before writing the skill directory, check the proposed name against this list. If a reserved fragment is present, transform it (drop the fragment or replace the claude*/anthropic* prefix with cc-) and confirm with the user.

Step 4: Create the skill files

Spawn the skill-extractor agent for the actual file generation.

The agent creates:

<skill-name>/
├── SKILL.md            # Main skill file with frontmatter
├── README.md           # Human-readable overview
└── reference/          # (optional) Supporting documentation
    └── examples.md     # Concrete examples and edge cases

Step 5: SKILL.md structure

The generated SKILL.md must follow this format:

markdown

---
name: "skill-name"
description: "<one-line description>. Use when: <trigger conditions>."
---

# <Skill Title>

> One-line summary of what this skill solves.

## Quick Reference

| Problem | Solution |
|---------|----------|
| {{problem 1}} | {{solution 1}} |
| {{problem 2}} | {{solution 2}} |

## The Problem

{{2-3 sentences explaining what goes wrong and why it's non-obvious.}}

## Solutions

### Option 1: {{Name}} (Recommended)

{{Step-by-step with code examples.}}

### Option 2: {{Alternative}}

{{For when Option 1 doesn't apply.}}

## Trade-offs

| Approach | Pros | Cons |
|----------|------|------|
| Option 1 | {{pros}} | {{cons}} |
| Option 2 | {{pros}} | {{cons}} |

## Edge Cases

- {{edge case 1 and how to handle it}}
- {{edge case 2 and how to handle it}}

Show full SKILL.md (160 more words)Show less

Step 6: Quality gates

Before finalizing, verify:

SKILL.md has valid YAML frontmatter with name and description
name matches the folder name (lowercase, hyphens)
name does NOT contain reserved fragments claude or anthropic (use cc- prefix for Claude Code skills)
Description includes "Use when:" trigger conditions
Solutions are self-contained (no external context needed)
Code examples are complete and copy-pasteable
No project-specific hardcoded values (paths, URLs, credentials)
No unnecessary dependencies

Step 7: Report

✅ Skill extracted: {{skill-name}}

Files created:
  {{path}}/SKILL.md          ({{lines}} lines)
  {{path}}/README.md         ({{lines}} lines)
  {{path}}/reference/examples.md  ({{lines}} lines)

Install: /plugin install (copy to your skills directory)
Publish: clawhub publish {{path}}

Source: MEMORY.md entries at lines {{n, m, ...}} (retained — the skill is portable, the memory is project-specific)

Examples

Extracting a debugging pattern

/si:extract "Fix for Docker builds failing on Apple Silicon with platform mismatch"

Creates docker-m1-fixes/SKILL.md with:

The platform mismatch error message
Three solutions (build flag, Dockerfile, docker-compose)
Trade-offs table
Performance note about Rosetta 2 emulation

Extracting a workflow pattern

/si:extract "Always regenerate TypeScript API client after modifying OpenAPI spec"

Creates api-client-regen/SKILL.md with:

Why manual regen is needed
The exact command sequence
CI integration snippet
Common failure modes

Tips

Extract patterns that would save time in a different project
Keep skills focused — one problem per skill
Include the error messages people would search for
Test the skill by reading it without the original context — does it make sense?

Files

Just SKILL.md in engineering-team/self-improving-agent/skills/extract of alirezarezvani/claude-skills.

Open the folder on GitHubat commit 19392f7

Compare with similar skills

Extract next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Extract compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Extract this skillalirezarezvani/claude-skills	28k	—	~1.4k	Automated safety check: Pass	MIT	1 mo ago
Trellis Session Insightmindfold-ai/Trellis	15k	4 repos	~1.7k	Automated safety check: Pass	AGPL-3.0	8 days ago
Native Data FetchingCherryHQ/cherry-studio-app	4k	6 repos	~2.9k	Automated safety check: Notes	MIT	today
Debugging Executionsn8n-io/n8n	207k	—	~2.6k	Automated safety check: Pass	Custom licence	today
Aoti Debugpytorch/pytorch	104k	1 repos	~1.7k	Automated safety check: Pass	Custom licence	today
Herdr Throwaway Reproductionherdrdev/herdr	43k	—	~2.4k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
15k GitHub starsUsed in 4 repos~1.7k tokens
DevelopmentAuto-check passed
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
4k GitHub starsUsed in 6 repos~2.9k tokens
DevelopmentAuto-check: notes
Debugging Executions
n8n-io/n8n
Official
Debug failed or wrong-output workflow executions using executions tools.
207k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-check passed
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
104k GitHub starsUsed in 1 repo~1.7k tokens
DevelopmentAuto-check passed
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
43k GitHub stars~2.4k tokensUpdated today
DevelopmentAuto-check passed
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
258 GitHub starsUsed in 51 repos~2.4k tokens
DevelopmentAuto-check passed

More from alirezarezvani/claude-skills

All 342 skills in this repo

Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
28k GitHub starsUsed in 3 repos~3.2k tokens
Auto-check passed
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
28k GitHub starsUsed in 2 repos~1.8k tokens
Auto-check passed
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
28k GitHub starsUsed in 1 repo~4.2k tokens
Auto-check passed
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
28k GitHub starsUsed in 1 repo~2.5k tokens
Auto-check passed
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
28k GitHub starsUsed in 1 repo~2.1k tokens
Auto-check passed
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
28k GitHub starsUsed in 1 repo~4.9k tokens
Auto-check passed

Questions about Extract

What does Extract do?

Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples. Extract is an agent skill from alirezarezvani/claude-skills.md, reference docs, and examples.

When should I use Extract?

Extract fits situations like: the user runs /si:extract; asks to package a recurring solution from memory into a skill.

How do I install Extract in Claude Code?

Run `npx skills add alirezarezvani/claude-skills --skill extract -a claude-code`. Or copy the skill folder (engineering-team/self-improving-agent/skills/extract in alirezarezvani/claude-skills) into .claude/skills/extract in your project. Claude Code loads it when a task matches its description.

How do I install Extract in Codex?

Run `npx skills add alirezarezvani/claude-skills --skill extract -a codex`. Or copy the skill folder (engineering-team/self-improving-agent/skills/extract in alirezarezvani/claude-skills) into .agents/skills/extract in your project. Codex loads it when a task matches its description.

Can I use Extract in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill extract -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/extract, .gemini/skills/extract, .github/skills/extract and .opencode/skills/extract in your project.

What does Extract need to run?

SKILL.md names no scripts, command-line tools or credentials: Extract is instructions for the agent only. Our summary lists: Docker.

Does Extract access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Extract safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Extract use?

Extract is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Extract use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Extract?

Skills that share tags, products or a category with Extract: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Extract?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,829 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.

Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Extract

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

/si:extract — Create Skills from Patterns

Usage

When to Extract

Workflow

Step 1: Identify the pattern

Step 2: Determine skill scope

Step 3: Generate skill name

Step 4: Create the skill files

Step 5: SKILL.md structure

Step 6: Quality gates

Step 7: Report

Examples

Extracting a debugging pattern

Extracting a workflow pattern

Tips

Files

Compare with similar skills

Similar skills

More from alirezarezvani/claude-skills

Related

Questions about Extract