Api Connector Builder

When you need to add a new API integration to a repo that already has several, this keeps you from reinventing the wheel. It walks through learning the existing connector pattern first (file layout, config schema, auth model, test style), then building the new integration to match that house style instead of importing some generic HTTP client approach. The workflow is practical: inspect two existing connectors, map their structure, then build your Jira or Slack integration using the same layers and conventions. The guardrails are the real value here, specifically calling out not to cargo cult old patterns if the repo has evolved, and not to stop at transport code when the repo expects registry wiring and tests too.

skills.sh installs: 5.5K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill api-connector-builder --agent claude-code

Installs into .claude/skills of the current project.

Files

API Connector Builder

Use this when the job is to add a repo-native integration surface, not just a generic HTTP client.

The point is to match the host repository's pattern:

connector layout
config schema
auth model
error handling
test style
registration/discovery wiring

When to Use

"Build a Jira connector for this project"
"Add a Slack provider following the existing pattern"
"Create a new integration for this API"
"Build a plugin that matches the repo's connector style"

Guardrails

do not invent a new integration architecture when the repo already has one
do not start from vendor docs alone; start from existing in-repo connectors first
do not stop at transport code if the repo expects registry wiring, tests, and docs
do not cargo-cult old connectors if the repo has a newer current pattern