find-docs

Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer — do not rely on training data for API details, signatures, or configuration options as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and well-structured with a clear two-step workflow and guardrails, but it loses token efficiency by repeating the same command examples across multiple sections. Consolidating the duplicated invocations would tighten it without losing clarity.

Suggestions

Remove the duplicate `npx ctx7@latest library`/`docs` command blocks: show each invocation once in its Step section rather than repeating them in the intro and Workflow overview.

Tighten restatement sentences like 'Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.' since the surrounding examples already convey this.

Consider adding an explicit output-validation checkpoint (e.g., confirm the returned library ID format before running `docs`) to push workflow clarity from guardrails toward a full validate-then-proceed loop.

Dimension	Reasoning	Score
Conciseness	The body restates the same `library` and `docs` command invocations three times (intro, Workflow, and per-step sections) and includes mild restatement sentences, which is noticeable padding even though no basic concepts are over-explained.	3 / 5
Actionability	Fully executable, copy-paste-ready commands with concrete worked examples (React, Next.js, Prisma) and a good/bad query table that covers the common cases.	5 / 5
Workflow Clarity	The two-step resolve-then-query process is clearly sequenced with explicit guardrails and a quota-error feedback loop, but checkpoints are guardrails rather than an explicit validate-then-retry on output.	4 / 5
Progressive Disclosure	No bundle files exist and the body references none; the self-contained doc is well-organized into clear sections (Workflow, Step 1/2, Authentication, Error Handling, Common Mistakes), satisfying the simple-skill exception for well-organized single-file skills.	5 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across all dimensions: it states concrete capabilities, provides comprehensive natural trigger terms, explicitly covers both what and when, and occupies a distinct niche. It is slightly verbose but the verbosity does not cross into fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Retrieves up-to-date documentation, API references, and code examples') plus explicit enumerated use-cases, matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both what ('Retrieves up-to-date documentation, API references, and code examples') and when ('Use this skill whenever the user asks about...'; 'Always use for:...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural terms ('library, framework, SDK, CLI tool, or cloud service') with named examples (React, Next.js, Prisma) and common phrasings like 'API syntax questions' and 'version migration issues'.	5 / 5
Distinctiveness Conflict Risk	Clear niche (current developer-tech documentation via CLI lookup) with distinct, specific triggers and minimal overlap with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: upstash/context7
Path: skills/find-docs/SKILL.md
Commit: 4e980f6

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.