Context7

Skill arvindand/agent-skills/skills/context7

Reusable agent skills for Claude Code, GitHub Copilot, and other AI assistants. Dependency intelligence, GitHub ops, documentation lookup, UI/UX design patterns.

Install

npx -y skills add arvindand/agent-skills --skill context7

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.4 KB, as published. Nobody here has run it

Context7 Documentation Lookup

Use 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 scripts/context7.py docs <library-id> [topic] [mode]

If the library ID is unclear, search first:

python3 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 version to the library ID (for example /vercel/next.js/14) or include the version in the topic.

If syntax is unclear, run:

python3 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 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