agentleFS
Sign inStart free
EskyeeEskyee/agentbot-opensource/skills/get-api-docs/SKILL.md

get-api-docs

Skill17 starsChanged 5 months agoMITView on GitHub

Use this skill when you need documentation for a third-party library, SDK, or API before writing code that uses it — for example, "use the OpenAI API", "call the Stripe API", "use the Anthropic SDK", "query Pinecone", or any time the user asks you to write code against an external service and you need current API reference. Fetch the docs with chub before answering, rather than relying on training knowledge.

4 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When you need documentation for a library or API, fetch it with the chub CLI rather than guessing from training data.

    line 13
  2. Distinctive:

    Read the fetched content and use it to write accurate code or answer the question.

    line 35
  3. Distinctive:

    Do not rely on memorized API shapes — use what the docs say.

    line 36
  4. Distinctive:

    After completing the task, if you discovered something not in the doc — a gotcha, workaround, version quirk, or project-specific detail — …

    line 40
  5. Very specific:

    If multiple languages exist and you don't pass --lang, chub will tell you which are available

    line 84

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Get API Docs via chub

When you need documentation for a library or API, fetch it with the chub CLI rather than guessing from training data. This gives you the current, correct API.

Step 1 — Find the right doc ID

chub search "<library name>" --json

Pick the best-matching id from the results (e.g. openai/chat, anthropic/sdk, stripe/api). If nothing matches, try a broader term.

Step 2 — Fetch the docs

chub get <id> --lang py    # or --lang js, --lang ts

Omit --lang if the doc has only one language variant — it will be auto-selected.

Step 3 — Use the docs

Read the fetched content and use it to write accurate code or answer the question. Do not rely on memorized API shapes — use what the docs say.

Step 4 — Annotate what you learned

After completing the task, if you discovered something not in the doc — a gotcha, workaround, version quirk, or project-specific detail — save it so future sessions start smarter:

chub annotate <id> "Webhook verification requires raw body — do not parse before verifying"

Annotations are local, persist across sessions, and appear automatically on future chub get calls. Keep notes concise and actionable. Don't repeat what's already in the doc.

Step 5 — Give feedback

Rate the doc so authors can improve it. Ask the user before sending.

chub feedback <id> up                        # doc worked well
chub feedback <id> down --label outdated     # doc needs updating

Available labels: outdated, inaccurate, incomplete, wrong-examples, wrong-version, poorly-structured, accurate, well-structured, helpful, good-examples.

Quick reference

GoalCommand
List everythingchub search
Find a docchub search "stripe"
Exact id detailchub search stripe/api
Fetch Python docschub get stripe/api --lang py
Fetch JS docschub get openai/chat --lang js
Save to filechub get anthropic/sdk --lang py -o docs.md
Fetch multiplechub get openai/chat stripe/api --lang py
Save a notechub annotate stripe/api "needs raw body"
List noteschub annotate --list
Rate a docchub feedback stripe/api up

Notes

  • chub search with no query lists everything available
  • IDs are <author>/<name> — confirm the ID from search before fetching
  • If multiple languages exist and you don't pass --lang, chub will tell you which are available

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free