playbooks

home / skills / upstash / context7 / documentation-lookup

documentation-lookup skill

/plugins/claude/context7/skills/documentation-lookup

This skill fetches up-to-date library and framework documentation and provides accurate code examples for user questions.

npx playbooks add skill upstash/context7 --skill documentation-lookup

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.1 KB
---
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

Overview

This skill uses Context7 to fetch up-to-date library and framework documentation for code examples, setup steps, and API references. It activates when users ask about specific packages, configuration, or need code snippets tied to frameworks like Next.js, React, Prisma, or Supabase. The skill ensures responses are current, version-aware, and sourced from the best matching docs.

How this skill works

The skill first calls resolve-library-id with the library name and the user's full question to find the most relevant library entry. It selects the best match by exact name, version preference when provided, and benchmark score. Then it calls query-docs with the chosen libraryId and the user's question, and uses the returned documentation and examples to craft a precise, versioned answer.

When to use it

  • User asks how to configure or set up a framework or middleware (e.g., Next.js middleware setup).
  • User requests code involving a particular library (e.g., write a Prisma query or Supabase auth flow).
  • User asks for API references or method lists for a library (e.g., Supabase auth methods).
  • User mentions specific frameworks or packages by name or version (React 19, Next.js 15).
  • User needs authoritative code examples or migration steps based on current docs.

Best practices

  • Always pass the user's full question to resolve-library-id to improve relevance ranking.
  • Prefer exact name and version-specific library IDs when the user specifies a version.
  • Favor official/primary packages over forks when multiple matches are available.
  • Include cited version information in answers when documentation is versioned.
  • Return concise, copy-pasteable code examples from the fetched docs and note any config prerequisites.

Example use cases

  • Show a working Next.js middleware example for edge runtime and mention required Next.js version.
  • Generate a Prisma query to filter and paginate users, using the latest Prisma docs for syntax.
  • List Supabase client auth methods and show an example sign-in flow from the docs.
  • Explain how to configure Tailwind in a Vite/React project with the exact setup commands.
  • Provide React component patterns or hooks examples pulled from current official docs.

FAQ

What if multiple libraries match my query?

The skill selects the best match by exact name, version preference, and benchmark score; it prefers official packages over forks.

Will answers reflect the library version I mention?

Yes. When a version is specified, the skill prefers version-specific library IDs and cites the version in the response.