documentation-build

Validates documentation builds successfully. Use when checking Sphinx/RTD build integrity or diagnosing build failures. Reports errors, warnings, and build configuration issues.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

The body is a tight, executable build-validation procedure with explicit validation/retry checkpoints and a completion checklist. It avoids concept padding and is well-organized for a single-purpose skill.

Dimension	Reasoning	Score
Conciseness	Lean procedural spec that assumes Claude's competence — it never explains what Sphinx/RTD is, and every section (Scope, Inputs, Actions, Constraints, Output) earns its place.	3 / 3
Actionability	Provides fully executable commands (make clean, make html, a real for-loop probing targets) and concrete search heuristics, copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	Six clearly sequenced steps with an explicit feedback loop in step 4 (capture, clean, retry, stop) and a verification checklist in step 6, appropriate for batch build operations.	3 / 3
Progressive Disclosure	A single-purpose skill with well-organized sections and no need for external references; structure is clear and navigable without any bundle files.	3 / 3
	Total	12 / 12 Passed

Description

100%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 concise, third-person description that clearly states capabilities and provides an explicit use-when trigger. It is specific, naturally worded, and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Names several concrete actions — "Validates documentation builds", "Reports errors, warnings, and build configuration issues" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly answers both what (validates builds, reports errors/warnings/config issues) and when ("Use when checking Sphinx/RTD build integrity or diagnosing build failures").	3 / 3
Trigger Term Quality	Includes natural terms a user would say — "Sphinx/RTD build integrity", "diagnosing build failures", "documentation builds" — giving good coverage rather than jargon.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (documentation build validation) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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-build/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.