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

backend-patterns
mcp-server-patterns
github-ops

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

82/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

88

Quality

81

Clarity

85

Completeness

72

Summary

This skill guides an agent to build a new API connector or provider by analyzing and replicating existing integration patterns in the target repository. It emphasizes learning the host codebase's architectural conventions (file layout, config schema, auth model) before implementing, ensuring the new integration fits naturally into the project rather than introducing an alien pattern.

Detected Capabilities

file readcode analysispattern matchingdocumentation reviewtest analysis

Trigger Keywords

Phrases that agents use to match this skill to user intent.

build connectoradd providerapi integrationmatch repo patternplugin implementationintegration architecture

Use Cases

Add a Jira connector following existing repo patterns
Build a Slack provider that mirrors the codebase's integration architecture
Create a new API integration while maintaining repo consistency
Implement a plugin that matches the repository's connector style
Extend a microservice with a native provider layer matching established patterns

Quality Notes

Skill emphasizes learning before building, reducing risk of architectural mismatches
Clear guardrails prevent common anti-patterns (inventing new architectures, cargo-culting)
Workflow is practical and sequences correctly: inspect existing code → define scope → implement in repo layers → validate
Reference shapes are concrete and multi-language (Python, TypeScript), making the skill applicable to diverse codebases
Quality checklist is specific and actionable, with registry/discovery wiring as a key requirement not obvious in vendor docs
No operational guidance on file creation, shell commands, or test execution — skill focuses on analysis and pattern matching
Uses repo-native conventions consistently, avoiding prescriptive one-size-fits-all patterns

Model: claude-haiku-4-5-20251001Analyzed: Sep 9, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

v1.3
Content updated
✦ AINo behavioral changes detected.
2026-09-09
LATEST
v1.2
Content updated
✦ AINo observable behavioral changes between versions.
2026-07-14
View This Version
v1.1
Content updated
✦ AIAdds LICENSE file
2026-04-20
View This Version
v1.0
2026-04-12
View This VersionInitial version

api-connector-builder