documentation-review

Performs comprehensive documentation review including build validation, Diataxis analysis, structure audit, accuracy verification, and style compliance. Use when reviewing documentation changes or auditing documentation quality.

Quality

85%

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%Weight 40%Scale 1-3

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

A well-structured orchestration skill with exemplary workflow clarity and actionability, plus a clean one-level reference to the report template. The main weakness is repetition of the checkpoint/verification pattern across stages.

Suggestions

Factor the repeated Execute/Capture/Verify/Checkpoint pattern into a single stated template applied per stage, rather than re-emitting the full pattern for each of the seven stages.

Consider moving the Stage 7 assembly table and priority-order detail into the report template reference to trim the core workflow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and operational, but the Execute/Capture/Verify/Checkpoint pattern and verification phrasing repeat across all seven stages, adding tokens that could be templated or tightened.	2 / 3
Actionability	Gives concrete skill names to invoke, exact checkpoint string formats, a skill-to-report-section mapping table, and specific error-handling procedures — fully actionable.	3 / 3
Workflow Clarity	A clearly sequenced 7-stage workflow with explicit per-stage checkpoints, a build-failure decision point that halts the pipeline, and structured error recovery — matching the top anchor.	3 / 3
Progressive Disclosure	The body is an orchestration overview with a single clearly-signaled one-level-deep reference to references/doc-review-report-template.md (a real file), and content is appropriately inline rather than nested.	3 / 3
	Total	11 / 12 Passed

Description

85%Weight 40%Scale 1-3

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 that names concrete capabilities and provides an explicit use-when trigger, with third-person voice throughout. Trigger-term coverage is the only weak spot, being somewhat narrow.

Suggestions

Broaden trigger terms to include common phrasings users actually say, e.g. 'Use when reviewing or auditing documentation, checking docs quality, or reviewing documentation changes'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'build validation, Diataxis analysis, structure audit, accuracy verification, and style compliance' — matching the top anchor.	3 / 3
Completeness	Explicitly answers both what ('Performs comprehensive documentation review including...') and when ('Use when reviewing documentation changes or auditing documentation quality').	3 / 3
Trigger Term Quality	'reviewing documentation changes or auditing documentation quality' are natural phrases but coverage is narrow, missing common variations a user would say like 'docs' or 'check my documentation'.	2 / 3
Distinctiveness Conflict Risk	Clear niche as a comprehensive documentation-review orchestration skill with distinct triggers, unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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: canonical/copilot-collections
Path: skills/documentation-review/SKILL.md
Commit: 0fe9990

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