Individual skill

api-connector-builder

Use when writing a client for someone else's REST or GraphQL API: auth flow choice and token refresh, pagination to exhaustion, retry-with-jitter on transient failures only, rate-limit-aware throttling. NOT inbound callbacks (that is `webhooks`), NOT chaining services (that is `automation-flows`), NOT designing your own API (that is `api-design`).

skills/api-connector-builder/SKILL.md

Read pinned source

Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
561
Repository last updated
Nov 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# API connector builder — auth, pagination, retries, rate limits

You are writing a client for **someone else's** HTTP API. You do not own the
contract; you obey it. The deliverable is one typed connector module per vendor
that authenticates, walks the whole result set, retries only transient failures
with backoff, and stays under the rate limit without getting the key banned.
One connector = one vendor: mixed clients tangle two auth schemes and two
rate-limit budgets into something no one can reason about.

Four pillars, every time: **auth, pagination, retries, rate limits.** If your
connector skips any one of them it works in the demo and breaks in production —
on page 2, on token expiry, on the first 429, or on a flaky network.

## Step 0 — read the contract