New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Context7 Documentation Lookup

by affaan-m in affaan-m/ECC

Fetches current library and framework documentation through the Context7 MCP instead of relying on training data, resolving a library ID before each query.

MITAuto-check passedDevelopment

Install Context7 Documentation Lookup

skills CLI
$ npx skills add affaan-m/ECC --skill documentation-lookup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install affaan-m/ECC documentation-lookup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/documentation-lookup .claude/skills/documentation-lookup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
documentation-lookup
GitHub stars
277k
Used in
4 other repos
Token cost
~1.2k tokens
SKILL.md length
644 words
Files
1
Skills in repo
683
Repo updated
First seen
Licence
MIT

At a glance

Fetches current library and framework documentation through the Context7 MCP instead of relying on training data, resolving a library ID before each query.

  • Works in 4 steps: Resolve the Library ID → Select the Best Match → Fetch the Documentation → …
  • Answering setup or configuration questions about a named framework
  • SKILL.md covers Core Concepts, When to use, How it works and Examples, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

When a question depends on a library, framework or API, this skill has the agent pull live documentation from the Context7 MCP server rather than answer from memory. It uses two tools: `resolve-library-id`, which turns a library name and your question into a Context7 library ID such as `/vercel/next.js`, and `query-docs`, which fetches documentation and code snippets for that ID.

The flow has three steps: resolve the ID, pick the best match, then fetch docs with a specific question. Matching favors an exact name, a higher benchmark score, High or Medium source reputation and a version-specific ID when you named a version. The skill applies to setup questions, requests for code that depends on a library and API reference lookups, and needs the Context7 MCP configured in the agent harness.

When your agent uses it

  • Answering setup or configuration questions about a named framework
  • Writing code that depends on a library's current API
  • Looking up the reference for a specific library version
  • Checking an API's behavior against live docs instead of memory

Example prompts

  • “How do I configure Next.js middleware? Check the current docs first.”
  • “Write a Prisma query that returns users with their latest order, using the up-to-date API.”
  • “What auth methods does Supabase offer right now?”

Requirements

  • The Context7 MCP server configured in your agent
  • Network access to Context7

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Resolve the Library ID
  2. Select the Best Match
  3. Fetch the Documentation
  4. Use the Documentation

What it can do on your machine

Read from SKILL.md and the folder at commit 2d515e4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Context7 Documentation Lookup loads about 1.2k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 644 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit 2d515e4, republished under its MIT licence (© affaan-m). 644 words, ~1,228 tokens.

Download SKILL.mdSave it as .claude/skills/documentation-lookup/SKILL.md (or your agent's skills folder).
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).
metadata.origin
ECC

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.

Show full SKILL.md (270 more words)Show less
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.

© affaan-m, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/documentation-lookup of affaan-m/ECC.

Open the folder on GitHubat commit 2d515e4

Used in 4 other repositories

We found 14 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 4 other GitHub owners. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Context7 Documentation Lookup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Context7 Documentation Lookup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Context7 Documentation Lookup this skillaffaan-m/ECC277k4 repos~1.2kAutomated safety check: PassMIT
Analyze Logsactivepieces/activepieces25k1 repos~1.6kAutomated safety check: PassMIT
ReleasePrefectHQ/fastmcp28k—~2.9kAutomated safety check: PassApache-2.0
Review PRPrefectHQ/fastmcp28k—~3.1kAutomated safety check: PassApache-2.0
ObservalObserval/Observal4.3k—~2.2kAutomated safety check: PassApache-2.0
Ue Code AuthoringJasonMa0012/MooaToon750—~1.9kAutomated safety check: NotesCustom licence

