get-api-docs
Retrieves current library docs to prevent guessing API shapes.
Install
mkdir -p .claude/skills/get-api-docs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12633" && unzip -o skill.zip -d .claude/skills/get-api-docs && rm skill.zipInstalls to .claude/skills/get-api-docs
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Search for API documentation using keywords.
- →Fetch documentation for a specific API ID.
- →Specify the language for fetched documentation.
- →Annotate documentation with custom notes.
- →Rate the quality of API documentation.
How it works
The skill uses the `chub` CLI to search for and retrieve current API documentation, allowing for language specification and local annotations.
Inputs & outputs
When to use get-api-docs
- →Getting API docs
- →Fetching SDK references
- →Annotating library gotchas
About this skill
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
| Goal | Command |
|---|---|
| List everything | chub search |
| Find a doc | chub search "stripe" |
| Exact id detail | chub search stripe/api |
| Fetch Python docs | chub get stripe/api --lang py |
| Fetch JS docs | chub get openai/chat --lang js |
| Save to file | chub get anthropic/sdk --lang py -o docs.md |
| Fetch multiple | chub get openai/chat stripe/api --lang py |
| Save a note | chub annotate stripe/api "needs raw body" |
| List notes | chub annotate --list |
| Rate a doc | chub feedback stripe/api up |
Notes
chub 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
When not to use it
- →When relying on outdated training data for API information.
- →When the user asks for information not related to external APIs or SDKs.
Limitations
- →Annotations are local and persist across sessions.
- →Doc IDs are in `<author>/<name>` format.
How it compares
This skill fetches current API documentation directly, preventing reliance on potentially outdated training data, unlike manual searches or memory.
Compared to similar skills
get-api-docs side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| get-api-docs (this skill) | 0 | 5mo | Review | Beginner |
| protocolsio-integration | 1 | 2mo | Review | Intermediate |
| openapi-spec-generation | 22 | 2mo | No flags | Intermediate |
| microsoft-code-reference | 7 | 5mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
protocolsio-integration
K-Dense-AI
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
openapi-spec-generation
wshobson
Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.
microsoft-code-reference
github
Look up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs—to find the right method, check parameters, get working examples, or troubleshoot errors. Catches hallucinated methods, wrong signatures, and deprecated patterns by querying official docs.
openai-knowledge
openai
Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.
agent-docs-api-openapi
ruvnet
Agent skill for docs-api-openapi - invoke with $agent-docs-api-openapi
openai-docs
openai
Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits); prioritize OpenAI docs MCP tools and restrict any fallback browsing to official OpenAI domains.