Agent skill · research science · pedronauck
context7
Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer — do not rely on training data for API details, signatures, or configuration options as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details.
Why this skill is useful
Provides a CLI tool that retrieves up-to-date technical documentation and code examples for various libraries and frameworks, which the AI may not have access to.
What it needs
Requires ctx7 installed locally. About 4k tokens when loaded. Last updated 2026-08-01. 564 stars on the source repository.
What this skill does
Documentation Lookup Retrieve current documentation and code examples for any library using the Context7 CLI. Run commands with npx ctx7@latest so setup always uses the latest CLI without a global install: Optionally install globally if you prefer a bare ctx7 command: Workflow Two-step process: resolve the library name to an ID, then query docs with that ID. You MUST call library first to obtain a valid library ID UNLESS the user explicitly provides a library ID in the format /org/project or /org/project/version. IMPORTANT: Do not run these commands more than 3 times per question. If you cannot find what you need after 3 attempts, use the best result you have. Step 1: Resolve a Library Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. Use the official library name with proper punctuation (e.g., "Next.js" not "nextjs", "Customer.io" not "customerio", "Three.js" not "threejs"). If results look wrong, try alternate spellings such as next.js before changing the query. Always pass a query argument — it is required and directly affects result ranking. Use the user's intent to form the query, which helps disambiguate when multiple libraries share a similar name. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query. Result fields Each result includes: Library ID — Context7-compatible identifier (format: /org/project) Name — Library or package name Description — Short summary Code Snippets — Number of available code examples Source Reputation — Authority indicator (High, Medium, Low, or Unknown) Benchmark Score — Quality indicator (100 is the highest score) Versions — List of versions if available. Use one of those versions if the user provides a version in their query. The format is /org/project/version. Selection process 1. Analyze the query to understand what library/package the user is looking for 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pedronauck/context7