Similar skills

  • Analyze Logs

    activepieces/activepieces

    Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.

    25k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Release

    PrefectHQ/fastmcp

    Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.

    28k GitHub stars~2.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Review PR

    PrefectHQ/fastmcp

    Assess a FastMCP pull request for justified behavior, compatibility, and correctness, then follow CI and review feedback to a revision-specific verdict.

    28k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Observal

    Observal/Observal

    A skill your agent uses when starting any task the organization may already have an approved skill, prompt, MCP server, or Agent for: reviewing code, a commit, a diff, or a pull request; writing…

    4.3k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Ue Code Authoring

    JasonMa0012/MooaToon

    A skill your agent uses when writing or modifying UE C++ (classes, actors, components, subsystems, interfaces, function libraries) with Rider MCP available.

    750 GitHub stars~1.9k tokensUpdated 23 days ago
    DevelopmentAuto-check: notes

  • Misakanet Failure Memory

    Ikalus1988/MisakaNet

    Search and record failure-recovery lessons from real engineering sessions; submit and verify debugging lessons across the MisakaNet network.

    526 GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

More from affaan-m/ECC

All 682 skills in this repo

  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    277k GitHub starsUsed in 5 repos~3.1k tokens
    Auto-check passed

  • VideoDB Video Search and Editing

    affaan-m/ECC

    Ingests, indexes, searches, edits and monitors video, audio and live streams through the VideoDB Python SDK, returning stream links, clips and timestamps.

    277k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes

  • Docs Governance

    affaan-m/ECC

    Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references.

    277k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    277k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed

  • Master Agreement Generator

    affaan-m/ECC

    Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    277k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Frontend Design Direction

    affaan-m/ECC

    Set an ECC-specific frontend design direction for production UI work.

    277k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed

Works with

Categories

Questions about Context7 Documentation Lookup

What does Context7 Documentation Lookup do?

Fetches current library and framework documentation through the Context7 MCP instead of relying on training data, resolving a library ID before each query. When a question depends on a library, framework or API, this skill has the agent pull live documentation from the Context7 MCP server rather than answer from memory.js`, and `query-docs`, which fetches documentation and code snippets for that ID.

When should I use Context7 Documentation Lookup?

Context7 Documentation Lookup fits situations like: answering setup or configuration questions about a named framework; writing code that depends on a library's current API; looking up the reference for a specific library version; checking an API's behavior against live docs instead of memory.

How do I install Context7 Documentation Lookup in Claude Code?

Run `npx skills add affaan-m/ECC --skill documentation-lookup -a claude-code`. Or copy the skill folder (skills/documentation-lookup in affaan-m/ECC) into .claude/skills/documentation-lookup in your project. Claude Code loads it when a task matches its description.

How do I install Context7 Documentation Lookup in Codex?

Run `npx skills add affaan-m/ECC --skill documentation-lookup -a codex`. Or copy the skill folder (skills/documentation-lookup in affaan-m/ECC) into .agents/skills/documentation-lookup in your project. Codex loads it when a task matches its description.

Can I use Context7 Documentation Lookup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill documentation-lookup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/documentation-lookup, .gemini/skills/documentation-lookup, .github/skills/documentation-lookup and .opencode/skills/documentation-lookup in your project.

What does Context7 Documentation Lookup need to run?

SKILL.md names no scripts, command-line tools or credentials: Context7 Documentation Lookup is instructions for the agent only. Our summary lists: The Context7 MCP server configured in your agent; Network access to Context7.

Does Context7 Documentation Lookup access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Context7 Documentation Lookup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Context7 Documentation Lookup use?

Context7 Documentation Lookup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Context7 Documentation Lookup use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Context7 Documentation Lookup?

Skills that share tags, products or a category with Context7 Documentation Lookup: Analyze Logs (activepieces/activepieces, 25k stars), Release (PrefectHQ/fastmcp, 28k stars), Review PR (PrefectHQ/fastmcp, 28k stars) and Observal (Observal/Observal, 4.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Context7 Documentation Lookup?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 276,673 GitHub stars. The repository holds 683 skills in this directory. The repository was last updated on October 11, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.