When you need documentation for a library or API, fetch it with the chub CLI
Works with
rather than guessing from training data. This gives you the current, correct API.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionget-api-docsExecute the skills CLI command in your project's root directory to begin installation:
Fetches get-api-docs from andrewyng/context-hub and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate get-api-docs. Access via /get-api-docs in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
12.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
12.6K
stars
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.
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.
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.
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.
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.
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.
chub feedback <id> up --label accurate "Clear examples, models are current"
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.
| 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 |
chub search with no query lists everything available<author>/<name> — confirm the ID from search before fetching--lang, chub will tell you which are availablePrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
langchain-ai/deepagents
jwynia/agent-skills
mindrally/skills
github/awesome-copilot
kostja94/marketing-skills
wispbit-ai/skills
get-api-docs reduced setup friction for our internal harness; good balance of opinion and flexibility.
get-api-docs has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in get-api-docs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
get-api-docs fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added get-api-docs from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added get-api-docs from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: get-api-docs is focused, and the summary matches what you get after install.
Useful defaults in get-api-docs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend get-api-docs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for get-api-docs matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 59