PluginBench
Skill
Official
Review
Audit score 70

documentation-lookup

upstash/context7

Fetch current documentation for libraries and frameworks instead of relying on training data.

What is documentation-lookup?

This skill retrieves up-to-date documentation from Context7 when users ask about libraries, frameworks, API references, or code examples. Use it for setup questions, code generation involving specific libraries, or when users mention frameworks like React, Vue, Next.js, Prisma, or Supabase.

  • Resolves library names to Context7 library IDs with relevance ranking
  • Fetches current documentation for the selected library
  • Returns version-specific documentation when available
  • Provides code examples and API references from official sources
  • Handles setup and configuration questions with accurate, up-to-date information

How to install documentation-lookup

npx skills add https://github.com/upstash/context7 --skill documentation-lookup
Claude Code
Cursor
Windsurf
Cline

How to use documentation-lookup

  1. 1.When user asks about a library or framework, extract the library name and their specific question
  2. 2.Call resolve-library-id with the library name and full user question
  3. 3.Review the resolution results and select the best match based on name accuracy and benchmark score
  4. 4.Call query-docs with the selected library ID and the user's specific question
  5. 5.Incorporate the fetched documentation into your response with code examples and version citations

Use cases

Good for
  • User asks 'How do I configure Next.js middleware?' — fetch Next.js docs for middleware setup
  • User requests 'Write a Prisma query to fetch users with posts' — retrieve Prisma query documentation
  • User asks 'What are the Supabase authentication methods?' — fetch Supabase auth API reference
  • User mentions 'React 19' in a component question — retrieve version-specific React documentation
  • User needs Tailwind CSS utility class examples — fetch current Tailwind documentation
Who it's for
  • Frontend developers working with React, Vue, Svelte, or similar frameworks
  • Full-stack developers using Next.js, Express, or other backend frameworks
  • Developers integrating databases like Prisma or Supabase
  • Anyone needing current API references or code examples

documentation-lookup FAQ

What if multiple libraries match the user's query?

Choose based on exact or closest name match to what the user asked for, and prefer higher benchmark scores which indicate better documentation quality.

How do I handle version-specific questions?

When users mention a specific version (e.g., 'React 19' or 'Next.js 15'), prefer version-specific library IDs from the resolution results if available.

Should I use this skill for all code generation questions?

Use this skill when the user's question involves specific libraries, frameworks, or setup. For general coding questions without library context, standard assistance may be sufficient.

What if the library isn't found in Context7?

If resolution returns no matches, inform the user and provide assistance based on your training data, noting that you cannot access current documentation for that library.

Full instructions (SKILL.md)

Source of truth, from upstash/context7.


name: documentation-lookup description: This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.

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