Claude-skill-registry context7
Fetch up-to-date library documentation using Context7 API. Use this skill when the user asks for docs, examples, or help with a specific library/framework (e.g., "look up React docs", "context7 nextjs routing", "fetch docs for fastapi").
git clone https://github.com/majiayu000/claude-skill-registry
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/context7" ~/.claude/skills/majiayu000-claude-skill-registry-context7-66ddf4 && rm -rf "$T"
skills/data/context7/SKILL.mdContext7 Documentation Fetcher
This skill fetches up-to-date documentation and code examples from libraries using the Context7 API.
Standard Workflow
Context7 requires a two-step process:
Step 1: Search for the Library ID
First, search for the library to get its ID:
GET https://context7.com/api/v2/libs/search?libraryName=<library>&query=<context>
Parameters:
: The library name (e.g., "react", "nextjs", "fastapi")libraryName
: Search context to help find the right libraryquery
The response contains a
results array with library objects. Use the id field from the first result.
Step 2: Get Documentation Context
Use the library ID to fetch relevant documentation:
GET https://context7.com/api/v2/context?libraryId=<id>&query=<question>
Parameters:
: The ID from step 1 (e.g., "/vercel/next.js")libraryId
: Natural language question about the documentationquery
This returns ranked code snippets and documentation matching your query.
Example Usage
When the user asks about a library:
-
Search for the library: Fetch
Extract the library ID from the response (e.g., "/vercel/next.js")https://context7.com/api/v2/libs/search?libraryName=nextjs&query=routing -
Fetch documentation: Fetch
https://context7.com/api/v2/context?libraryId=/vercel/next.js&query=How to setup dynamic routes -
Present the results to the user with the relevant code examples and documentation.
Tips for Best Results
- Use specific, detailed queries rather than vague terms
- Include relevant context in the query (e.g., "useState hook with TypeScript" instead of just "state")
- The API works without an API key but has restricted rate limits