documentation-lookup

Ask your question naming the library, and the Skill calls the Context7 resolve-library-id tool to find the matching library ID, then query-docs to fetch current documentation and code snippets. The answer is built from the fetched docs rather than training data.

Context7 is an MCP server exposing live documentation through two tools: resolve-library-id, which maps a library name to an ID like /vercel/next.js, and query-docs, which fetches docs for that ID. You must resolve the ID before querying docs.

Yes. When the user mentions a version, the Skill prefers version-specific library IDs from the resolution results, such as /org/project/v1.2.0, so the fetched documentation matches the requested release.

Any harness with the Context7 MCP server configured can use it, including Claude Code, Cursor, and Codex. The Skill relies only on the resolve-library-id and query-docs MCP tools being available.

The Skill limits itself to three MCP calls per question; if the answer remains unclear, it states the uncertainty instead of guessing. It also depends on Context7 having indexed documentation for the requested library.

The Skill instructs redacting API keys, passwords, tokens, and other secrets from any query before passing it to resolve-library-id or query-docs. Treat your question as potentially containing secrets before it is sent.