Skip to content

oberconcejo/VS-CODE / .agents/skills/documentation-lookup

documentation-lookup

Verified

Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).

Documentation Lookup (Context7)

When the user asks about libraries, frameworks, or APIs, fetch current documentation via the Context7 MCP (tools resolve-library-id and query-docs) instead of relying on training data.

Core Concepts

  • Context7: MCP server that exposes live documentation; use it instead of training data for libraries and APIs.
  • resolve-library-id: Returns Context7-compatible library IDs (e.g. /vercel/next.js) from a library name and query.
  • query-docs: Fetches documentation and code snippets for a given library ID and question. Always call resolve-library-id first to get a valid library ID.

When to use

Activate when the user:

  • Asks setup or configuration questions (e.g. "How do I configure Next.js middleware?")
  • Requests code that depends on a library ("Write a Prisma query for...")
  • Needs API or reference information ("What are the Supabase auth methods?")
  • Mentions specific frameworks or libraries (React, Vue, Svelte, Express, Tailwind, Prisma, Supabase, etc.)

Use this skill whenever the request depends on accurate, up-to-date behavior of a library, framework, or API. Applies across harnesses that have the Context7 MCP configured (e.g. Claude Code, Cursor, Codex).

How it works

Step 1: Resolve the Library ID

Call the resolve-library-id MCP tool with:

  • libraryName: The library or product name taken from the user's question (e.g. Next.js, Prisma, Supabase).
  • query: The user's full question. This improves relevance ranking of results.

You must obtain a Context7-compatible library ID (format /org/project or /org/project/version) before querying docs. Do not call query-docs without a valid library ID from this step.

Step 2: Select the Best Match

From the resolution results, choose one result using:

  • Name match: Prefer exact or closest match to what the user asked for.
  • Benchmark score: Higher scores indicate better documentation quality (100 is highest).
  • Source reputation: Prefer High or Medium reputation when available.
  • Version: If the user specified a version (e.g. "React 19", "Next.js 15"), prefer a version-specific library ID if listed (e.g. /org/project/v1.2.0).

Step 3: Fetch the Documentation

Call the query-docs MCP tool with:

  • libraryId: The selected Context7 library ID from Step 2 (e.g. /vercel/next.js).
  • query: The user's specific question or task. Be specific to get relevant snippets.

Limit: do not call query-docs (or resolve-library-id) more than 3 times per question. If the answer is unclear after 3 calls, state the uncertainty and use the best information you have rather than guessing.

Step 4: Use the Documentation

  • Answer the user's question using the fetched, current information.
  • Include relevant code examples from the docs when helpful.
  • Cite the library or version when it matters (e.g. "In Next.js 15...").

Examples

Example: Next.js middleware

  1. Call resolve-library-id with libraryName: "Next.js", query: "How do I set up Next.js middleware?".
  2. From results, pick the best match (e.g. /vercel/next.js) by name and benchmark score.
  3. Call query-docs with libraryId: "/vercel/next.js", query: "How do I set up Next.js middleware?".
  4. Use the returned snippets and text to answer; include a minimal middleware.ts example from the docs if relevant.

Example: Prisma query

  1. Call resolve-library-id with libraryName: "Prisma", query: "How do I query with relations?".
  2. Select the official Prisma library ID (e.g. /prisma/prisma).
  3. Call query-docs with that libraryId and the query.
  4. Return the Prisma Client pattern (e.g. include or select) with a short code snippet from the docs.

Example: Supabase auth methods

  1. Call resolve-library-id with libraryName: "Supabase", query: "What are the auth methods?".
  2. Pick the Supabase docs library ID.
  3. Call query-docs; summarize the auth methods and show minimal examples from the fetched docs.

Best Practices

  • Be specific: Use the user's full question as the query where possible for better relevance.
  • Version awareness: When users mention versions, use version-specific library IDs from the resolve step when available.
  • Prefer official sources: When multiple matches exist, prefer official or primary packages over community forks.
  • No sensitive data: Redact API keys, passwords, tokens, and other secrets from any query sent to Context7. Treat the user's question as potentially containing secrets before passing it to resolve-library-id or query-docs.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 467kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 196kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 196kUpdated Claude CodeCodexVerifiedInstall