find-docs

Resolve library names to Context7 IDs and query documentation.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Blake-John/agent-config --skill find-docs-blake-john
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-docs
Source: https://github.com/Blake-John/agent-config/tree/main/.agents/skills/find-docs
Command: npx skills add https://github.com/Blake-John/agent-config --skill find-docs-blake-john

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locates authoritative, up-to-date docs, API references, configuration details, and code examples for developer technologies, reducing time spent searching across sources.

Core Features & Use Cases

  • Quick access to current documentation for libraries, frameworks, and tools.
  • Step-by-step workflow guidance for resolving library IDs and querying docs.
  • Use cases include API looksups, configuration help, code examples, and migration notes.

Quick Start

Resolve the library with ctx7 library, then query its documentation with ctx7 docs.

Frequently Asked Questions about find-docs

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

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

To find up-to-date API references and code examples, resolve the library name to a Context7-compatible library ID, then query its documentation using the recommended ctx7 docs command to surface current details.

What is the best way to look up current documentation for developer frameworks?

The best way to look up current documentation for developer frameworks is using a two-step workflow that resolves the exact library ID first, ensuring you retrieve authoritative, up-to-date docs instead of outdated search results.

Can I search for configuration details and migration notes using library lookup tools?

Yes, you can search for configuration details and migration notes by querying the resolved library ID, which surfaces specific API references and code examples relevant to your developer technology stack.

Do I need a specific library ID before querying API references?

Yes, you need a specific Context7-compatible library ID before querying API references, because the documentation search workflow requires resolving the library name first to accurately target and retrieve the correct docs.

Why does documentation search require resolving a library name first?

Documentation search requires resolving a library name first to disambiguate similar packages and target the exact Context7-compatible library ID, ensuring the subsequent docs query returns accurate, current API references and code examples.

What are the limitations of using automated library lookup for current docs?

A limitation of automated library lookup is that documentation retrieval depends entirely on successfully resolving a Context7-compatible library ID first; if the library name is ambiguous or unsupported, the docs query cannot proceed.