通过匹配目标仓库现有的集成模式,构建一个新的API连接器或提供者。适用于在不发明第二种架构的情况下添加一个集成。
当任务需要添加仓库原生的集成接口,而非仅通用 HTTP 客户端时使用此工具。
关键在于匹配宿主仓库的模式:
检查至少 2 个现有连接器/提供商,并映射:
仅定义仓库实际需要的接口:
典型分层:
新连接器应在代码库中显得自然,而非从不同生态导入。
providers/
existing_provider/
__init__.py
provider.py
config.py
integrations/
existing/
client.py
models.py
connector.py
src/integrations/
existing/
index.ts
client.ts
types.ts
test.ts
backend-patternsmcp-server-patternsgithub-opsCopy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/api-connector-builder · pinned to the source commit
git clone https://github.com/affaan-m/ECC.git
cd ECC
git checkout d8409a4b0813771235555e32e3d8046a73988bfa
mkdir -p ".claude/skills/api-connector-builder"
cp -r "docs/zh-CN/skills/api-connector-builder" ".claude/skills/api-connector-builder"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit d8409a4b0813. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.