How do I install the Context7 skill?

Run npx skillmds@latest add arvindand/context7 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Context7 safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Context7?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Context7 free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Context7?

arvindand (@arvindand) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Context7 by arvindand — Agent Skill

Name: Context7
Rating: 4.2 (5 reviews)
Author: arvindand

Context7

Documentation lookup via Context7 REST API. Use when the user needs current library APIs, framework patterns, migration guidance, or official code examples for React, Next.js, Prisma, Express, Vue, Angular, Svelte, or other npm/PyPI packages. Use when the user says 'how do I use X library', 'what's the API for Y', or asks for official documentation. Use even when you think you know the answer — training data may not reflect recent releases.

arvindand Updated Sep 10, 2026

File contents

Context7 Documentation Lookup

Use ${CLAUDE_SKILL_DIR}/scripts/context7.py to fetch current library documentation without MCP tool-schema overhead.

This is an execution skill. Decide whether to search or fetch directly, run the script, then use the returned docs to answer. Keep the main flow lean and load REFERENCES.md only when you need example commands, common library IDs, or troubleshooting details.

When to Use

Activate when the user asks for:

current library or framework APIs
official code examples or implementation patterns
version-specific docs or migration guidance
third-party tool setup that depends on vendor docs
documentation for libraries in npm, PyPI, or similar ecosystems

Core Workflow

If you already know the library ID, skip search and call:

python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py docs <library-id> [topic] [mode]

If the library ID is unclear, search first:

python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py search "<query>"

Pick the best matching library ID, then fetch docs.
Use the returned docs to answer with version-aware guidance and cite the source URL when the script provides one.

Decision Rules

Search only when the library ID is unclear or ambiguous.
Use code mode (default) for API references, function signatures, and implementation examples.
Use info mode for conceptual guides, architecture, and migration-heavy questions.
Use a focused topic first; broaden it if results are empty or off-target.
For version-specific docs, append the full upstream tag to the library ID (for example /vercel/next.js/v15.1.8), or include the version in the topic. A bare major such as /vercel/next.js/15 does not resolve.

If syntax is unclear, run:

python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py --help

Output Rules

Prefer official patterns over generic recall when the docs provide a direct answer.
Keep the answer tied to the user's requested library and version.
Call out deprecations, caveats, or migration notes when the docs surface them.
If the docs are incomplete, say so and fall back to the best available general knowledge instead of inventing specifics.

Recovery

Issue	Action
Library ID is unclear	Re-run search with an alternate name, org name, or broader query.
Results are empty or irrelevant	Broaden the topic, then retry with the other mode (`code` vs `info`).
User needs a specific version	Add the version to the library ID or mention it in the topic, then verify the returned docs match.
Rate limited	Tell the user about `CONTEXT7_API_KEY`, then use best-effort fallback guidance if needed.
Script usage is unclear	Run `python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py --help`.
Script or network failure	Say live docs lookup failed and continue with clearly-labeled fallback knowledge.

License: MIT See also: REFERENCES.md

---name: context7description: Documentation lookup via Context7 REST API. Use when the user needs current library APIs, framework patterns, migration guidance, or official code examples for React, Next.js, Prisma, Express, Vue, Angular, Svelte, or other npm/PyPI packages. Use when the user says 'how do I use X library', 'what's the API for Y', or asks for official documentation. Use even when you think you know the answer — training data may not reflect recent releases.license: MIT---# Context7 Documentation LookupUse `${CLAUDE_SKILL_DIR}/scripts/context7.py` to fetch current library documentation without MCP tool-schema overhead.This is an execution skill. Decide whether to search or fetch directly, run the script, then use the returned docs to answer. Keep the main flow lean and load [REFERENCES.md](REFERENCES.md) only when you need example commands, common library IDs, or troubleshooting details.## When to UseActivate when the user asks for:- current library or framework APIs- official code examples or implementation patterns- version-specific docs or migration guidance- third-party tool setup that depends on vendor docs- documentation for libraries in npm, PyPI, or similar ecosystems## Core Workflow1. If you already know the library ID, skip search and call: ```bash python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py docs <library-id> [topic] [mode] ```2. If the library ID is unclear, search first: ```bash python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py search "<query>" ```3. Pick the best matching library ID, then fetch docs.4. Use the returned docs to answer with version-aware guidance and cite the source URL when the script provides one.## Decision Rules- Search only when the library ID is unclear or ambiguous.- Use `code` mode (default) for API references, function signatures, and implementation examples.- Use `info` mode for conceptual guides, architecture, and migration-heavy questions.- Use a focused topic first; broaden it if results are empty or off-target.- For version-specific docs, append the full upstream tag to the library ID (for example `/vercel/next.js/v15.1.8`), or include the version in the topic. A bare major such as `/vercel/next.js/15` does not resolve.If syntax is unclear, run:```bashpython3 ${CLAUDE_SKILL_DIR}/scripts/context7.py --help```## Output Rules- Prefer official patterns over generic recall when the docs provide a direct answer.- Keep the answer tied to the user's requested library and version.- Call out deprecations, caveats, or migration notes when the docs surface them.- If the docs are incomplete, say so and fall back to the best available general knowledge instead of inventing specifics.## Recovery| Issue | Action ||-------|--------|| Library ID is unclear | Re-run search with an alternate name, org name, or broader query. || Results are empty or irrelevant | Broaden the topic, then retry with the other mode (`code` vs `info`). || User needs a specific version | Add the version to the library ID or mention it in the topic, then verify the returned docs match. || Rate limited | Tell the user about `CONTEXT7_API_KEY`, then use best-effort fallback guidance if needed. || Script usage is unclear | Run `python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py --help`. || Script or network failure | Say live docs lookup failed and continue with clearly-labeled fallback knowledge. |---> **License:** MIT> **See also:** [REFERENCES.md](REFERENCES.md)

Frequently asked questions