doc-review

Reviews documentation for factual accuracy

Quality

50%

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 ./.claude/skills/doc-review/SKILL.md

Quality

Content

50%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 skill body is well-organized and concise but lacks concrete executable guidance and validation steps, and its referenced bundle files (CHECKING.md, EXAMPLES.md) are missing. The workflow is a reasonable skeleton but stays at a high level.

Suggestions

Provide or restore the referenced CHECKING.md and EXAMPLES.md bundle files so the fact-checking guidance is actually reachable, or inline the essential checking procedure directly.

Add concrete, executable steps to the fact-checking workflow (e.g., specific commands or methods to verify links and claims) rather than only high-level directives.

Add a validation/checklist step confirming the review is complete before producing the report, since the workflow currently has no verification checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean with short instructions and no over-explanation of concepts Claude already knows, but a few phrases like 'Make sure that all claims...' could be tightened slightly, fitting the 'efficient with minor trimming' anchor.	4 / 5
Actionability	Guidance is high-level ('Make sure all claims are accurate', 'check for formatting, typos') with no concrete commands or specific procedures, and defers detail to CHECKING.md which is not present in the bundle.	2 / 5
Workflow Clarity	A numbered 1-4 sequence is present, but steps are generic ('Read the documentation', 'Make sure claims are accurate') with no validation checkpoints to confirm findings are complete.	3 / 5
Progressive Disclosure	The body signals one-level-deep references to CHECKING.md and EXAMPLES.md under a fact-checking section, but neither file exists in the bundle, leaving the references broken and reducing navigation value.	3 / 5
	Total	12 / 20 Passed

Description

50%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 concise and states a clear purpose but is generic, lacking explicit trigger guidance and concrete action detail. It reads as a one-line summary rather than a discovery-optimized description.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases users would say (e.g., 'Use when reviewing toolhive docs for accuracy, fact-checking claims, or verifying links').

List concrete actions the skill performs (e.g., 'Verifies toolhive claims, checks examples for accuracy, validates links point to existing files').

Include natural keyword variations like 'docs', 'fact-check', and 'verify claims' to improve trigger matching.

Dimension	Reasoning	Score
Specificity	Names the domain (documentation) and one concrete action (reviewing for factual accuracy), but lists no further specific actions, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Provides a clear 'what' (reviews documentation for factual accuracy) but lacks any explicit 'when' / 'Use when' trigger clause, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Contains relevant keywords ('documentation', 'factual accuracy') but misses common natural variations a user would say ('docs', 'fact-check', 'verify claims'), fitting the 'some keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The fact-checking niche is somewhat specific, but the broad term 'documentation' leaves overlap risk with general documentation skills, fitting the 'somewhat specific but could still overlap' anchor.	3 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: stacklok/toolhive
Path: .claude/skills/doc-review/SKILL.md
Commit: ccabad6

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