← ClaudeAtlas

api-skilllisted

Turn a REST API into an agent skill instead of an MCP server. Use when asked to give an agent access to an API, to "wrap" an API, or to decide between a skill and an MCP server for one.
techhorizonlabs/gearlist · ★ 2 · API & Backend · score 58
Install: claude install-skill techhorizonlabs/gearlist
# Turn an API into a skill Most APIs an agent needs are a few calls and one key. A skill covers that with a page of instructions. Build an MCP server only when the job outgrows the page. ## Skill or MCP server Build a skill when: - the agent uses a handful of endpoints; - it signs in with one key, or none; - each call stands alone, with no session to keep; - one person or one team uses it. Build an MCP server when: - each user signs in with their own account (OAuth); - there are many tools, or long-running and streaming calls; - several agents or apps share it and need separate permissions. Start with a skill. Move to an MCP server when the instructions pass about a page, or users need their own sign-in. ## Steps 1. Read the official API docs. Note the base URL, how it signs in, rate limits and terms of use. 2. Keep the key in an environment variable or the user's secret store. It never goes in the skill file, a prompt or a chat. 3. Write `SKILL.md`: - frontmatter with a `name` and a `description` that names the words a user would say; - what the API gives, in one line; - how it signs in and which variable holds the key; - the three to five calls the agent will actually make, each with an example request and the response fields to read; - limits, error codes and what to do on each; - what not to do: writes, deletes or spend without a human's yes. 4. Add a short script under `scripts/` only when requests need signing, paging or parsing. 5. Run each exa