技能适配器
- 作者仓库星标 2,235
- 作者仓库 claude-code-plugins-plus-skills
- 领域
- 数据
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @jeremylongshore · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- Docker
- 运行环境要求
- Docker
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# 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)
- `grep` and `find` available on PATH for plugin discovery
- Familiarity with the plugin structure: `commands/*.md`, `agents/*.md`, `skills/*/SKILL.md`, and `scripts/`
## Instructions
1. 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`).
2. Search existing plugins for relevant capabilities using file globbing across `plugins/community/`, `plugins/packages/`, and `plugins/examples/` directories. Match on `plugin.json` descriptions and keyword fields.
3. 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.
4. Synthesize extracted patterns by merging complementary approaches, simplifying where possible, and ensuring compatibility with the current environment.
5. 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.
6. 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
章节与文件索引
按说明文件中的顺序排列。
概述
先决条件
使用说明
输出
错误处理
文件/命令 -> plugins/ · grep · find · commands/*.md · agents/*.md · skills/*/SKILL.md · scripts/ · ${CLAUDE_SKILL_DIR}/references/how-it-works.md
内容校验值 -> 45c7616f4762
当前原文的自动摘译,尚未人工审校。
概述
分析存储库中的现有插件以提取其功能,然后综合这些学习模式并将其应用到当前任务中。充当通用技能变色龙,发现相关插件,提取其方法和方法,并使它们适应新的请求。
先决条件
对
plugins/目录树(社区、包、示例类别)的读取访问权限grep和find可在 PATH 上用于插件发现 熟悉插件结构:commands/*.md、agents/*.md、skills/*/SKILL.md和scripts/使用说明
分析用户的任务,以确定所需的核心功能、领域(安全、开发运营、测试、文档等)以及关键要求或约束(请参阅
${CLAUDE_SKILL_DIR}/references/how-it-works.md)。使用跨plugins/community/、plugins/packages/和plugins/examples/目录的文件全局搜索现有插件的相关功能。匹配plugin.json描述和关键字字段。输出
结构化的适应报告包含: 分析的插件列表以及从每个插件中提取的功能 结合相关模式的综合方法 该方法直接应用于用户的任务 适应技能的任何警告或限制
错误处理
错误 · 原因 · 解决方案 未找到匹配的插件 · 搜索词太窄或未表示域 · 扩大搜索关键字;检查替代类别;回退到通用方法 插件目录无法访问 · 缺少读取权限或路径不正确 · 验证
plugins/目录是否存在并且权限允许遍历 不兼容的模式 · 提取的方法与当前环境冲突 · 优先考虑最相关的插件方法;丢弃冲突的元素