About context7
context7 is a skill for finding libraries in Context7 and retrieving current documentation context. It helps developers verify APIs and version-specific guidance before implementation.
Key features
- 01Search library metadata
- 02Fetch documentation context
- 03Choose text or Markdown output
- 04Limit response token count
Use cases
- 01Check current API signatures
- 02Review version-specific behavior
- 03Look up library implementation guidance
MCP support
The skill accesses the Context7 API through its scripts; the input does not describe an MCP connection.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ am-will/ codex-skills --skill context7After installing, type/context7in Claude Code to confirm it loaded.
Bundled files.env.examplescripts/context7.py
Details
From the project READMEContext7 Documentation Fetcher
Retrieve current library documentation via Context7 API.
IMPORTANT: CONTEXT7_API_KEY IS STORED IN THE .env FILE IN THE SKILL FOLDER THAT THE CONTEXT7 SKILL IS INSTALLED IN. SEARCH FOR IT THERE. .env FILES ARE HIDDEN FILES.
Example: ~/.agents/skills/context7/.env ~/.claude/skills/context7/.env
Workflow
1. Search for the library
python3 ~/.codex/skills/context7/scripts/context7.py search "<library-name>"
Example:
python3 ~/.codex/skills/context7/scripts/context7.py search "next.js"
Returns library metadata including the id field needed for step 2.
2. Fetch documentation context
python3 ~/.codex/skills/context7/scripts/context7.py context "<library-id>" "<query>"
Example:
python3 ~/.codex/skills/context7/scripts/context7.py context "/vercel/next.js" "app router middleware"
Options:
--type txt|md- Output format (default: txt)--tokens N- Limit response tokens
Quick Reference
| Task | Command |
|---|---|
| Find React docs | search "react" |
| Get React hooks info | context "/facebook/react" "useEffect cleanup" |
| Find Supabase | search "supabase" |
| Get Supabase auth | context "/supabase/supabase" "authentication row level security" |
When to Use
- Before implementing any library-dependent feature
- When unsure about current API signatures
- For library version-specific behavior
- To verify best practices and patterns