documentation-lookup

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

Quality

83%

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

Quality

Content

85%

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

The body is concise, well-structured, and provides a clear sequenced workflow with an explicit no-guess verification checkpoint, but it lacks concrete executable code or commands showing how to actually fetch the documentation.

Suggestions

Add a small executable example of reaching an official source (e.g., a `pydoc`/`ripgrep`-over-vendored-source command or a WebFetch of an official docs URL) to lift actionability toward copy-paste-ready.

Optionally name one or two concrete source types per step (e.g., `pip show <pkg>` to find the installed version, then read its site-packages) instead of only describing the preference.

Consider a short 'Selection Rules' mini-checklist format to make the verification heuristic even more directly actionable.

Dimension	Reasoning	Score
Conciseness	The body is a lean ~20 lines with no padding and no explanation of concepts Claude already knows (e.g., what a library or API is); every line gives actionable guidance, matching the 'lean and efficient; every token earns its place' anchor rather than score 2's 'some unnecessary explanation'.	3 / 3
Actionability	Steps are concrete and directive ('Prefer an installed documentation set, package source, or purpose-built connector...') but there is no executable code, command, or copy-paste example of how to actually reach the official source, matching the 'some concrete guidance but incomplete' anchor rather than the fully executable score-3 example.	2 / 3
Workflow Clarity	The five numbered steps form a clear sequence with an explicit verification/fallback checkpoint ('If a current official source is unavailable, say what could not be verified and do not guess'), matching the 'clear sequence with explicit validation steps' anchor; it is not score 2 because the feedback/checkpoint is explicit.	3 / 3
Progressive Disclosure	This is a short single-purpose skill with well-organized sections (Workflow, Selection Rules) and no bundle files or nested references, which the rubric's simple-skills note says can score 3 with just well-organized sections; it is not score 2 because the content is appropriately split and not a monolithic wall.	3 / 3
	Total	11 / 12 Passed

Description

82%

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 concise and uses an explicit 'Use when...' trigger with natural user-facing terms, but it lists only one concrete capability and its domain is broad enough to risk overlap with general coding/web-search skills.

Suggestions

Add one or two more concrete capabilities (e.g., 'fetch current API references and version-matched code examples') to lift specificity from domain-and-some-actions to a multi-action list.

Narrow the trigger to reduce overlap, e.g. 'Use when an answer depends on current, version-specific library/framework/API docs rather than general knowledge.'

Mirror common user phrasings explicitly (e.g., 'latest docs', 'API reference', 'syntax for version X') to reinforce trigger-term distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names a clear domain ('current library, framework, or API documentation') and one concrete deliverable ('version-specific code examples'), but does not list multiple specific actions like extracting, filling, or merging, so it matches the 'names domain and some actions, but not comprehensive' anchor rather than score 3.	2 / 3
Completeness	It opens with an explicit 'Use when the user needs...' trigger and states the skill's purpose (current documentation lookup), clearly answering both 'what' and 'when', matching the top anchor; it is not score 2 because the when-clause is explicit rather than merely implied.	3 / 3
Trigger Term Quality	It uses natural phrasing a user would say ('current library, framework, or API documentation' and 'version-specific code examples'), covering common variations rather than jargon, matching the 'good coverage of natural terms users would say' anchor; not score 2 because the terms are what users actually request.	3 / 3
Distinctiveness Conflict Risk	The 'documentation lookup' niche is fairly specific, but 'library, framework, or API documentation' is broad enough that it could overlap with general coding-assist or web-search skills, matching the 'somewhat specific but could still overlap' anchor rather than a clearly distinct niche at score 3.	2 / 3
	Total	10 / 12 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: f627ab5

Reviewed: about 9 hours 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.