
API Connector Builder
Builds new API integrations that match a repository's existing connector patterns
- Repository
- affaan-m/ECC
- Stars
- 295,127
- Licence
- MIT
- Files
- 1 file
What it does
When asked to add a connector or provider for an external service (such as Jira or Slack), the agent first studies at least two existing integrations in your codebase and then builds the new one using the same file layout, config style, auth approach, error handling, tests and registration steps. It is designed to avoid inventing a second integration architecture, and it starts from in-repo examples rather than vendor documentation alone.
Great for
- Developers maintaining a codebase that already has several third-party integrations or plugins
- Teams who want a new connector to look native to their existing code rather than a generic HTTP client
- Engineers adding a new provider who want a checklist covering config, tests and registry wiring
Skip it if
- Projects with no existing integration pattern, since the skill depends on examples in the repo to copy (it offers no independent architecture guidance)
- Quick one-off scripts calling a single API, where a generic HTTP client would be simpler
- Anyone expecting it to run or verify the connector automatically: the file itself contains only guidance and no scripts
Try asking
- “Build a Jira connector for this project that follows the style of our existing integrations”
- “Add a Slack provider matching the existing provider pattern in this repo”
- “Create a new integration for this API, mirroring how the other connectors are structured and tested”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
api-connector-builder.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip api-connector-builder.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip api-connector-builder.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Point the agent at the repo and name two existing connectors to imitate so it maps the house style first
- Give it the target API's required scope: auth flow, key entities and whether it needs webhooks or polling
- Review the generated registration and test files against the repo's own conventions before merging
What's inside
- SKILL.md
Redistributed unmodified from affaan-m/ECC under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.