context7-docs-lookup

Original：🇺🇸 English
Translated

Use Context7 to fetch up-to-date library documentation. Activates when the user asks about libraries, frameworks, API references, or needs code examples — especially for setup questions, code generation, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.

6installs
Sourceupstash/context7
Added on

NPX Install

npx skill4agent add upstash/context7 context7-docs-lookup

Tags

Translated version includes tags in frontmatter
context7-toollibrary-documentationcode-examplesframework-referencesapi-lookup

SKILL.md Content

View Translation Comparison →
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