| name | library-docs |
| description | Fetch real-time, official library docs instead of relying on stale memory. Use whenever implementing against external libraries/frameworks/packages. |
| allowed-tools | mcp__context7__resolve-library-id, mcp__context7__get-library-docs |
| metadata | {"internal":true} |
Library Documentation Research
Purpose
Retrieve up-to-date docs from authoritative sources before coding against third-party APIs.
Core Workflow
- Resolve library id with
mcp__context7__resolve-library-id
- Choose best match by name relevance, trust score, and snippet coverage
- Fetch docs with
mcp__context7__get-library-docs
- Extract concrete API usage patterns and examples relevant to the task
Retrieval Guidance
- Use focused
topic queries when possible ("routing", "migrations", "cli options")
- Start around 5000 tokens; increase for broad API or migration work
- Prefer official library/project docs over blogs
When to Use
Use this skill first for:
- Any new dependency integration
- API changes or deprecations
- Migration/version-upgrade tasks
- Verifying exact signatures/options before implementation
Failure Handling
If no strong library match is found:
- Try alternate package/project names
- Query broader topic scope
- Fall back to primary-source web docs (official site/repo)
