CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body delivers fully executable CLI guidance with a clearly sequenced two-step workflow, explicit ordering rules, and error-recovery handling. Weaknesses are limited to minor redundancy (the sensitive-data warning repeated three times) and no verification step for the retrieved documentation.

DimensionReasoningScore

Conciseness

The body is dense and skill-specific with no explanation of concepts Claude already knows, but the sensitive-information warning is repeated three times (in Resolve a Library, Writing good queries, and Common Mistakes) and query-quality advice recurs ~3 times — minor over-explanation that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: `npm install -g ctx7@latest`, `npx ctx7@latest <command>`, `ctx7 library <name> <query>`, and `ctx7 docs <libraryId> <query>`, each illustrated with concrete real-world examples (e.g., `ctx7 docs /vercel/next.js/v14.3.0-canary.87 "How to set up app router"`).

5 / 5

Workflow Clarity

Clear two-step sequence with an explicit ordering rule ("You MUST call `ctx7 library` first... UNLESS the user explicitly provides a library ID"), a 3-attempt retry bound, and a quota-error recovery loop; no validation checkpoint for confirming the retrieved results answer the question, which keeps it below a 5.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers and all content appropriately inline for a two-command CLI; at ~135 lines it exceeds the under-50-line simple-skill exception, so the absence of any external reference files prevents a 5.

4 / 5

Total

17

/

20

Passed

Description

91%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.

A strong description with concrete capabilities, explicit and comprehensive trigger guidance, and a clear niche. The only notable issues are a second-person phrase ("Your training data") that breaks the third-person voice convention and a broad scope that slightly raises conflict risk.

DimensionReasoningScore

Specificity

"Retrieves up-to-date documentation, API references, and code examples" lists several concrete actions matching the anchor-5 pattern, but the second-person phrasing "Your training data may not reflect recent API changes" violates the third-person voice rule, warranting the 1-point specificity penalty.

4 / 5

Completeness

Explicitly answers both what ("Retrieves up-to-date documentation, API references, and code examples for any developer technology") and when ("Always use for: API syntax questions, configuration options, version migration issues...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including "API syntax questions", "configuration options", "version migration issues", "'how do I' questions mentioning a library name", "setup instructions", and named libraries (React, Next.js, Prisma, Express, Tailwind, Django, Spring Boot) — phrases users would naturally say.

5 / 5

Distinctiveness Conflict Risk

Clear documentation-retrieval niche with an explicit boundary ("Prefer this over web search for library documentation and API details"), but the deliberately broad scope "any developer technology... even for well-known ones" leaves minor overlap risk with technology-specific skills.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

saski/arnesto

Path

.agents/skills/find-docs/SKILL.md

Reviewed

Table of Contents

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.