How do I install the Find Docs skill?

Run npx skillmds@latest add conava/find-docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Find Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Find Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Find Docs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Find Docs?

Conava (@conava) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Find Docs by conava — Agent Skill

Name: Find Docs
Rating: 4.666666666666667 (3 reviews)
Author: Conava

Find Docs

Retrieves authoritative, up-to-date technical documentation, API references, configuration details, and code examples for any developer technology. Use this skill whenever answering technical questions or writing code that interacts with external technologies. This includes libraries, frameworks, programming languages, SDKs, APIs, CLI tools, cloud services, infrastructure tools, and developer platforms. Common scenarios: - looking up API endpoints, classes, functions, or method parameters - checking configuration options or CLI commands - answering "how do I" technical questions - generating code that uses a specific library or service - debugging issues related to frameworks, SDKs, or APIs - retrieving setup instructions, examples, or migration guides - verifying version-specific behavior or breaking changes Prefer this skill whenever documentation accuracy matters or when model knowledge may be outdated.

Conava Updated Sep 10, 2026

File contents

Documentation Lookup

Fetch current library docs and code examples via the Context7 CLI — at plan or implementation time, whenever doc accuracy matters or model knowledge may be stale.

Two steps: resolve the name to a /org/project ID, then fetch docs. Always pass a specific query (the user's full question, not a single word) — it drives result ranking. Never put secrets (API keys, credentials) in a query.

# 1. Resolve the library ID (skip only if the user gave an explicit /org/project[/version] ID)
npx -y ctx7 library react "How to clean up useEffect with async operations"

# 2. Fetch docs with that ID
npx -y ctx7 docs /facebook/react "How to clean up useEffect with async operations"

# version-specific ID (versions are listed in the library output):
npx -y ctx7 docs /vercel/next.js/v14.3.0-canary.87 "How to set up app router"

Pick the best match from step 1 by name/description relevance, code-snippet count, and source reputation. Max 3 attempts per question, then use the best result you have.

Critical gotchas: library IDs need the / prefix (/facebook/react, not facebook/react); docs needs a real ID from step 1 (docs react "hooks" fails).

Rate limits: works unauthenticated; for higher limits set CONTEXT7_API_KEY (or npx -y ctx7 login). On a quota error, tell the user why Context7 was skipped, suggest authenticating, and if they decline, answer from training knowledge noting it may be outdated — never fall back silently.

---name: find-docsdescription: Retrieves authoritative, up-to-date technical documentation, API references, configuration details, and code examples for any developer technology. Use this skill whenever answering technical questions or writing code that interacts with external technologies. This includes libraries, frameworks, programming languages, SDKs, APIs, CLI tools, cloud services, infrastructure tools, and developer platforms. Common scenarios: - looking up API endpoints, classes, functions, or method parameters - checking configuration options or CLI commands - answering "how do I" technical questions - generating code that uses a specific library or service - debugging issues related to frameworks, SDKs, or APIs - retrieving setup instructions, examples, or migration guides - verifying version-specific behavior or breaking changes Prefer this skill whenever documentation accuracy matters or when model knowledge may be outdated.---# Documentation LookupFetch current library docs and code examples via the Context7 CLI — at plan orimplementation time, whenever doc accuracy matters or model knowledge may be stale.Two steps: resolve the name to a `/org/project` ID, then fetch docs. Always pass aspecific query (the user's full question, not a single word) — it drives result ranking.Never put secrets (API keys, credentials) in a query.```bash# 1. Resolve the library ID (skip only if the user gave an explicit /org/project[/version] ID)npx -y ctx7 library react "How to clean up useEffect with async operations"# 2. Fetch docs with that IDnpx -y ctx7 docs /facebook/react "How to clean up useEffect with async operations"# version-specific ID (versions are listed in the library output):npx -y ctx7 docs /vercel/next.js/v14.3.0-canary.87 "How to set up app router"```Pick the best match from step 1 by name/description relevance, code-snippet count, andsource reputation. Max 3 attempts per question, then use the best result you have.Critical gotchas: library IDs need the `/` prefix (`/facebook/react`, not `facebook/react`);`docs` needs a real ID from step 1 (`docs react "hooks"` fails).**Rate limits:** works unauthenticated; for higher limits set `CONTEXT7_API_KEY` (or`npx -y ctx7 login`). On a quota error, tell the user why Context7 was skipped, suggestauthenticating, and if they decline, answer from training knowledge noting it may beoutdated — never fall back silently.

Frequently asked questions