---
id: daily-api-connector-builder
name: "api-connector-builder"
url: https://skills.yangsir.net/skill/daily-api-connector-builder
author: affaan-m
domain: ai-backend-engineering
tags: ["backend", "api-integration", "api-development", "typescript", "automation"]
install_count: 4300
rating: 4.40 (15 reviews)
github: https://github.com/affaan-m/everything-claude-code
---

# api-connector-builder

> 为代码库添加原生API集成，遵循项目的连接器布局、配置架构、认证模型和错误处理模式

**Stats**: 4,300 installs · 4.4/5 (15 reviews)

## Before / After 对比

### API集成开发

**Before**:

手动研究现有项目的API集成模式，反复试错配置格式和认证流程，与项目风格不一致，需要多次重构才能合并

**After**:

自动分析项目的连接器模式，生成符合项目风格的API集成代码，包括配置schema、认证处理和错误响应，一次通过率大幅提升

| Metric | Before | After | Change |
|---|---|---|---|
| 开发时间 | 240分钟 | 60分钟 | -75% |
| 代码风格一致性 | 55% | 92% | +67% |

## Readme

# api-connector-builder

# 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

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

```

### Connector-style

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

```

### TypeScript plugin-style

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

Weekly Installs495Repository[affaan-m/everyt…ude-code](https://github.com/affaan-m/everything-claude-code)GitHub Stars156.2KFirst Seen9 days agoSecurity Audits[Gen Agent Trust HubPass](/affaan-m/everything-claude-code/api-connector-builder/security/agent-trust-hub)[SocketPass](/affaan-m/everything-claude-code/api-connector-builder/security/socket)[SnykPass](/affaan-m/everything-claude-code/api-connector-builder/security/snyk)Installed oncodex466opencode450gemini-cli447cursor447antigravity446kimi-cli446

---
*Source: https://skills.yangsir.net/skill/daily-api-connector-builder*
*Markdown mirror: https://skills.yangsir.net/api/skill/daily-api-connector-builder/markdown*