explainx.ainewsletter3.4k
Backend

get-api-docs▌

andrewyng/context-hub · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/andrewyng/context-hub --skill get-api-docs
0 commentsdiscussion
summary

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.
skill.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

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.

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 search with 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
how to use get-api-docs

How to use get-api-docs on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add get-api-docs
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/andrewyng/context-hub --skill get-api-docs

The skills CLI fetches get-api-docs from GitHub repository andrewyng/context-hub and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/get-api-docs

Reload or restart Cursor to activate get-api-docs. Access the skill through slash commands (e.g., /get-api-docs) or your agent's skill management interface.

⚠

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

✓

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

✓

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

✓

Improve work quality by 30-40% with less effort

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client with skill support
  • ›Clear understanding of task or problem to solve
  • ›Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • ⚠Expecting perfect results without iteration
  • ⚠Not providing enough context in prompts
  • ⚠Using skill for tasks outside its intended scope
  • ⚠Accepting outputs without review and validation

Best Practices▌

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • −Don't use without understanding skill limitations
  • −Don't skip validation of outputs
  • −Don't share sensitive information in prompts
  • −Don't expect skill to replace human judgment

💡 Pro Tips

  • ★Be specific about desired format and style
  • ★Ask for multiple options to choose from
  • ★Request explanations to understand reasoning
  • ★Combine AI efficiency with human expertise

When to Use This▌

✓ 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.

Learning Path▌

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.6★★★★★59 reviews
  • ★★★★★Alexander Khan· Dec 28, 2024

    get-api-docs reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★James Abebe· Dec 24, 2024

    get-api-docs has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Charlotte Lopez· Dec 24, 2024

    Useful defaults in get-api-docs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Nikhil Johnson· Dec 20, 2024

    get-api-docs fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Kwame Robinson· Dec 16, 2024

    We added get-api-docs from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Dhruvi Jain· Dec 4, 2024

    We added get-api-docs from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Li Martin· Dec 4, 2024

    Solid pick for teams standardizing on skills: get-api-docs is focused, and the summary matches what you get after install.

  • ★★★★★Oshnikdeep· Nov 23, 2024

    Useful defaults in get-api-docs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Mei Kim· Nov 23, 2024

    I recommend get-api-docs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Alexander Gonzalez· Nov 19, 2024

    Registry listing for get-api-docs matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 59

1 / 6