Documentation Lookup
Pull current library and framework docs into the agent session instead of guessing APIs from stale training data.
Overview
Documentation Lookup is an agent skill most often used in Build (also Validate and Ship) that fetches live Context7 documentation for libraries and frameworks instead of relying on training data.
Install
npx skills add https://github.com/upstash/context7 --skill documentation-lookupWhat is this skill?
- Two-step Context7 flow: resolve-library-id then query-docs with the user’s question
- Triggered by setup questions, code generation, and named stacks (React, Next.js, Prisma, Supabase, etc.)
- Version-aware library selection when the user names a release (e.g. React 19)
- Uses benchmark scores from resolution results to pick the best documentation corpus
- Replaces hallucinated API shapes with fetched reference snippets
- 2-step fetch flow: resolve-library-id then query-docs
Adoption & trust: 1.4k installs on skills.sh; 57k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need correct setup steps or API usage for a library and the agent would otherwise invent outdated signatures or config.
Who is it for?
Solo builders wiring integrations, scaffolding features, or debugging framework config who want cited, current vendor docs in-chat.
Skip if: Pure product strategy with no named library, or environments where outbound doc fetch tools are blocked.
When should I use this skill?
User asks about libraries, frameworks, API references, setup, or code involving specific stacks.
What do I get? / Deliverables
The agent answers with documentation grounded in Context7 query results matched to the right library ID and your exact question.
- Ranked library ID selection from resolution
- Documentation excerpts answering the user query
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Most invocations happen while writing or configuring code, so Build is the canonical shelf. Library setup, API methods, and framework config are integration work against external docs sources.
Where it fits
Spike a Supabase auth flow using query-docs before committing to the full schema.
Generate Prisma queries with IDs resolved from the user’s model names.
Confirm the latest testing APIs for a framework before writing integration tests.
How it compares
Live doc retrieval via Context7—not a static SKILL.md cheat sheet or a general web search skill.
Common Questions / FAQ
Who is documentation-lookup for?
Developers using Claude Code, Cursor, or Codex who regularly depend on React, Next.js, Prisma, Supabase, and similar ecosystems.
When should I use documentation-lookup?
Use it in Build for implementation questions; in Validate when prototyping against a new SDK; and in Ship when verifying config against current API docs.
Is documentation-lookup safe to install?
It implies network calls to documentation services; confirm tool permissions and read the Security Audits panel on this Prism page.
SKILL.md
READMESKILL.md - Documentation Lookup
When the user asks about libraries, frameworks, or needs code examples, use Context7 to fetch current documentation instead of relying on training data. ## When to Use This Skill Activate this skill when the user: - Asks setup or configuration questions ("How do I configure Next.js middleware?") - Requests code involving libraries ("Write a Prisma query for...") - Needs API references ("What are the Supabase auth methods?") - Mentions specific frameworks (React, Vue, Svelte, Express, Tailwind, etc.) ## How to Fetch Documentation ### Step 1: Resolve the Library ID Call `resolve-library-id` with: - `libraryName`: The library name extracted from the user's question - `query`: The user's full question (improves relevance ranking) ### Step 2: Select the Best Match From the resolution results, choose based on: - Exact or closest name match to what the user asked for - Higher benchmark scores indicate better documentation quality - If the user mentioned a version (e.g., "React 19"), prefer version-specific IDs ### Step 3: Fetch the Documentation Call `query-docs` with: - `libraryId`: The selected Context7 library ID (e.g., `/vercel/next.js`) - `query`: The user's specific question ### Step 4: Use the Documentation Incorporate the fetched documentation into your response: - Answer the user's question using current, accurate information - Include relevant code examples from the docs - Cite the library version when relevant ## Guidelines - **Be specific**: Pass the user's full question as the query for better results - **Version awareness**: When users mention versions ("Next.js 15", "React 19"), use version-specific library IDs if available from the resolution step - **Prefer official sources**: When multiple matches exist, prefer official/primary packages over community forks