documentation-lookup

Fetches current library and framework documentation via the Context7 MCP server.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill documentation-lookup-diazmelgarejo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-lookup
Source: https://github.com/diazMelgarejo/orama-system/tree/main/.cursor/.agents/skills/documentation-lookup
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill documentation-lookup-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI training data becomes outdated, so answers about libraries and frameworks can reference deprecated APIs or miss new features. This Skill retrieves live, version-aware documentation through the Context7 MCP instead of relying on stale training knowledge. ## Core Features & Use Cases - Library Resolution: Converts a library name like Next.js, Prisma, or Supabase into a Context7-compatible library ID using the resolve-library-id tool. - Targeted Doc Queries: Fetches relevant documentation snippets and code examples with the query-docs tool, ranked by name match, benchmark score, and source reputation. - Version Awareness: Prefers version-specific library IDs when the user mentions versions like React 19 or Next.js 15. - Use Case: When asked "How do I configure Next.js middleware?", the Skill resolves the official Next.js library ID, queries the current docs, and answers with an up-to-date middleware.ts example. ## Quick Start Ask how to set up middleware in Next.js and have the current official documentation fetched via Context7 to answer with a working code example.

Frequently Asked Questions about documentation-lookup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get up-to-date library documentation in an AI assistant?

Use the Context7 MCP integration: first call resolve-library-id with the library name and your question, then call query-docs with the returned library ID. This retrieves current documentation and code snippets rather than relying on training data.

How does Context7 resolve-library-id work?

resolve-library-id takes a library name and query, then returns Context7-compatible library IDs in the format /org/project. You select the best match by name similarity, benchmark score, and source reputation before querying docs.

Can I fetch docs for a specific version like Next.js 15 or React 19?

Yes. When the user mentions a version, the resolution step may return version-specific library IDs such as /org/project/v1.2.0. Prefer those IDs so query-docs returns documentation matching that release.

Which AI tools support the Context7 MCP documentation lookup?

Any harness with the Context7 MCP server configured works, including Claude Code, Cursor, and Codex. The skill activates for setup questions, API references, and code examples involving named frameworks.

What are the limitations of querying docs through Context7?

The skill limits itself to three MCP calls per question; if the answer remains unclear, it states the uncertainty rather than guessing. It also depends on Context7 having indexed the library, so obscure packages may not resolve.