How do I install the Get API Docs skill?

Run npx skillmds@latest add m2ai-portfolio/get-api-docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Get API Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Get API Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Get API Docs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Get API Docs?

m2ai-portfolio (@m2ai-portfolio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Get API Docs by m2ai-portfolio — Agent Skill

Name: Get API Docs
Author: m2ai-portfolio

Get API Docs

Fetch curated, versioned API documentation through the `chub` CLI before writing code against an external API or SDK, so calls are checked against real docs instead of recalled from memory. Use before implementing anything that calls an external API, when unsure of the correct parameters, methods, or patterns, when a model name or endpoint needs verifying, or when the user asks how to use a specific service's API.

File contents

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 improvement

Workflow

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 py or --lang js to get language-specific examples
Use --full sparingly — it returns all reference files and uses more tokens
Annotations persist locally across sessions — use them to build knowledge

---name: get-api-docsdescription: Fetch curated, versioned API documentation through the `chub` CLI before writing code against an external API or SDK, so calls are checked against real docs instead of recalled from memory. Use before implementing anything that calls an external API, when unsure of the correct parameters, methods, or patterns, when a model name or endpoint needs verifying, or when the user asks how to use a specific service's API.---# Skill: Get API Documentation via Context HubUse 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```bash# Search for available docs (no query lists all)chub search [query]# Fetch documentation by ID (with language variant)chub get <id> --lang py # Python docschub get <id> --lang js # JavaScript/TypeScript docschub 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 workaroundchub annotate <id> "note about what you learned"# View existing annotationschub annotate --list# Rate documentation qualitychub feedback <id> up # Helpfulchub feedback <id> down # Needs improvement```## Workflow1. **Search** for the relevant API: `chub search "stripe"`2. **Fetch** language-specific docs: `chub get stripe/api --lang js`3. **Read** the output and use it as the source of truth for API calls4. **Annotate** if you discover gaps: `chub annotate stripe/api "webhook needs raw body"`5. **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 py` or `--lang js` to get language-specific examples- Use `--full` sparingly — it returns all reference files and uses more tokens- Annotations persist locally across sessions — use them to build knowledge

Frequently asked questions