Execute 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. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
26
10%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/examples/pi-pathfinder/skills/skill-adapter/SKILL.mdAnalyzes existing plugins in the repository to extract their capabilities, then synthesizes and applies those learned patterns to the current task. Functions as a universal skill chameleon that discovers relevant plugins, extracts their approaches and methodologies, and adapts them to novel requests.
plugins/ directory tree (community, packages, examples categories)grep and find available on PATH for plugin discoverycommands/*.md, agents/*.md, skills/*/SKILL.md, and scripts/${CLAUDE_SKILL_DIR}/references/how-it-works.md).plugins/community/, plugins/packages/, and plugins/examples/ directories. Match on plugin.json descriptions and keyword fields.commands/*.md): read content, extract approach and input/output patterns.agents/*.md): understand roles, decision-making patterns, expertise areas.skills/*/SKILL.md): read instructions, extract core capability and tool usage.scripts/*.sh, *.py): analyze logic, identify reusable patterns and error handling.A structured adaptation report containing:
| Error | Cause | Solution |
|---|---|---|
| No matching plugins found | Search terms too narrow or domain not represented | Broaden search keywords; check alternative categories; fall back to general-purpose approach |
| Plugin directory inaccessible | Missing read permissions or incorrect path | Verify plugins/ directory exists and permissions allow traversal |
| Incompatible patterns | Extracted approaches conflict with current environment | Prioritize the most relevant plugin's approach; discard conflicting elements |
| Empty skill/command files | Plugin has stub content without real instructions | Skip that plugin and note it as incomplete; rely on other sources |
Learning code analysis from security plugins:
Task: "Analyze this codebase for issues."
Process: Discover owasp-top-10-scanner, code-quality-enforcer, and security-audit-agent. Extract OWASP vulnerability checks, complexity/duplication metrics, and dependency scanning patterns. Synthesize a multi-layer analysis covering security, quality, and dependencies. Apply to the target codebase (see ${CLAUDE_SKILL_DIR}/references/example-workflows.md).
Adopting documentation skills:
Task: "Generate API documentation."
Process: Find api-documenter, openapi-generator, readme-builder. Extract code parsing, OpenAPI spec generation, and hierarchical documentation structuring. Combine into an end-to-end pipeline: parse endpoints, generate spec, create interactive docs, build README.
Learning automation from DevOps plugins: Task: "Automate deployment process." Process: Search DevOps category for deployment, CI/CD, and Docker plugins. Extract build-test-deploy-verify workflows, parallel job patterns, and service orchestration. Adapt to the user's specific tech stack and infrastructure.
${CLAUDE_SKILL_DIR}/references/how-it-works.md -- detailed five-phase adaptation process${CLAUDE_SKILL_DIR}/references/example-workflows.md -- end-to-end workflow examples${CLAUDE_SKILL_DIR}/references/errors.md -- error handling patterns3a2d27d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.