context7

Fetch up-to-date library documentation via the Context7 API.

3|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/0xharryriddle/codex-field-kit --skill context7-0xharryriddle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context7
Source: https://github.com/0xharryriddle/codex-field-kit/tree/main/archive/upstream/examples/codex-skills/skills/context7
Command: npx skills add https://github.com/0xharryriddle/codex-field-kit --skill context7-0xharryriddle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Fetch up-to-date library documentation via Context7 API to ensure you always have current API signatures, patterns, and best practices when integrating external libraries.

Core Features & Use Cases

  • Library discovery: search for libraries by name to locate the correct library context.
  • Documentation fetch: retrieve targeted documentation context for a given library and query, with optional output formats and token limits.
  • Safe credentials handling: relies on CONTEXT7_API_KEY stored in the skill's .env file to authenticate requests.
  • Use Case: Before implementing a library-dependent feature, verify APIs and usage examples to avoid version drift.

Quick Start

Run the context7 script to search for a library and fetch its documentation context.

Frequently Asked Questions about context7

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

FAQPage Schema
How do I fetch up-to-date documentation for external libraries like React or Supabase?

You can fetch up-to-date library documentation by running the context7 script to search for a specific library and retrieve its current API signatures, patterns, and best practices directly via the Context7 API.

Why does my code break after a library upgrade, and how can I verify current APIs?

Library upgrades often cause version drift. You can verify current APIs by fetching targeted library documentation before implementing features, ensuring your code aligns with the latest API signatures and usage patterns.

Do I need an API key to retrieve library context and search for documentation?

Yes, retrieving library context requires a CONTEXT7_API_KEY stored in the skill's .env file. This key safely handles credentials and authenticates all documentation search and context retrieval requests.

Can I limit the documentation tokens returned when searching for library best practices?

Yes, when fetching library documentation you can specify optional output types and token limits. This constrains the retrieved context to match your specific query regarding APIs, patterns, or best practices.

What is the best way to discover a specific library before integrating its API?

The best way to discover a library is using the library search feature to locate the correct library context by name. This identifies the exact library before fetching its targeted documentation and API signatures.