Get api docs
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.From its SKILL.md
npx -y skills add naga-k/chub-claude-plugin --skill get-api-docsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.7 KB, as published. Nobody here has run it
Get API Docs via chub
When you need documentation for a library or API, fetch it with chub via npx
rather than guessing from training data. This gives you the current, correct API.
Always use npx --yes @aisuite/chub to run chub — this ensures it's available
without requiring a global install.
Step 1 — Find the right doc ID
npx --yes @aisuite/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
npx --yes @aisuite/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:
npx --yes @aisuite/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
Always rate the doc after using it. This helps authors fix outdated or incorrect docs and prioritize improvements. Include a label and a brief comment explaining what was good or what needs fixing — specific feedback is the most valuable.
npx --yes @aisuite/chub feedback <id> up --label accurate "Clear examples, models are current"
npx --yes @aisuite/chub feedback <id> down --label outdated "Lists gpt-4o as latest but gpt-5.4 is out"
Available labels: outdated, inaccurate, incomplete, wrong-examples,
wrong-version, poorly-structured, accurate, well-structured, helpful,
good-examples.
If you notice the doc has wrong model names, deprecated APIs, missing features, or incorrect code patterns, always leave a downvote with details so it can be fixed.
Quick reference
| Goal | Command |
|---|---|
| List everything | npx --yes @aisuite/chub search |
| Find a doc | npx --yes @aisuite/chub search "stripe" |
| Exact id detail | npx --yes @aisuite/chub search stripe/api |
| Fetch Python docs | npx --yes @aisuite/chub get stripe/api --lang py |
| Fetch JS docs | npx --yes @aisuite/chub get openai/chat --lang js |
| Save to file | npx --yes @aisuite/chub get anthropic/sdk --lang py -o docs.md |
| Fetch multiple | npx --yes @aisuite/chub get openai/chat stripe/api --lang py |
| Save a note | npx --yes @aisuite/chub annotate stripe/api "needs raw body" |
| List notes | npx --yes @aisuite/chub annotate --list |
| Rate a doc | npx --yes @aisuite/chub feedback stripe/api up |
Notes
- All commands use
npx --yes @aisuite/chub— no global install required searchwith 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