documentation-lookup

Use when the user needs current library, framework, or API documentation and version-specific code examples.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/documentation-lookup/SKILL.md

Quality

Content

86%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 is an efficient, well-structured instruction-only skill that tells Claude exactly what to do without padding. Its main gap is the absence of an explicit validation step confirming the retrieved documentation actually matches the requested version before citing it.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what documentation or libraries are, and every line (workflow steps, selection rules, fallback) earns its place.	5 / 5
Actionability	Concrete, specific instructional guidance ('Identify the exact project, package, and version', 'Read only the pages needed', 'Cite the official page or local source path'); as an instruction-only skill code absence is not penalized, but it stops short of copy-paste-ready specifics.	4 / 5
Workflow Clarity	A clear five-step sequence with a built-in fallback ('If a current official source is unavailable, say what could not be verified and do not guess'), though it lacks an explicit verification checkpoint confirming the cited source matches the requested version.	4 / 5
Progressive Disclosure	A short single-purpose skill under 50 lines with no need for external references; it is well-organized into Workflow and Selection Rules sections, satisfying the simple-skill exception for a top score.	5 / 5
	Total	18 / 20 Passed

Description

56%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 a strong, natural trigger clause but functions more as a 'when' than a 'what' — it names the domain without listing concrete actions the skill performs. Adding explicit verbs (e.g., 'fetches, reads, and cites') would raise specificity and completeness.

Suggestions

Add explicit concrete actions to the 'what' (e.g., 'Fetches and reads current official documentation, then cites the source and version') so both what and when are explicitly stated.

Include common synonyms like 'docs', 'reference docs', or 'API reference' to broaden natural trigger coverage.

Tighten the version trigger by mentioning version pinning (e.g., 'when the answer depends on a specific version of a library, framework, or API').

Dimension	Reasoning	Score
Specificity	The description names the domain ('library, framework, or API documentation') but provides no concrete actions — it is essentially a trigger clause with a domain, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It has a clear 'when' ('Use when the user needs current... documentation') but the 'what' is only weakly implied rather than stated as concrete actions, matching the 'clear what but when weakly implied' inverse and the cap for missing explicit what detail.	3 / 5
Trigger Term Quality	Good coverage of natural phrases users would say ('library, framework, or API documentation', 'version-specific code examples'), though it omits common synonyms like 'docs', 'reference', or file extensions.	4 / 5
Distinctiveness Conflict Risk	The trigger around 'current... documentation' and 'version-specific code examples' is fairly distinct, with only minor overlap risk against general coding/research skills.	4 / 5
	Total	13 / 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: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/documentation-lookup/SKILL.md
Commit: d5ae560

Reviewed: 1 day 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.