skill-adapter
- Repo stars 2,235
- Author updated Live
- Author repo claude-code-plugins-plus-skills
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @jeremylongshore · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Docker
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skill-adapter
description: 'Execute analyzes existing plugins to extract their capabilities, then Analyzes existing plugins…
category: data
runtime: Docker
---
# skill-adapter output preview
## PART A: Task fit
- Use case: 'Execute analyzes existing plugins to extract their capabilities, then Analyzes 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 ….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Prerequisites / Instructions” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “'Execute analyzes existing plugins to extract their capabilities, then Analyzes 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 …”.
- **02** When the source has headings, the agent prioritizes “Overview / Prerequisites / Instructions” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Overview / Prerequisites / Instructions”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-adapter
description: 'Execute analyzes existing plugins to extract their capabilities, then Analyzes existing plugins…
category: data
source: jeremylongshore/claude-code-plugins-plus-skills
---
# skill-adapter
## When to use
- 'Execute analyzes existing plugins to extract their capabilities, then Analyzes existing plugins in the repository to…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / Prerequisites / Instructions” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-adapter" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / Prerequisites / Instructions
rules -> SKILL.md triggers / order / output contract
runtime -> Docker | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Skill Adapter
Overview
Analyzes 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.
Prerequisites
- Read access to the
plugins/directory tree (community, packages, examples categories) grepandfindavailable on PATH for plugin discovery- Familiarity with the plugin structure:
commands/*.md,agents/*.md,skills/*/SKILL.md, andscripts/
Instructions
- Analyze the user's task to identify the core capability needed, the domain (security, devops, testing, documentation, etc.), and key requirements or constraints (see
${CLAUDE_SKILL_DIR}/references/how-it-works.md). - Search existing plugins for relevant capabilities using file globbing across
plugins/community/,plugins/packages/, andplugins/examples/directories. Match onplugin.jsondescriptions and keyword fields. - For each relevant plugin discovered, extract capabilities from its components:
- Commands (
commands/*.md): read content, extract approach and input/output patterns. - Agents (
agents/*.md): understand roles, decision-making patterns, expertise areas. - Skills (
skills/*/SKILL.md): read instructions, extract core capability and tool usage. - Scripts (
scripts/*.sh,*.py): analyze logic, identify reusable patterns and error handling.
- Commands (
- Synthesize extracted patterns by merging complementary approaches, simplifying where possible, and ensuring compatibility with the current environment.
- Apply the adapted skill to the user's task, following the learned methodology while adjusting syntax, tools, and output format to match the current context.
- Report which plugins were consulted, what patterns were extracted, and how they were adapted for the current task.
Output
A structured adaptation report containing:
- List of plugins analyzed and capabilities extracted from each
- The synthesized approach combining relevant patterns
- The direct application of that approach to the user's task
- Any caveats or limitations of the adapted skill
Error Handling
| 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 |
Examples
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.
Resources
${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 patterns
Decide Fit First
Design Intent
How To Use It
Boundaries And Review