get-api-docs
Skill0 starsChanged 7 months agoMITView on GitHub
Use the chub CLI to fetch curated, versioned API documentation before writing code against external APIs. This prevents hallucinated API calls and ensures correct SDK usage. 20 entries including: airtable, amplitude, anthropic/claude-api, asana, assemblyai, atlassian/confluence, auth0, aws/s3, binance, braintree, chromadb, clerk, cloudflare/workers, cockroachdb, cohere, datadog, deepgram, deepl, deepseek, directus. Run chub search to get the current full list.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- NashEQify/forgetheir own version, first seen Oct 25, 2026
- Eskyee/agentbot-opensourcetheir own version, first seen Oct 13, 2026
- mxyhi/ok-skillstheir own version, first seen Jul 23, 2026
- zizhenchen47-oss/claude-skillstheir own version, first seen Jun 4, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- mxyhi/ok-skills★ 511same name
- Eskyee/agentbot-opensource★ 17same name
- NashEQify/forge★ 2same name
- zizhenchen47-oss/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- aarSkill
- agent-cost-modelSkill
- banana-makerSkill
- bitter-lesson-scorecardSkill
- boot-tax-monitorSkill
- compensating-complexity-auditorSkill
- context-fork-guideSkill
- context-hygieneSkill
- counterargument-stress-testSkill
- dark-code-auditSkill
- executive-briefingSkill
- failure-asymmetrySkill
- failure-postmortemSkill
- file-intelSkill
- geopolitical-signal-enricherSkill
- gh-reviewSkill
- model-routerSkill
- optimize-descriptionSkill
- prompt-rewriterSkill
- skill-auditSkill
- skill-maintenanceSkill
- spec-gap-detectorSkill
- token-burn-auditorSkill
- what-am-i-forgettingSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Use the chub CLI to fetch curated, versioned API documentation before writing code against external APIs.
- Distinctive: line 11
Before implementing code that calls an external API or SDK
- Distinctive: line 12
When unsure about correct API parameters, methods, or patterns
- Distinctive: line 13
When the user asks about how to use a specific service's API
- Very specific: line 48
Annotate: if you discover gaps: chub annotate stripe/api "webhook needs raw body"
- Very specific: line 49
Rate: after use: chub feedback stripe/api up
- Very specific: line 55
Run chub search to get the current full list.
- Distinctive: line 59
Always fetch docs BEFORE writing API integration code, not after
- Very specific: line 60
Use --lang py or --lang js to get language-specific examples
- Very specific: line 61
Use --full sparingly — it returns all reference files and uses more tokens
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Get API Documentation via Context Hub
Use the chub CLI to fetch curated, versioned API documentation before writing code against external APIs. This prevents hallucinated API calls and ensures correct SDK usage.
When to Use
- Before implementing code that calls an external API or SDK
- When unsure about correct API parameters, methods, or patterns
- When the user asks about how to use a specific service's API
Commands
# Search for available docs (no query lists all)
chub search [query]
# Fetch documentation by ID (with language variant)
chub get <id> --lang py # Python docs
chub get <id> --lang js # JavaScript/TypeScript docs
chub get <id> # Default (usually JS)
# Fetch full docs (all reference files)
chub get <id> --lang py --full
# Fetch specific reference file (token-efficient)
chub get <id> --file <filename>
# Add persistent annotation when you discover a gap or workaround
chub annotate <id> "note about what you learned"
# View existing annotations
chub annotate --list
# Rate documentation quality
chub feedback <id> up # Helpful
chub feedback <id> down # Needs improvementWorkflow
- Search for the relevant API:
chub search "stripe" - Fetch language-specific docs:
chub get stripe/api --lang js - Read the output and use it as the source of truth for API calls
- Annotate if you discover gaps:
chub annotate stripe/api "webhook needs raw body" - Rate after use:
chub feedback stripe/api up
Available Docs (as of 2026-03-07)
20 entries including: airtable, amplitude, anthropic/claude-api, asana, assemblyai, atlassian/confluence, auth0, aws/s3, binance, braintree, chromadb, clerk, cloudflare/workers, cockroachdb, cohere, datadog, deepgram, deepl, deepseek, directus.
Run chub search to get the current full list.
Important
- Always fetch docs BEFORE writing API integration code, not after
- Use
--lang pyor--lang jsto get language-specific examples - Use
--fullsparingly — it returns all reference files and uses more tokens - Annotations persist locally across sessions — use them to build knowledge
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

