skill-adapter

Analyzes existing plugins to extract their capabilities, then adapts and applies those skills to the current task. Acts as a universal skill chameleon that learns from other plugins. Activates when you request "skill adapter" functionality.

1,868 stars

Best use case

skill-adapter is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Analyzes existing plugins to extract their capabilities, then adapts and applies those skills to the current task. Acts as a universal skill chameleon that learns from other plugins. Activates when you request "skill adapter" functionality.

Teams using skill-adapter should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/pi-pathfinder/SKILL.md --create-dirs "https://raw.githubusercontent.com/jeremylongshore/claude-code-plugins-plus-skills/main/backups/skill-structure-cleanup-20251108-073936/plugins/examples/pi-pathfinder/skills/pi-pathfinder/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/pi-pathfinder/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How skill-adapter Compares

Feature / Agentskill-adapterStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Analyzes existing plugins to extract their capabilities, then adapts and applies those skills to the current task. Acts as a universal skill chameleon that learns from other plugins. Activates when you request "skill adapter" functionality.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Skill Adapter - Universal Plugin Capability Extractor

## Purpose
Analyzes plugins in the claude-code-plugins marketplace to understand their capabilities, extracts the core patterns and approaches, then adapts those skills to solve the current user's task. Acts as a "skill chameleon" that can adopt any plugin's capabilities.

## How It Works

### 1. Task Analysis
When user presents a task:
- Identify the core capability needed (e.g., "analyze code quality", "generate documentation", "automate deployment")
- Determine the domain (security, devops, testing, etc.)
- Extract key requirements and constraints

### 2. Plugin Discovery
Search existing plugins for relevant capabilities:

```bash
# Find plugins in relevant category
ls plugins/community/ plugins/packages/ plugins/examples/

# Search for keywords in plugin descriptions
grep -r "keyword" --include="plugin.json" plugins/

# Find similar commands/agents
grep -r "capability-name" --include="*.md" plugins/
```

### 3. Capability Extraction

For each relevant plugin found, analyze:

**Commands (commands/*.md):**
- Read the markdown content
- Extract the approach/methodology
- Identify input/output patterns
- Note any scripts or tools used

**Agents (agents/*.md):**
- Understand the agent's role
- Extract problem-solving approach
- Note decision-making patterns
- Identify expertise areas

**Skills (skills/*/SKILL.md):**
- Read the skill instructions
- Extract core capability
- Note trigger conditions
- Understand tool usage patterns

