context7-docs

Fetch current library and API documentation to ground coding answers.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/gevrey/openclaw_backup --skill context7-docs-gevrey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context7-docs
Source: https://github.com/gevrey/openclaw_backup/tree/main/skills/context7-docs
Command: npx skills add https://github.com/gevrey/openclaw_backup --skill context7-docs-gevrey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ctx7, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Retrieve up-to-date, authoritative documentation for libraries and APIs to ground coding guidance and reduce hallucinations.

Core Features & Use Cases

  • Ground coding answers with current library/API docs.
  • Resolve library IDs and fetch version-specific guidance.
  • Produce trust-marked outputs with Source, Version, Confidence, and Verify markers, and run a built-in sanity check.

Quick Start

Ask Context7 to locate the target library docs and fetch the latest guidance for your task.

Frequently Asked Questions about context7-docs

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

FAQPage Schema
How do I ground coding answers in current official documentation to prevent hallucinations?

Ground coding answers in current official documentation by fetching version-specific library and API docs through Context7 tools to prevent hallucinations. The Skill retrieves authoritative guidance, annotates outputs with Source, Version, Confidence, and Verify markers, and runs a lightweight sanity check.

What's the best way to fetch version-specific library docs for framework migrations?

Fetch version-specific library docs for framework migrations by resolving the target library ID and retrieving the latest guidance through Context7 tools. The Skill produces trust-marked outputs annotated with Source, Version, Confidence, and Verify markers to validate the migration documentation.

How does Context7 lookup work for grounding API documentation?

Context7 lookup works by fetching current official documentation through the ctx7 library/docs tools, optionally using deterministic wrappers in scripts/context7_lookup.sh. It grounds coding guidance by annotating responses with Source, Version, Confidence, and Verify markers followed by a sanity check via scripts/context7_sanity_check.py.

Do I need the ctx7 dependency to use context7-docs for documentation retrieval?

Yes, the ctx7 dependency is required to retrieve current official library and API documentation. The Skill relies on ctx7 library/docs tools to fetch authoritative guidance and resolve library IDs for version-specific documentation grounding.

When should I use documentation grounding to reduce API hallucination risk?

Use documentation grounding when users request latest docs, framework setup/configuration, migrations, or API guidance where hallucination risk is high. Trigger the grounding process when users explicitly say "use context7" or when coding answers require authoritative validation against current official documentation.

What trust markers does context7-docs add to fetched library documentation?

Context7-docs adds Source, Version, Confidence, and Verify markers to fetched library documentation outputs. These trust markers annotate the grounded coding guidance and are followed by a built-in sanity check using scripts/context7_sanity_check.py to validate the retrieved documentation.