context7

Resolve library IDs and query official docs for version-aware API answers.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kittne/codex-skills-by-codex --skill context7-kittne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context7
Source: https://github.com/kittne/codex-skills-by-codex/tree/main/context7
Command: npx skills add https://github.com/kittne/codex-skills-by-codex --skill context7-kittne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Context7 provides up-to-date, official documentation and version guidance for external libraries across languages. Use when querying library APIs, debugging dependency issues, or installing/upgrading dependencies, to ensure information comes from official docs rather than outdated knowledge.

Core Features & Use Cases

  • Resolve the exact library ID for a given package/framework within a repo, factoring in per-project versions.
  • Detect installed library version from common files (package.json, go.mod, pyproject.toml, etc.) to tailor guidance.
  • Query official Context7 docs for precise API surfaces, configuration keys, and version-specific caveats.
  • Provide doc-backed answers with version-aware notes and safe fallbacks when docs are ambiguous.

Quick Start

Ask Context7 for the latest docs by naming the library and its language, then specify an exact API surface question.

Frequently Asked Questions about context7

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get up-to-date official documentation for a specific library version?

To get up-to-date official documentation, specify the library name and language to query precise API surfaces and version-specific caveats. The system detects installed versions from repo files to tailor guidance directly from official docs.

How does resolving a library ID from repository files work?

Resolving a library ID works by detecting installed library versions from common files like package.json, go.mod, or pyproject.toml. It factors in per-project versions to identify the exact package or framework within your repo.

Can I use this to debug dependency issues across different languages?

Yes, you can use this to debug dependency issues across languages by querying official Context7 docs. It detects library context from repo files and provides version-aware notes with safe fallbacks for external libraries.

What is the best way to query API surfaces when documentation is ambiguous?

The best way to query API surfaces when documentation is ambiguous is to request doc-backed answers with version-aware caveats. The system provides safe fallbacks and resolves precise API details directly from official documentation.

Why does my library API guidance include version-aware caveats?

Your library API guidance includes version-aware caveats to ensure information comes from official docs rather than outdated knowledge. It factors in per-project versions detected from repository files to deliver precise, version-specific details.

Do I need to specify an exact API surface question to get version guidance?

Yes, you need to specify an exact API surface question after naming the library and language to get version guidance. This ensures the doc-backed answers target the precise configuration keys and version-specific caveats you need.