write

Write a documentation fix on a branch. Makes the minimal change, formats, self-reviews, and commits. Use after research has identified what to change. "write the fix", "make the changes", "implement the fix for #1234".

1.35x

Quality

—

Does it follow best practices?

Impact

99%

1.35x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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

A tight, well-sequenced workflow skill with concrete executable commands and validation checkpoints at every risky step. It is self-contained and appropriately concise without any padding.

Dimension	Reasoning	Score
Conciseness	The body is lean: each section is a terse directive with commands and no explanation of concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	Executable commands appear throughout (git checkout -b, scripts/lint.sh, git diff) and the commit step is a complete copy-paste-ready heredoc template.	3 / 3
Workflow Clarity	A clear numbered sequence (branch → edit → front matter → validate → self-review → commit) with explicit checkpoints: prettier hook, lint, git diff self-review, and staged-file verification.	3 / 3
Progressive Disclosure	Under 50 lines with no need for external references; the body is a single self-contained file organized into well-labeled numbered sections, meeting the simple-skill standard for a 3.	3 / 3
	Total	12 / 12 Passed

Description

100%

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 states concrete capabilities, provides natural trigger terms, and gives explicit when-to-use guidance gated on prior research. It is clearly scoped to documentation fixes with low conflict risk.

Dimension	Reasoning	Score
Specificity	"Makes the minimal change, formats, self-reviews, and commits" lists multiple specific concrete actions matching the score-3 anchor.	3 / 3
Completeness	It states what (edit, format, self-review, commit) and an explicit "Use after research has identified what to change" when-clause, answering both clearly.	3 / 3
Trigger Term Quality	"write the fix", "make the changes", "implement the fix for #1234" are natural phrases a user would say when they need this skill, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	"Write a documentation fix on a branch" plus the research-gated trigger carves a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: docker/docs
Commit: 67d0999

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.