Documentation Lookup
Fetch current library and framework documentation through Context7 MCP whenever agent answers would otherwise rely on stale training data.
Overview
Documentation Lookup is a journey-wide agent skill that fetches live library and framework documentation through Context7 MCP—usable whenever a solo builder needs accurate API or setup answers before committing to code.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill documentation-lookupWhat is this skill?
- Routes library and API questions through Context7 MCP tools resolve-library-id and query-docs
- Mandates resolve-library-id before query-docs for valid library IDs such as /vercel/next.js
- Activates on setup, configuration, API reference, and named-framework requests (React, Prisma, Supabase, etc.)
- Replaces guesswork from training cutoff with live documentation snippets across supported harnesses
- Works wherever Context7 MCP is configured (Claude Code, Cursor, and similar agents)
- Two-step Context7 flow: resolve-library-id then query-docs
- Explicit tools: resolve-library-id and query-docs
Adoption & trust: 4.2k installs on skills.sh; 210k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to wire up a framework or SDK and cannot trust the model’s training-era answers for setup steps, method signatures, or breaking changes.
Who is it for?
Indie builders integrating React, Next.js, Prisma, Supabase, Tailwind, or other fast-moving stacks who already have Context7 MCP in their agent harness.
Skip if: Pure greenfield logic with no external libraries, or environments where Context7 MCP is not installed and configured.
When should I use this skill?
User asks setup or configuration questions, requests library-dependent code, needs API or reference information, or mentions specific frameworks (React, Next.js, Prisma, Supabase, etc.).
What do I get? / Deliverables
The agent resolves a Context7 library id and returns current documentation snippets and examples aligned with the package you named.
- Context7 library id resolution for the named package
- Current documentation excerpts and code snippets for the user’s question
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Spike a new UI kit’s install steps by querying live setup docs before committing to the stack.
Implement a payment or auth SDK call using query-docs output for the exact method list.
Draft server handlers that match current ORM migration and query APIs from Context7 snippets.
Verify failing integration tests against the latest documented error codes and config flags.
Patch production config after a minor release by re-querying docs for deprecated options.
How it compares
Use instead of asking the model to recall framework APIs from memory when a live doc lookup is available.
Common Questions / FAQ
Who is documentation-lookup for?
Solo and indie developers using Claude Code, Cursor, Codex, or similar agents who need trustworthy, current framework documentation while building or debugging integrations.
When should I use documentation-lookup?
Use it during Build integrations when writing Prisma or ORM code, during Validate prototyping when configuring a new stack, during Ship debugging when middleware or auth behavior changed, and anytime you name a specific library in a question.
Is documentation-lookup safe to install?
The skill only instructs the agent to call Context7 MCP tools; review the Security Audits panel on this page and your MCP server permissions before enabling network doc access.
SKILL.md
READMESKILL.md - Documentation Lookup
# Documentation Lookup (Context7) When the user asks about libraries, frameworks, or APIs, fetch current documentation via the Context7 MCP (tools `resolve-library-id` and `query-docs`) instead of relying on training data. ## Core Concepts - **Context7**: MCP server that exposes live documentation; use it instead of training data for libraries and APIs. - **resolve-library-id**: Returns Context7-compatible library IDs (e.g. `/vercel/next.js`) from a library name and query. - **query-docs**: Fetches documentation and code snippets for a given library ID and question. Always call resolve-library-id first to get a valid library ID. ## When to use Activate when the user: - Asks setup or configuration questions (e.g. "How do I configure Next.js middleware?") - Requests code that depends on a library ("Write a Prisma query for...") - Needs API or reference information ("What are the Supabase auth methods?") - Mentions specific frameworks or libraries (React, Vue, Svelte, Express, Tailwind, Prisma, Supabase, etc.) Use this skill whenever the request depends on accurate, up-to-date behavior of a library, framework, or API. Applies across harnesses that have the Context7 MCP configured (e.g. Claude Code, Cursor, Codex). ## How it works ### Step 1: Resolve the Library ID Call the **resolve-library-id** MCP tool with: - **libraryName**: The library or product name taken from the user's question (e.g. `Next.js`, `Prisma`, `Supabase`). - **query**: The user's full question. This improves relevance ranking of results. You must obtain a Context7-compatible library ID (format `/org/project` or `/org/project/version`) before querying docs. Do not call query-docs without a valid library ID from this step. ### Step 2: Select the Best Match From the resolution results, choose one result using: - **Name match**: Prefer exact or closest match to what the user asked for. - **Benchmark score**: Higher scores indicate better documentation quality (100 is highest). - **Source reputation**: Prefer High or Medium reputation when available. - **Version**: If the user specified a version (e.g. "React 19", "Next.js 15"), prefer a version-specific library ID if listed (e.g. `/org/project/v1.2.0`). ### Step 3: Fetch the Documentation Call the **query-docs** MCP tool with: - **libraryId**: The selected Context7 library ID from Step 2 (e.g. `/vercel/next.js`). - **query**: The user's specific question or task. Be specific to get relevant snippets. Limit: do not call query-docs (or resolve-library-id) more than 3 times per question. If the answer is unclear after 3 calls, state the uncertainty and use the best information you have rather than guessing. ### Step 4: Use the Documentation - Answer the user's question using the fetched, current information. - Include relevant code examples from the docs when helpful. - Cite the library or version when it matters (e.g. "In Next.js 15..."). ## Examples ### Example: Next.js middleware 1. Call **resolve-library-id** with `libraryName: "Next.js"`, `query: "How do I set up Next.js middleware?"`. 2. From results, pick the best match (e.g. `/vercel/next.js`) by name and benchmark score. 3. Call **query-docs** with `libraryId: "/vercel/next.js"`, `query: "How do I set up Next.js middleware?"`. 4. Use the returned snippets and text to answer; include a minimal `middleware.ts` example from the docs if relevant. ### Example: Prisma query 1. Call **resolve-library-id** with `libraryName: "Prisma"`, `query: "How do I query with relations?"`. 2. Select the official Prisma library ID (e.g. `/prisma/prisma`). 3. Call **query-docs** with that `libraryId` and the query. 4. Return the Prisma Client pattern (e.g. `include` or `select`) with a