Api Connector Builder

When you need to add another integration to a codebase that already has a connector pattern, this skill keeps you from inventing a second architecture. It walks you through learning the house style from existing providers, then building the new connector to match: same file layout, config schema, auth model, error handling, and test conventions. The workflow is inspect two existing connectors, map their structure, then build in those same layers. It's opinionated about one thing: start from what's already in the repo, not vendor docs or your favorite HTTP client pattern. Useful when you're adding Slack to a project that already has three other integrations and you want the fourth to look like it belongs.

skills.sh installs: 3.6K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --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