API Connector Builder
Add a new API integration that matches the repo's existing connector style instead of inventing a second architecture.
- What
- Add a new API integration that matches the repo's existing connector style instead of inventing a second architecture.
- Cost
- Free
- Needs
- Use "API Connector Builder" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a method for adding one more integration to a codebase without inventing a second architecture. The skill starts from the host repository's own habits: it inspects at least two existing connectors to map the file layout, config schema, auth model, retry and pagination conventions, error handling, registry wiring, and test style, then defines only the integration surface the repo actually needs (auth flow, key entities, core read/write operations, rate limits, webhook or polling model). The build follows repo-native slices (config, client/transport, mapping layer, provider entrypoint, registration, tests) with a quality checklist, and the guardrails push back against the two classic failure modes: inventing a new integration architecture when the repo already has one, and cargo-culting an outdated connector when a newer pattern exists. Reference shapes are given for provider-style (Python), connector-style, and TypeScript plugin layouts, plus related skills for backend patterns and MCP servers. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure guidance, nothing to install; it assumes the target repo already has connectors to learn from, otherwise there is no house style to match. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
Use "API Connector Builder" with your Muse. Prerequisites: the Muse app (mobile or web), and a repository that already has at least one integration or connector to learn the house style from. Pure guidance skill, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/api-connector-builder/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "I need to add a [Jira / Slack / ...] connector to [repo path or description]. First map the existing connector pattern, then propose the new integration surface." 3. Ask Muse to walk through the workflow: learn the house style from 2 existing connectors, narrow the target surface (auth, entities, operations, pagination, webhooks), then build in repo-native slices with the quality checklist. Tip: the guardrail that matters most is "do not invent a new architecture when the repo already has one". If Muse proposes a fresh abstraction, ask it to point at the existing pattern it matches. Safety: a skill is plain-text instructions; it runs nothing by itself. Review any code before committing it, never paste secrets into a chat, and review anything Muse proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.