Documentation Lookup
- 6 installs
- Updated January 17, 2026
- benedictking/context7
documentation-lookup is a skill that makes an agent fetch current library and framework documentation through Context7 before answering setup, API, or code-generation questions.
About
This skill tells the agent to pull up-to-date library and framework documentation through Context7 whenever a developer asks about libraries, APIs, or needs code examples. It resolves a library ID with resolve-library-id, then calls query-docs with the user's question and incorporates the returned docs into the answer. A developer uses it to avoid stale training-data answers on fast-moving frameworks like React, Next.js, Prisma, or Supabase.
- Fetches current library docs via Context7 instead of relying on training data
- Four-step flow: resolve-library-id then query-docs with the user's question
- Version-aware: prefers version-specific library IDs like React 19 or Next.js 15
Documentation Lookup by the numbers
- 6 all-time installs (skills.sh)
- Ranked #1,205 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
documentation-lookup capabilities & compatibility
- Capabilities
- documentation lookup · api reference · code examples
- Use cases
- documentation · research
What documentation-lookup says it does
When the user asks about libraries, frameworks, or needs code examples, use Context7 to fetch current documentation instead of relying on training data.
Requests code involving libraries ("Write a Prisma query for...")
npx skills add https://github.com/benedictking/context7 --skill documentation-lookupAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 6 |
|---|---|
| Last updated | January 17, 2026 |
| Repository | benedictking/context7 ↗ |
What it does
Fetch current framework or library documentation so code answers reflect the latest version instead of stale training data.
Who is it for?
Getting accurate, version-specific answers about libraries and frameworks instead of relying on the model's training data.
When should I use this skill?
The user asks setup or configuration questions, requests code involving a library, or mentions a specific framework.
What you get
Answers cite current, version-specific documentation with relevant code examples.
- An answer grounded in current library documentation with relevant code examples
Files
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 questionquery: 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
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71FAQ
When does this skill activate?
When the user asks setup or configuration questions, requests code involving libraries, needs API references, or mentions frameworks like React, Vue, Svelte, Express, or Tailwind.
How does it choose the right library?
It calls resolve-library-id and selects the exact or closest name match, prefers higher benchmark scores, and picks version-specific IDs when the user mentions a version.