Documentation Lookup (Context7)

Use up-to-date library and framework docs via Context7 MCP instead of training data.

You say
Install this skill Read the source first Free Written by affaan-m · unverified publisher
Context cost
1.3k tokensestimated from the bundle, loaded when it triggers
Bundle
2 files · 5.2 kBtext throughout, nothing executable
Licence
MITfree to use
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

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).

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

documentationmcp

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md4.9 kB · 90 lines
--- name: documentation-lookup description: 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). ---
6# Documentation Lookup (Context7)
7
8When 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.
9
10## Core Concepts
11
12- **Context7**: MCP server that exposes live documentation; use it instead of training data for libraries and APIs.
13- **resolve-library-id**: Returns Context7-compatible library IDs (e.g. /vercel/next.js) from a library name and query.
14- **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.
15
16## When to use
17
18Activate when the user:
19
20- Asks setup or configuration questions (e.g. "How do I configure Next.js middleware?")
21- Requests code that depends on a library ("Write a Prisma query for...")
22- Needs API or reference information ("What are the Supabase auth methods?")
23- Mentions specific frameworks or libraries (React, Vue, Svelte, Express, Tailwind, Prisma, Supabase, etc.)
24
25Use 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).
26
27## How it works
28
29### Step 1: Resolve the Library ID
30
31Call the **resolve-library-id** MCP tool with:
32
33- **libraryName**: The library or product name taken from the user's question (e.g. Next.js, Prisma, Supabase).
34- **query**: The user's full question. This improves relevance ranking of results.
35
36You 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.
37
38### Step 2: Select the Best Match
39
40From the resolution results, choose one result using:
41
42- **Name match**: Prefer exact or closest match to what the user asked for.
43- **Benchmark score**: Higher scores indicate better documentation quality (100 is highest).
44- **Source reputation**: Prefer High or Medium reputation when available.
45- **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).
46
47### Step 3: Fetch the Documentation
48
49Call the **query-docs** MCP tool with:
50
51- **libraryId**: The selected Context7 library ID from Step 2 (e.g. /vercel/next.js).
52- **query**: The user's specific question or task. Be specific to get relevant snippets.
53
54Limit: 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.
55
56### Step 4: Use the Documentation
57
58- Answer the user's question using the fetched, current information.
59- Include relevant code examples from the docs when helpful.
60- Cite the library or version when it matters (e.g. "In Next.js 15...").
61
62## Examples
63
64### Example: Next.js middleware
65
661. Call **resolve-library-id** with libraryName: "Next.js", query: "How do I set up Next.js middleware?".
672. From results, pick the best match (e.g. /vercel/next.js) by name and benchmark score.
683. Call **query-docs** with libraryId: "/vercel/next.js", query: "How do I set up Next.js middleware?".
694. Use the returned snippets and text to answer; include a minimal middleware.ts example from the docs if relevant.
70
71### Example: Prisma query
72
731. Call **resolve-library-id** with libraryName: "Prisma", query: "How do I query with relations?".
742. Select the official Prisma library ID (e.g. /prisma/prisma).
753. Call **query-docs** with that libraryId and the query.
764. Return the Prisma Client pattern (e.g. include or select) with a short code snippet from the docs.
77
78### Example: Supabase auth methods
79
801. Call **resolve-library-id** with libraryName: "Supabase", query: "What are the auth methods?".
812. Pick the Supabase docs library ID.
823. Call **query-docs**; summarize the auth methods and show minimal examples from the fetched docs.
83
84## Best Practices
85
86- **Be specific**: Use the user's full question as the query where possible for better relevance.
87- **Version awareness**: When users mention versions, use version-specific library IDs from the resolve step when available.
88- **Prefer official sources**: When multiple matches exist, prefer official or primary packages over community forks.
89- **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.
90
In the file
SKILL.md716 words
Files2
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈70
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
1,230
on trigger
The instruction body and 1 supporting file, read only when the skill fires.
0.65%
of a 200k window
Ten skills this size would take about 7% of the window before you open a file.
050k100k150k200k context window

1.3k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

2 files, 5.2 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • agents/openai.yaml0.3 kB
  • SKILL.md4.9 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 2 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Documentation Lookup (Context7) · 1.3k tokens when loaded npx mcprush@latest skill add affaan-m/documentation-lookup-context7

Writes to .claude/skills/documentation-lookup-context7/ in the current project. Add --global to put it in your home directory instead, for every project.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referenceaffaan-m/documentation-lookup-context7

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0