Agent skill · software engineering · affaan-m
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.
Why this skill is useful
Provides specific patterns and workflows for building API connectors that align with existing repository structures, which the AI may not reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
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 Workflow 1. Learn the house style Inspect at least 2 existing connectors/providers and map: file layout abstraction boundaries config model retry / pagination conventions registry hooks test fixtures and naming 2. Narrow the target integration Define only the surface the repo actually needs: auth flow key entities core read/write operations pagination and rate limits webhook or polling model 3. Build in repo-native layers Typical slices: config/schema client/transport mapping layer connector/provider entrypoint registration tests 4. Validate against the source pattern The new connector should look obvious in the codebase, not imported from a different ecosystem. Reference Shapes Provider-style Connector-style TypeScript plugin-style Quality Checklist [ ] matches an existing in-repo integration pattern [ ] config validation exists [ ] auth and error handling are explicit [ ] pagination/retry behavior follows repo norms [ ] registry/discovery wiring is complete [ ] tests mirror the host repo's style [ ] docs/examples are updated if expected by the repo Related Skills backend-patterns mcp-server-patterns github-ops
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/api-connector-builder--6dc591