> 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.
curl "https://skillshub.wtf/mxyhi/ok-skills/get-api-docs?format=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
| 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
> related_skills --same-repo
> yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
> xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my
> vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
> test-driven-development
Use when implementing any feature or bugfix, before writing implementation code