extract

Convert recurring patterns or debugging solutions into portable, reusable skills.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/stericishere/skills --skill extract-stericishere
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract
Source: https://github.com/stericishere/skills/tree/main/self-improving-agent/skills/extract
Command: npx skills add https://github.com/stericishere/skills --skill extract-stericishere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn recurring patterns or debugging solutions into standalone, reusable skills with a standard structure (SKILL.md, reference docs, and examples), reducing duplication and speeding development workflows.

Core Features & Use Cases

  • Automates the extraction of patterns into portable, shareable skills that can be installed in any project.
  • Establishes a standard skill skeleton (SKILL.md, README.md, and optionally reference docs) to capture context, examples, and usage.
  • Useful for capturing debugging workflows, common fixes, and repeatable processes that have broad applicability.

Quick Start

Run /si:extract <pattern description> to create a new skill directory with SKILL.md, README.md, and optional reference docs.

Frequently Asked Questions about extract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn recurring debugging solutions into reusable skills?

To turn recurring debugging solutions into reusable skills, you provide a pattern description to generate a standard skill directory containing SKILL.md, README.md, and optional reference docs, making the solution portable across projects.

What is the best way to standardize development patterns across multiple teams?

Standardizing development patterns across teams involves converting them into portable skills with a standard skeleton structure like SKILL.md and reference docs, ensuring consistent application and faster onboarding wherever the pattern appears.

How do I create a portable skill from a recurring code pattern?

You create a portable skill by running the extraction command with a pattern description, which generates a skill directory containing SKILL.md frontmatter and optional directories like scripts, references, and assets for execution.

Do I need a specific file format to define a reusable skill?

Yes, defining a reusable skill requires a valid SKILL.md file containing frontmatter with a name and description, alongside optional directories for scripts, references, and assets that the skill loads during execution.

Can I capture debugging workflows into a shareable format for other projects?

Yes, you can capture debugging workflows into a shareable format by extracting them into standalone skills with standard reference docs and examples, reducing duplication and allowing installation in any project.

What limitations exist when extracting patterns into standalone skills?

Extracting patterns into standalone skills requires strict adherence to the SKILL.md frontmatter format for valid execution, meaning any pattern lacking clear context, examples, or repeatable steps may not translate effectively into a portable skill.