affaan-m/ECC/docs/zh-CN/skills/api-connector-builder/SKILL.md
api-connector-builder
Use it for engineering tasks; the detail page covers purpose, installation, and practical steps.
- Source repository stars
- 234,327
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-07-27
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
当任务需要添加仓库原生的集成接口,而非仅通用 HTTP 客户端时使用此工具。
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/api-connector-builder"Inspect the Agent Skill "api-connector-builder" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/docs/zh-CN/skills/api-connector-builder/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
使用时机
"为此项目构建 Jira 连接器" "按照现有模式添加 Slack 提供商" "为此 API 创建新集成" "构建符合仓库连接器风格的插件"
"为此项目构建 Jira 连接器""按照现有模式添加 Slack 提供商""为此 API 创建新集成" - 02
约束条件
若仓库已有集成架构,不得自行发明新架构 不得仅从供应商文档入手;应优先参考仓库内现有连接器 若仓库需要注册机制、测试和文档,不得仅停留在传输代码层面 若仓库有更新的当前模式,不得盲目复制旧连接器
若仓库已有集成架构,不得自行发明新架构不得仅从供应商文档入手;应优先参考仓库内现有连接器若仓库需要注册机制、测试和文档,不得仅停留在传输代码层面 - 03
工作流程
文件布局 抽象边界 配置模型 重试/分页约定 注册钩子 测试夹具和命名规范
文件布局抽象边界配置模型
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 56/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 234,327 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | catalog record | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- affaan-m/ECC
- Skill path
- docs/zh-CN/skills/api-connector-builder/SKILL.md
- Commit
- 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
API 连接器构建器
当任务需要添加仓库原生的集成接口,而非仅通用 HTTP 客户端时使用此工具。
关键在于匹配宿主仓库的模式:
- 连接器布局
- 配置模式
- 认证模型
- 错误处理
- 测试风格
- 注册/发现机制
使用时机
- "为此项目构建 Jira 连接器"
- "按照现有模式添加 Slack 提供商"
- "为此 API 创建新集成"
- "构建符合仓库连接器风格的插件"
约束条件
- 若仓库已有集成架构,不得自行发明新架构
- 不得仅从供应商文档入手;应优先参考仓库内现有连接器
- 若仓库需要注册机制、测试和文档,不得仅停留在传输代码层面
- 若仓库有更新的当前模式,不得盲目复制旧连接器
工作流程
1. 学习内部风格
检查至少 2 个现有连接器/提供商,并映射:
- 文件布局
- 抽象边界
- 配置模型
- 重试/分页约定
- 注册钩子
- 测试夹具和命名规范
2. 缩小目标集成范围
仅定义仓库实际需要的接口:
- 认证流程
- 关键实体
- 核心读写操作
- 分页和速率限制
- Webhook 或轮询模型
3. 按仓库原生层次构建
典型分层:
- 配置/模式
- 客户端/传输层
- 映射层
- 连接器/提供商入口
- 注册机制
- 测试
4. 对照源模式验证
新连接器应在代码库中显得自然,而非从不同生态导入。
参考模板
提供商风格
providers/
existing_provider/
__init__.py
provider.py
config.py
连接器风格
integrations/
existing/
client.py
models.py
connector.py
TypeScript 插件风格
src/integrations/
existing/
index.ts
client.ts
types.ts
test.ts
质量检查清单
- [ ] 匹配仓库内现有集成模式
- [ ] 存在配置验证
- [ ] 认证和错误处理明确
- [ ] 分页/重试行为遵循仓库规范
- [ ] 注册/发现机制完整
- [ ] 测试镜像宿主仓库风格
- [ ] 若仓库要求,更新文档/示例
相关技能
backend-patternsmcp-server-patternsgithub-ops
Alternatives
Compare before choosing
affaan-m/ECC
api-connector-builder
Build a new API connector or provider by matching the target repo's existing integration pattern exactly. Use when adding one more integration without inventing a second architecture.
affaan-m/ECC
api-connector-builder
Use it for engineering tasks; the detail page covers purpose, installation, and practical steps.
coreyhaines31/marketingskills
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
event4u-app/agent-config
design-intelligence
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.