**Scripts (scripts/*.sh, *.py):**
- Analyze script logic
- Extract reusable patterns
- Identify best practices
- Note error handling approaches

### 4. Pattern Synthesis

Combine learned patterns:
- Merge multiple approaches if beneficial
- Adapt to current context and constraints
- Simplify or enhance based on user needs
- Ensure compatibility with current environment

### 5. Skill Application

Apply the adapted skill:
- Use the learned approach
- Follow the extracted patterns
- Apply best practices discovered
- Adapt syntax/tools to current context

## Example Workflows

### Example 1: Learning Code Analysis from Security Plugins

**User task:** "Analyze this codebase for issues"

**Process:**
1. Search for security and code-analysis plugins
2. Find: `owasp-top-10-scanner`, `code-quality-enforcer`, `security-audit-agent`
3. Extract patterns:
   - OWASP scanner checks for: SQL injection, XSS, CSRF, auth issues
   - Quality enforcer looks at: complexity, duplication, standards
   - Audit agent examines: dependencies, secrets, permissions
4. Synthesize approach:
   - Run multi-layer analysis
   - Check security patterns first
   - Then code quality metrics
   - Then dependency issues
5. Apply to user's codebase with adapted checks

### Example 2: Adopting Documentation Skills

**User task:** "Generate API documentation"

**Process:**
1. Find documentation plugins
2. Discover: `api-documenter`, `openapi-generator`, `readme-builder`
3. Extract approaches:
   - API documenter: parses code, generates OpenAPI spec
   - OpenAPI generator: creates interactive docs
   - README builder: structures documentation hierarchically
4. Synthesize:
   - Parse code for endpoints
   - Generate OpenAPI/Swagger spec
   - Create interactive documentation
   - Build comprehensive README
5. Apply combined approach to user's API

### Example 3: Learning Automation from DevOps Plugins

**User task:** "Automate deployment process"

**Process:**
1. Search DevOps category
2. Find: `deployment-automation`, `ci-cd-pipeline`, `docker-compose-generator`
3. Extract patterns:
   - Deployment automation: build → test → deploy → verify
   - CI/CD pipeline: trigger conditions, parallel jobs, rollback
   - Docker compose: service orchestration, environment management
4. Synthesize deployment workflow
5. Apply to user's specific tech stack

## Reasoning Process

### When to Use Skill Adapter

Trigger when:
- User needs capability that might exist in marketplace
- Task could benefit from existing plugin patterns
- User asks: "Is there a plugin for this?"
- Similar problems have been solved before
- Multiple approaches could be combined

### Plugin Selection Criteria

Choose plugins based on:
1. **Relevance**: Matches task domain/requirements
2. **Quality**: Well-documented, clear approach
3. **Simplicity**: Not overly complex for the task
4. **Recency**: Updated plugins preferred
5. **Popularity**: Featured or well-maintained plugins

### Adaptation Strategy

When adapting skills:
- **Keep**: Core logic and proven patterns
- **Adapt**: Syntax, tool names, specific commands
- **Enhance**: Add error handling, user feedback
- **Simplify**: Remove unnecessary complexity
- **Contextualize**: Adjust to user's environment

## Limitations and Boundaries

### What Skill Adapter CAN Do:
✅ Read and analyze plugin source code
✅ Extract patterns and approaches
✅ Adapt methodologies to new contexts
✅ Combine multiple plugin capabilities
✅ Apply learned skills with reasoning

### What Skill Adapter CANNOT Do:
❌ Execute compiled code (MCP servers)
❌ Access external APIs without credentials
❌ Modify original plugins
❌ Guarantee exact plugin behavior replication
❌ Use plugins that require specific environment setup

## Success Criteria

Skill adaptation is successful when:
1. User's task is completed effectively
2. Approach borrowed makes logical sense
3. Adapted skill is properly contextualized
4. User understands where the approach came from
5. Result quality matches or exceeds original plugin

## Transparency

Always inform user:
- Which plugins were analyzed
- What patterns were extracted
- How the skill was adapted
- Why this approach was chosen
- Any limitations of the adaptation

## Example Usage

```
User: "I need to validate JSON schemas in my project"

Skill Adapter Process:
1. Searches plugins for JSON validation
2. Finds: schema-validator, json-lint-enforcer
3. Extracts: ajv library usage, error formatting patterns
4. Adapts: Uses available tools (jq, node, python)
5. Applies: Validates user's schemas with detailed errors
6. Reports: "I adapted the schema-validator approach using jq
   for validation and added custom error formatting"
```

## Meta-Learning

Skill Adapter improves by:
- Tracking which plugins solve which tasks best
- Learning which patterns are most reusable
- Noting which adaptations work well
- Building a mental model of the marketplace
- Understanding plugin ecosystem relationships

---

**In essence:** Skill Adapter is a meta-skill that makes the entire plugin marketplace available as a learning resource, extracting and applying capabilities on-demand to solve user tasks efficiently.

Related Skills

schema-optimization-orchestrator

1868
from jeremylongshore/claude-code-plugins-plus-skills

Multi-phase schema optimization workflow orchestrator. Creates session directories, spawns phase agents sequentially, validates outputs, aggregates results. Trigger: "run schema optimization", "optimize schema workflow", "execute schema phases"

test-skill

1868
from jeremylongshore/claude-code-plugins-plus-skills

Test skill for E2E validation. Trigger with "run test skill" or "execute test". Use this skill when testing skill activation and tool permissions.

example-skill

1868
from jeremylongshore/claude-code-plugins-plus-skills

Brief description of what this skill does and when the model should activate it. Use when [describe the user's intent or situation]. Trigger with "example phrase", "another trigger", "/example-skill".

testing-visual-regression

1868
from jeremylongshore/claude-code-plugins-plus-skills

Detect visual changes in UI components using screenshot comparison. Use when detecting unintended UI changes or pixel differences. Trigger with phrases like "test visual changes", "compare screenshots", or "detect UI regressions".

generating-unit-tests

1868
from jeremylongshore/claude-code-plugins-plus-skills

Test automatically generate comprehensive unit tests from source code covering happy paths, edge cases, and error conditions. Use when creating test coverage for functions, classes, or modules. Trigger with phrases like "generate unit tests", "create tests for", or "add test coverage".

generating-test-reports

1868
from jeremylongshore/claude-code-plugins-plus-skills

Generate comprehensive test reports with metrics, coverage, and visualizations. Use when performing specialized testing. Trigger with phrases like "generate test report", "create test documentation", or "show test metrics".

orchestrating-test-execution

1868
from jeremylongshore/claude-code-plugins-plus-skills

Test coordinate parallel test execution across multiple environments and frameworks. Use when performing specialized testing. Trigger with phrases like "orchestrate tests", "run parallel tests", or "coordinate test execution".

managing-test-environments

1868
from jeremylongshore/claude-code-plugins-plus-skills

Test provision and manage isolated test environments with configuration and data. Use when performing specialized testing. Trigger with phrases like "manage test environment", "provision test env", or "setup test infrastructure".

generating-test-doubles

1868
from jeremylongshore/claude-code-plugins-plus-skills

Generate mocks, stubs, spies, and fakes for dependency isolation. Use when creating mocks, stubs, or test isolation fixtures. Trigger with phrases like "generate mocks", "create test doubles", or "setup stubs".

generating-test-data

1868
from jeremylongshore/claude-code-plugins-plus-skills

Generate realistic test data including edge cases and boundary conditions. Use when creating realistic fixtures or edge case test data. Trigger with phrases like "generate test data", "create fixtures", or "setup test database".

analyzing-test-coverage

1868
from jeremylongshore/claude-code-plugins-plus-skills

Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".

managing-snapshot-tests

1868
from jeremylongshore/claude-code-plugins-plus-skills

Create and validate component snapshots for UI regression testing. Use when performing specialized testing. Trigger with phrases like "update snapshots", "test UI snapshots", or "validate component snapshots".