find-docs

Retrieves current library documentation and code examples via the Context7 CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/crazygit/dot-code-agents --skill find-docs-crazygit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-docs
Source: https://github.com/crazygit/dot-code-agents/tree/main/claude/skills/find-docs
Command: npx skills add https://github.com/crazygit/dot-code-agents --skill find-docs-crazygit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieve current documentation and code examples for any library using the Context7 CLI. Ensure you always work with the latest docs rather than relying on outdated training data.

Core Features & Use Cases

  • Resolve a library to a Context7-compatible ID and then query its documentation with ctx7 library and ctx7 docs.
  • Retrieve API references, setup instructions, configuration options, and code samples across libraries, frameworks, and tools.
  • Use cases include API syntax lookups, migration notes, and CLI usage for popular stacks like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot.

Quick Start

Lookup up-to-date library docs by name using the Context7 CLI to resolve and fetch documentation.

Frequently Asked Questions about find-docs

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

FAQPage Schema
How do I get up-to-date API references and code examples for a library?

To get up-to-date API references and code examples, retrieve current documentation using the Context7 CLI. This resolves a library to a compatible ID and fetches setup instructions, configuration options, and code samples.

How can I look up documentation for frameworks like React or Next.js without relying on outdated training data?

You can look up documentation for frameworks like React or Next.js by querying the Context7 CLI. It retrieves current syntax, migration notes, and CLI usage directly, ensuring you avoid outdated training data.

What is the workflow to fetch library docs when I only know the library name?

The workflow to fetch library docs involves a two-step process using the Context7 CLI. First, resolve the library name to a Context7-compatible ID, then query its documentation, limiting resolution attempts to three per question.

Does this documentation lookup approach work for both frontend libraries and backend cloud services?

Yes, this documentation lookup works for both frontend libraries and backend cloud services. It applies to retrieving API references, configuration options, and code samples across diverse libraries, frameworks, and tools.

What happens if a library ID isn't provided when trying to retrieve docs?

If a library ID isn't provided when retrieving docs, the system follows a documented two-step workflow to resolve the name first. It automatically limits resolution attempts to three per question to prevent excessive lookups.