fetching-library-docs
Token-efficient library API documentation fetcher using Context7 MCP with 77% token savings. Fetches code examples, API references, and usage patterns for published libraries (React, Next.js, Prisma, etc). Use when users ask "how do I use X library", need code examples, want API syntax, or are learning a framework's official API. Triggers: "Show me React hooks", "Prisma query syntax", "Next.js routing API". NOT for exploring repo internals/source code (use researching-with-deepwiki) or local files.
npx skills add majiayu000/claude-skill-registry --skill fetching-library-docs-abdullahmalik17-hacathan-2-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Context7 Efficient Documentation Fetcher Fetch library documentation with automatic 77% token reduction via shell pipeline. ## Quick Start **Always use the token-efficient shell pipeline:** ```bash # Automatic library resolution + filtering bash scripts/fetch-docs.sh --library <library-name> --topic <topic> # Examples: bash scripts/fetch-docs.sh --library react --topic useState bash scripts/fetch-docs.sh --library nextjs --topic routing bash scripts/fetch-docs.sh --library prisma --topic queries ``` **Result:** Returns ~205 tokens instead of ~934 tokens (77% savings). ## Standard Workflow For any documentation request, follow this workflow: ### 1. Identify Library and Topic Extract from user query: - **Library:** React, Next.js, Prisma, Express, etc. - **Topic:** Specific feature (hooks, routing, queries, etc.) ### 2. Fetch with Shell Pipeline ```bash bash scripts/fetch-docs.sh --library <library> --topic <topic> --verbose ``` The `--verbose` flag shows token savings statistics. ### 3. Use Filtered Output The script automatically: - Fetches full documentation (934 tokens, stays in subprocess) - Filters to code examples + API signatures + key notes - Returns only essential content
- Quick Start
- Standard Workflow
- 1. Identify Library and Topic
- 2. Fetch with Shell Pipeline
- 3. Use Filtered Output
- Parameters
- Basic Usage
- Mode Selection
- Common Library IDs
- Workflow Patterns
- Pattern 1: Quick Code Examples
- Pattern 2: Learning New Library
- Pattern 3: Specific Feature Lookup
- Pattern 4: Deep Exploration
Automatic library resolution + filtering bash scripts/fetch-docs.sh --library <library-name> --topic <topic> bash scripts/fetch-docs.sh --library react --topic useState bash scripts/fetch-docs.sh --library nextjs --topic routing bash scripts/fetch-docs.sh --library prisma --topic queries bash scripts/fetch-docs.sh --library <library> --topic <topic> --verbose bash scripts/fetch-docs.sh [OPTIONS] bash scripts/fetch-docs.sh --library react --topic useState --verbose Step 1: Get overview bash scripts/fetch-docs.sh --library prisma --topic "getting started" --mode info
What does the fetching-library-docs skill do?
Token-efficient library API documentation fetcher using Context7 MCP with 77% token savings. Fetches code examples, API references, and usage patterns for published libraries (React, Next.js, Prisma, etc). Use when users ask "how do I use X library", need code examples, want API syntax, or are learning a framework's official API. Triggers: "Show me React hooks", "Prisma query syntax", "Next.js routing API". NOT for exploring repo internals/source code (use researching-with-deepwiki) or local files.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill fetching-library-docs-abdullahmalik17-hacathan-2-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.