Get Api Docs
Fetch up-to-date third-party API and SDK documentation with the chub CLI before your agent writes integration code.
Overview
get-api-docs is an agent skill for the Build phase that fetches current third-party API and SDK documentation through the chub CLI before integration code is written.
Install
npx skills add https://github.com/andrewyng/context-hub --skill get-api-docsWhat is this skill?
- Triggers on requests like OpenAI API, Stripe API, Anthropic SDK, or explicit chub/Context Hub mentions
- Two-step flow: verify chub via chub --help, then follow CLI instructions to fetch the right doc set
- Optional global install via npm install -g @aisuite/chub when Node, network, and package permissions allow
- Positions chub as preferable to generic web search for current API behavior and latest reference pages
- 2-step workflow: chub --help then fetch docs per CLI instructions
Adoption & trust: 879 installs on skills.sh; 13.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to call an external API but your agent’s built-in knowledge may be outdated and ad-hoc web search is unreliable for exact reference details.
Who is it for?
Solo builders starting a new Stripe, OpenAI, Anthropic, or Pinecone integration who want a repeatable doc-fetch step in the agent loop.
Skip if: Purely internal code with no external HTTP/SDK dependencies, or environments where shell, npm, and network installs are permanently blocked without an alternate chub binary.
When should I use this skill?
User asks to use an external API/SDK, wants the latest docs, or mentions chub or Context Hub before integration code.
What do I get? / Deliverables
You have fresh, service-specific documentation aligned with chub’s current CLI behavior so the agent can implement calls against the real API surface.
- Current API/SDK documentation retrieved via chub for the named service
- Agent answers grounded in fetched reference rather than stale training recall
Recommended Skills
Journey fit
External service wiring happens during product build when you connect Stripe, OpenAI, Pinecone, and similar APIs. Integrations is the canonical shelf for tooling that resolves API reference material instead of guessing from stale training data.
How it compares
Use this integration skill instead of guessing API shapes from training data or unstructured web search when Context Hub is available.
Common Questions / FAQ
Who is get-api-docs for?
Indie developers and agent users who regularly wire products to third-party APIs and need authoritative, up-to-date reference material before coding.
When should I use get-api-docs?
During Build integrations when the user names a vendor API/SDK, asks for latest docs, or mentions chub or Context Hub—before writing request handlers, auth, or SDK calls.
Is get-api-docs safe to install?
It may require global npm install and shell/network access; review the Security Audits panel on this page and your org’s package-install policy before enabling it in production agents.
SKILL.md
READMESKILL.md - Get Api Docs
# 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 - Ensure chub exists and get the latest instructions for using it Run ```bash chub --help ``` If this results in an error showing that chub does not exist, then install it first, and run it again. If the environment has node, npm, network access, and package-manager permission, install it as follows: ```bash npm install -g @aisuite/chub ``` ## Step 2 — Find the right documents If there is a conflict, follow the instructions from the output of chub --help since that will be the latest guidance. However, a key command for searching for the right documentation is chub search: ```bash chub search "<keywords>" --json ``` Pick the best-matching `id` from the results (e.g. `openai/chat`, `anthropic/sdk`, `stripe/api`). If nothing matches, try some broader terms. ## Step 3 — Fetch the docs Again, follow the latest instructions from chub --help instead of this if there is a conflict. But a key command for fetching the relevant docs is: ```bash chub get <id> --lang py # or --lang js, --lang ts ``` Remember to include the --lang parameter. ## Step 4 — Use the docs and leave feedback 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. Finally, 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: ```bash 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. Additionally, to help all developers, give feedback on the documentation using chub feedback, following the instructions in chub --help . Do not include secrets, source code, private architecture details, or other sensitive information in feedback comments.