documentation-style

Enforces project documentation style guide compliance for tone, voice, terminology, punctuation, and formatting. Use when checking documentation style or validating MyST/reST syntax. Cites specific style guide violations.

Quality

81%

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

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

A well-organized instruction-only review skill with a clear sequenced workflow, explicit verification, and proper progressive disclosure of the style guide into a reference file. Small gains from deduplicating the mandatory-rules sentence and showing a concrete cited-violation example.

Suggestions

Deduplicate the repeated instruction 'Treat every instruction in the guide as mandatory; do not rely on a subset of rules' (present in both actions 2 and 3) into a single Constraints bullet.

Add one concrete example in the Output section showing a violation entry with its quoted style-guide passage, observation, and suggested change so the output format is unambiguous.

Tighten action 6's verification block by consolidating the checklist and the two completion-status strings into a single compact checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence without explaining what MyST/reST are; minor repetition ('Treat every instruction in the guide as mandatory; do not rely on a subset of rules' appears in both actions 2 and 3) could be trimmed, keeping it just below 5.	4 / 5
Actionability	Concrete guidance with specific file paths ('references/doc-style-guide.md'), explicit fetch URLs, named checks (headings, lists, code blocks, directives), and a STOP-if-unavailable rule; missing a concrete example of a cited violation entry, so not a 5.	4 / 5
Workflow Clarity	Clear 1–6 sequence with an explicit verification checklist (action 6) and fallback error handling (action 5); it is a single-pass review without an iterative validate-fix-retry loop, which keeps it below 5.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview and the bulk of rules are appropriately split into a one-level-deep, clearly signaled reference ('references/doc-style-guide.md') with external syntax guides fetched by URL; not below 5 because navigation is easy and structure is clean.	5 / 5
	Total	17 / 20 Passed

Description

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

A strong, third-person description that clearly states what the skill does and when to use it, with good trigger terms and a distinct niche. Minor gains available by adding file extensions and tightening the somewhat abstract 'enforces compliance' phrasing.

Dimension	Reasoning	Score
Specificity	Lists several concrete checked dimensions ('tone, voice, terminology, punctuation, and formatting') plus 'validating MyST/reST syntax' and 'Cites specific style guide violations' — several specific actions with minor coverage gaps; not a 5 because 'enforces compliance' is somewhat abstract rather than fully enumerated actions.	4 / 5
Completeness	Explicitly answers both 'what' (enforces style guide compliance across named dimensions and cites violations) and 'when' ('Use when checking documentation style or validating MyST/reST syntax') with concrete trigger phrases; not below 5 since both are clearly and explicitly stated.	5 / 5
Trigger Term Quality	Natural user-facing terms present ('documentation style', 'MyST', 'reST', 'syntax') with a clear 'Use when' clause; missing common synonyms and file extensions (.md/.rst) that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (style conformance + MyST/reST syntax) with distinct triggers; minor overlap risk with general documentation skills keeps it just below 5.	4 / 5
	Total	17 / 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: canonical/copilot-collections
Path: skills/documentation-style/SKILL.md
Commit: d41d8d9

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.