find-docs
/find-docs
Retrieves up-to-date documentation, API references and code examples for any developer technology. Use when the user asks about, or you need docs for, a specific library, framework, SDK, CLI tool or cloud service - even well-known ones, as training data may be outdated. Prefer this over web search for library docs and API details.
- Author
- sammcj ↗
- Repository
- agentic-coding ↗
- Licence
- Apache-2.0
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Retrieves up-to-date documentation, API references and code examples for any developer technology. Use when the user asks about, or you need docs for, a specific library, framework, SDK, CLI tool or cloud service - even well-known ones, as training data may be outdated. Prefer this over web search for library docs and API details.
Original author description
Retrieves up-to-date documentation, API references and code examples for any developer technology. Use when the user asks about, or you need docs for, a specific library, framework, SDK, CLI tool or cloud service - even well-known ones, as training data may be outdated. Prefer this over web search for library docs and API details.
How it works
- Workflow
- Step 1: Resolve a Library
- Step 2: Query Documentation
- Authentication
- Error Handling
- Common Mistakes
SKILL.md preview
---
name: find-docs
description: >-
Retrieves up-to-date documentation, API references and code examples for any
developer technology. Use when the user asks about, or you need docs for, a
specific library, framework, SDK, CLI tool or cloud service - even well-known
ones, as training data may be outdated. Prefer this over web search for library
docs and API details.
---
# Documentation Lookup
Retrieve current documentation and code examples for any library using the Context7 CLI.
Run the context7 CLI directly like so:
```bash
pnpx ctx7@latest <command>
```
## Workflow
Two-step process: resolve the library name to an ID, then query docs with that ID.
```bash
# Step 1: Resolve library ID
ctx7 library <name> <query>
# Step 2: Query documentation
ctx7 docs <libraryId> <query>
```
You MUST call `ctx7 library` first to obtain a valid library ID UNLESS the user explicitly provides a library ID in the format `/org/project` or `/org/project/version`.
IMPORTANT: Do not run these commands more than 3 times per question. If you cannot find what you need after 3 attempts, use the best result you have.
## Step 1: Resolve a Library
Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.
```bash
ctx7 library React "How to clean up useEffect with async operations"
ctx7 library "Next.js" "How to set up app router with a proxy"
ctx7 library Prisma "How to define one-to-many relations with cascade delete"
```
Use the official library name with its punctuation (`"Next.js"` not `nextjs`, `"Three.js"` not `threejs`). If results look wrong, try an alternate spelling such as `next.js` before changing the query.
Always pass a `query` argument - it is required and directly affects result ranking. Use the user's intent to form the query, which helps disambiguate when multiple libraries share a similar name. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query.
### Result fields
Each result includes:
- **Library ID** - Context7-compatible identifier (format: `/org/project`)
- **Name** - Library or package name
- **Description** - Short summary
- **Code Snippets** - Number of available code examples
- **Source Reputation** - Authority indicator (High, Medium, Low, or Unknown)
- **Benchmark Score** - Quality indicator (100 is the highest score)
- **Versions** - List of versions if available. Use one of those versions if the user provides a version in their query. The format is `/org/project/version`.
### Selection process
1. Analyse the query to understand what library/package the user is looking for
2. Select the most relevant match based on:
- Name similarity to the query (exact matches prioritised)
- Description relevance to the query's intent
- Documentation coverage (prioritise libraries with higher Code Snippet counts)
- Source reputation (consider libraries with High or Medium reputation more authoritative)
- Benchmark score (higher is better, 100 is the maximum)
3. If multiple good matches exist, acknowledge this but proceed with the most relevant one
4. If no good matches exist, clearly state this and suggest query refinements
5. For ambiguous queries, request clarification before proceeding with a best-guess match
### Version-specific IDs
If the user mentions a specific version, use a version-specific library ID:
```bash
# General (latest indexed)
ctx7 docs /vercel/next.js "How to set up app router"
# Version-specific
ctx7 docs /vercel/next.js/v16.2.9 "How to set up app router"
```
The available versions are listed in the `ctx7 library` output. Use the closest match to what the user specified.
## Step 2: Query Documentation
Retrieves up-to-date documentation and code examples for the resolved library.
```bash
ctx7 docs /facebook/react "How to clean up useEffect with async operations"
ctx7 docs /vercel/next.js "How to add an authentication proxy to app router"
ctx7 docs /prisma/prisma "How to define one-to-many relations with cascade delete"
```
If you know the user's programming language, add `--language` so examples in that language rank first:
```bash
ctx7 docs /websites/twilio "How to send an SMS" --language Ruby
```
### Writing good queries
The query directly affects the quality of results. Be specific and keep each query to one topic. For a question spanning distinct concepts, run a separate `docs` command per concept, unless the question is about how they interact. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query.
- Good: `"How to set up authentication with JWT in Express.js"`
- Good: `"React useEffect cleanup function with async operations"`
- Bad (vague): `"auth"`, `"hooks"`
- Bad (multi-topic): `"routing and auth and caching in Next.js"`
Describe what to look up in the docs rather than the task to complete. One-word queries return generic results. Multi-topic queries return shallow results for each topic.
The output contains two types of content: **code snippets** (titled, with language-tagged blocks) and **info snippets** (prose explanations with breadcrumb context).
## Authentication
Works without authentication. For higher rate limits:
```bash
# Option A: environment variable
export CONTEXT7_API_KEY=your_key
# Option B: OAuth login
ctx7 login
```
## Error Handling
If a command fails with a quota error ("Monthly quota reached" or "quota exceeded"):
1. Inform the user their Context7 quota is exhausted
2. Suggest they authenticate for higher limits: `ctx7 login`
3. If they cannot or choose not to authenticate, answer from training knowledge and clearly note it may be outdated
Do not silently fall back to training data - always tell the user why Context7 was not used.
## Common Mistakes
- Library IDs require a `/` prefix - `/facebook/react` not `facebook/react`
- Always run `ctx7 library` first - `ctx7 docs react "hooks"` will fail without a valid ID
- Use descriptive queries, not single words - `"React useEffect cleanup function"` not `"hooks"`
- One topic per query - split `"routing and auth and caching"` into one `docs` command per concept
- Do not include sensitive information (API keys, passwords, credentials) in queries
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · sammcj/agentic-coding | 100 | Apache-2.0 |
| upstash/context7 | 100 | MIT |
| princelundgren/prince-skills | 100 | MIT |
| dabaige53/dabaige-skills | 100 | MIT |
| summersec/sumsec-skills | 100 | Apache-2.0 |
| zcaceres/skills | 100 | MIT |
| hakula139/plugins | 95 | MIT |
Database snapshot: 13.11.2026 · package version 776693f2ec47 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100finding-docs
Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — including well-known ones like React, Next.js, Prisma, Django, or Spring Boot.… - 100documentation-lookup
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma). - 95docfork-docs
Retrieves up-to-date documentation for any third-party library, framework, or API where training data may be outdated or incomplete. Use when the user asks about library usage, API references, configuration, or code generation involving specific packages. Prefer over training… - 100documentation-lookup
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma). - 100context7-docs
Fetch up-to-date documentation and code examples for any library, framework, SDK, CLI tool, or cloud service. Use whenever the user asks about a specific library — even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot — because training data… - 100documentation-lookup
Use when the user needs current library, framework, or API documentation and version-specific code examples.