Skip to main content
affpapa.org
RU EN
skill Claude Code CX Codex Cursor GitHub Copilot

api-connector-builder — Claude Code skill: install

This skill builds an API connector by following the target repository’s existing integration pattern. Use it when a new provider should fit the current architecture.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add affaan-m/ECC --skill api-connector-builder -a claude-code
Open on GitHub

What api-connector-builder does

api-connector-builder is for adding a connector or provider that looks native to the host repository. It starts by reviewing at least 2 existing integrations, then maps their file layout, configuration model, authentication, error handling, registration hooks, and test style.

The work is split into repository-shaped layers: config and schema, client or transport, data mapping, connector entrypoint, registration, and tests. It also follows local conventions for retries, pagination, fixtures, and naming. Documentation and examples are updated when the repository expects them.

Install this skill when the codebase already has a clear integration pattern to follow. A repository without that pattern still needs a separate architecture decision.

What it helps with

  • add a Jira connector that matches the project
  • create a Slack provider with repository registration
  • build a new integration for an API
  • follow existing retry and pagination conventions
  • cover a connector with repo-style tests

Example prompts for the agent

  • “Build a Jira connector for this project”
  • “Add a Slack provider following the existing pattern”
  • “Create a new integration for this API”

How to install api-connector-builder

1Skills CLI (Vercel)

npx skills add affaan-m/ECC --skill api-connector-builder -a claude-code

2Manually: put the files in place

~/.claude/skills/api-connector-builder/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/api-connector-builder/

From the same set146

The whole set →
video-editing affaan-m AI-assisted workflow for editing, trimming, and enriching real footage. Connects raw recordings with FFmpeg cuts, Remotion overlays, and ElevenLabs voiceovers. Claude Code CX Codex Cursor +1 6,500installs docker-patterns affaan-m A skill with Dockerfile and Docker Compose patterns: local dev stacks, networking, volumes, container hardening. Claude Code CX Codex Cursor +1 6,300installs frontend-patterns affaan-m A skill for React and Next.js work: component patterns, state, data fetching, and render performance. Use it when building or reviewing UI. Claude Code CX Codex Cursor +1 5,900installs backend-patterns affaan-m A skill with backend patterns for Node.js, Express and Next.js API routes: layering, caching, transactions, error handling. Claude Code CX Codex Cursor +1 5,900installs coding-standards affaan-m Baseline cross-project coding conventions for naming, immutability, and clean code principles. Useful for code reviews and refactoring. Claude Code CX Codex Cursor +1 5,600installs api-design affaan-m Provides REST API design standards covering resource naming, status codes, pagination, and error payloads. Use it when creating or auditing API contracts. Claude Code CX Codex Cursor +1 5,500installs rust-testing affaan-m A skill for writing Rust tests: unit, integration, async, property-based, mocks and coverage. Useful when the project runs on TDD. Claude Code CX Codex Cursor +1 5,500installs laravel-security affaan-m This skill reviews Laravel authentication, Eloquent safety, CSRF, XSS, APIs, and production settings. Use it for security reviews or deployment checks. Claude Code CX Codex Cursor +1 5,400installs

Similar

build-mcpb official Anthropic Packages a local MCP server with Node or Python so users can install it without setting up a runtime first. Claude Code 6,229installs stripe-best-practices stripe This skill guides Stripe API choices, payment flows, and integration security. Use it when building, testing, or reviewing Stripe code. Claude Code CX Codex Cursor +1 97,800installs solana-dev Solana Foundation Skill for building Solana dApps, writing Anchor smart contracts, managing wallets and transactions. Covers setup, testing, and devnet deployment end-to-end. Claude Code CX Codex Cursor +1 98,300installs microsoft-code-reference official github Checks Microsoft APIs and SDK code against official docs, finds working samples, and helps debug Azure and .NET issues. GitHub Copilot 14,251installs mcp-builder official anthropics This skill walks through building an MCP server in TypeScript or Python, from reading the protocol spec to writing tests and evaluation questions. Claude Code Claude.ai 130,949installs google-agents-cli-adk-code official Google A reference skill for building ADK agents with tools, callbacks, state, and workflows. Use it when an agent project needs concrete API patterns or code examples. Claude Code CX Codex Cursor +1 511,400installs lark-im larksuite This skill lets an agent work with Lark IM messages, chats, files, and interactive cards. Use it when coding tasks need access to team conversations. Claude Code CX Codex Cursor +1 472,300installs lark-event larksuite Listens to Lark/Feishu events and streams them as NDJSON. Use it for bots, message processing, and long-running subscribers. Claude Code CX Codex Cursor +1 466,200installs

Questions about api-connector-builder

How do I install api-connector-builder in Claude Code?

Run npx skills add affaan-m/ECC --skill api-connector-builder -a claude-code. The skill file is placed at ~/.claude/skills/api-connector-builder/SKILL.md.

What does api-connector-builder do?

It helps build an API connector or provider around the repository’s current integration pattern. The workflow covers configuration, authentication, error handling, registration, and tests.

Which platforms support api-connector-builder?

The skill supports Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.

Source text

SKILL.md · MIT 
---
name: api-connector-builder
description: 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.
metadata:
  version: "1.0.0"
  origin: ECC direct-port adaptation
---

# 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

```text
providers/
  existing_provider/
    __init__.py
    provider.py
    config.py
```

### Connector-style

```text
integrations/
  existing/
    client.py
    models.py
    connector.py
```

### TypeScript plugin-style

```text
src/integrations/
  existing/
    index.ts
    client.ts
    types.ts
    test.ts
```

## 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`

© affaan-m · MIT · affaan-m/ECC

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor