Back to browse

affaan-m/ECC

api-connector-builder

通过匹配目标仓库现有的集成模式，构建一个新的API连接器或提供者。适用于在不发明第二种架构的情况下添加一个集成。

56Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/api-connector-builder"
Automated source guide

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Turn api-connector-builder's source instructions into a guide you can follow

According to the pinned SKILL.md from affaan-m/ECC: 当任务需要添加仓库原生的集成接口，而非仅通用 HTTP 客户端时使用此工具。

npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/api-connector-builder"
Check the pinned source

Best fit

  • 通过匹配目标仓库现有的集成模式，构建一个新的API连接器或提供者。适用于在不发明第二种架构的情况下添加一个集成。

Bring this context

  • A concrete task that matches the documented purpose of api-connector-builder.
  • The files, examples, or context the task depends on.
  • Your constraints, target environment, and definition of done.

Expected outputs

  • A result that follows the pinned api-connector-builder instructions.
  • A concise record of assumptions, inputs used, and unresolved questions.
  • A final check against the source workflow and relevant permission signals.

Key source sections

Read api-connector-builder through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

使用时机

"为此项目构建 Jira 连接器" "按照现有模式添加 Slack 提供商" "为此 API 创建新集成" "构建符合仓库连接器风格的插件"

SKILL.md · 使用时机
"为此项目构建 Jira 连接器""按照现有模式添加 Slack 提供商""为此 API 创建新集成"
02

约束条件

若仓库已有集成架构，不得自行发明新架构 不得仅从供应商文档入手；应优先参考仓库内现有连接器 若仓库需要注册机制、测试和文档，不得仅停留在传输代码层面 若仓库有更新的当前模式，不得盲目复制旧连接器

SKILL.md · 约束条件
若仓库已有集成架构，不得自行发明新架构不得仅从供应商文档入手；应优先参考仓库内现有连接器若仓库需要注册机制、测试和文档，不得仅停留在传输代码层面
03

工作流程

文件布局 抽象边界 配置模型 重试/分页约定 注册钩子 测试夹具和命名规范

SKILL.md · 工作流程
文件布局抽象边界配置模型
04

1. 学习内部风格

文件布局 抽象边界 配置模型 重试/分页约定 注册钩子 测试夹具和命名规范

SKILL.md · 1. 学习内部风格
文件布局抽象边界配置模型
05

2. 缩小目标集成范围

认证流程 关键实体 核心读写操作 分页和速率限制 Webhook 或轮询模型

SKILL.md · 2. 缩小目标集成范围
认证流程关键实体核心读写操作

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Task-start prompt

Confirm source fit, inputs, and outputs before acting.

Use api-connector-builder to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.

Source-guided execution

Make the Agent explicitly follow the key extracted sections.

Apply the pinned api-connector-builder source to [task]. Pay particular attention to these source sections: “使用时机”, “约束条件”, “工作流程”, “1. 学习内部风格”, “2. 缩小目标集成范围”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].

Result-review prompt

Check omissions, permissions, and source drift before delivery.

Review the current api-connector-builder result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.

Output checklist

Verify each item before delivery

The task matches the purpose documented in the SKILL.md.

The source section “使用时机” has been checked.

The source section “约束条件” has been checked.

The source section “工作流程” has been checked.

The source section “1. 学习内部风格” has been checked.

Inputs, constraints, and acceptance criteria are explicit.

Unverified facts, compatibility, and outcome claims are clearly marked.

Any file, command, network, or data action has been reviewed.

Choose a different workflow

When another Skill is the better fit

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.

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

api-connector-builder

ターゲット リポジトリの既存統合パターンに正確に一致する新しい API コネクターまたはプロバイダーを構築します。2 番目のアーキテクチャを発明せずに、1 つ以上の統合を追加するときに使用します。

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

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

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does api-connector-builder do?

当任务需要添加仓库原生的集成接口，而非仅通用 HTTP 客户端时使用此工具。

How do I start using api-connector-builder?

The catalog detected this source-specific install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/api-connector-builder". Inspect the command and pinned source before running it.

Which Agent platforms does it declare?

No dedicated Agent platform is declared in the pinned source record.

Repository stars
234,327
Repository forks
35,711
Quality
56/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

56/100
Documentation17/30
Specificity7/25
Maintenance20/20
Trust signals12/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

api-connector-builder by affaan-m

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.

api-connector-builder by affaan-m

ターゲット リポジトリの既存統合パターンに正確に一致する新しい API コネクターまたはプロバイダーを構築します。2 番目のアーキテクチャを発明せずに、1 つ以上の統合を追加するときに使用します。

ab-testing by coreyhaines31

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

design-intelligence by event4u-app

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.

existing-ui-audit by event4u-app

Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min

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-patterns
  • mcp-server-patterns
  • github-ops
Source repo
affaan-m/ECC
Skill path
docs/zh-CN/skills/api-connector-builder/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected