Workflow·Developer Tools & Repos·v1.0.0

API Connector Builder

Build a new API connector or provider by matching the target repo's existing integration pattern exactly.

You say
Install this skill Read the source first Free Written by affaan-m · unverified publisher
Context cost
675 tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 2.7 kBtext throughout, nothing executable
Licence
MITfree to use
Last change
v1.0.0
Servers it uses
Noneruns standalone

What it does

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.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

api

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md2.7 kB · 122 lines
--- 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 ---
9# API Connector Builder
10
11Use this when the job is to add a repo-native integration surface, not just a generic HTTP client.
12
13The point is to match the host repository's pattern:
14
15- connector layout
16- config schema
17- auth model
18- error handling
19- test style
20- registration/discovery wiring
21
22## When to Use
23
24- "Build a Jira connector for this project"
25- "Add a Slack provider following the existing pattern"
26- "Create a new integration for this API"
27- "Build a plugin that matches the repo's connector style"
28
29## Guardrails
30
31- do not invent a new integration architecture when the repo already has one
32- do not start from vendor docs alone; start from existing in-repo connectors first
33- do not stop at transport code if the repo expects registry wiring, tests, and docs
34- do not cargo-cult old connectors if the repo has a newer current pattern
35
36## Workflow
37
38### 1. Learn the house style
39
40Inspect at least 2 existing connectors/providers and map:
41
42- file layout
43- abstraction boundaries
44- config model
45- retry / pagination conventions
46- registry hooks
47- test fixtures and naming
48
49### 2. Narrow the target integration
50
51Define only the surface the repo actually needs:
52
53- auth flow
54- key entities
55- core read/write operations
56- pagination and rate limits
57- webhook or polling model
58
59### 3. Build in repo-native layers
60
61Typical slices:
62
63- config/schema
64- client/transport
65- mapping layer
66- connector/provider entrypoint
67- registration
68- tests
69
70### 4. Validate against the source pattern
71
72The new connector should look obvious in the codebase, not imported from a different ecosystem.
73
74## Reference Shapes
75
76### Provider-style
77
78```text
79providers/
80 existing_provider/
81 __init__.py
82 provider.py
83 config.py
84```
85
86### Connector-style
87
88```text
89integrations/
90 existing/
91 client.py
92 models.py
93 connector.py
94```
95
96### TypeScript plugin-style
97
98```text
99src/integrations/
100 existing/
101 index.ts
102 client.ts
103 types.ts
104 test.ts
105```
106
107## Quality Checklist
108
109- [ ] matches an existing in-repo integration pattern
110- [ ] config validation exists
111- [ ] auth and error handling are explicit
112- [ ] pagination/retry behavior follows repo norms
113- [ ] registry/discovery wiring is complete
114- [ ] tests mirror the host repo's style
115- [ ] docs/examples are updated if expected by the repo
116
117## Related Skills
118
119- backend-patterns
120- mcp-server-patterns
121- github-ops
122
In the file
SKILL.md406 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈70
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
605
on trigger
The instruction body, read only when the skill fires.
0.34%
of a 200k window
Ten skills this size would take about 3% of the window before you open a file.
050k100k150k200k context window

675 tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Small enough to keep loaded permanently without thinking about it.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 2.7 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md2.7 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# API Connector Builder · 675 tokens when loaded npx mcprush@latest skill add affaan-m/api-connector-builder

Writes to .claude/skills/api-connector-builder/ in the current project. Add --global to put it in your home directory instead, for every project.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Version1.0.0
Publishedno release date on file
PriceFree
Referenceaffaan-m/api-connector-builder

Versions

v1.0.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v1.0.0
  • No earlier releases have been published to the marketplace.
Pinning

Put affaan-m/api-connector-builder@1.0.0 in the install command to hold this exact version. Without the suffix you get whatever is current the day you install, and nothing moves under you afterwards.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0