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".

Quality

87%

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

100%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 body is a tightly scoped, fully actionable documentation-fix workflow with concrete commands, explicit validation checkpoints, and clean structure. It assumes Claude's competence and every section earns its place.

Dimension	Reasoning	Score
Conciseness	Lean body with no explanations of concepts Claude already knows; every line is an instruction, command, or constraint, and each token earns its place.	5 / 5
Actionability	Provides copy-paste-ready commands throughout — branch creation, lint invocation, the full commit heredoc, and staged-file verification — covering the common case completely.	5 / 5
Workflow Clarity	Clear numbered sequence with explicit validation checkpoints (auto-format hook, manual lint, self-review re-read, git diff verification) and a stop-and-report blocker loop for unverifiable URLs.	5 / 5
Progressive Disclosure	Under 50 lines, single-purpose, and well-organized into numbered sections plus Notes; references are one level deep and the bundled hook script (scripts/post-edit.sh) is real.	5 / 5
	Total	20 / 20 Passed

Description

75%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 clearly states what the skill does and when to use it, with concrete actions and natural trigger phrases. It is mostly distinct and specific, with minor room to add synonyms and sharpen the use-when phrasing.

Suggestions

Add a few natural synonyms such as "edit the docs" or "apply the documentation fix" to broaden trigger coverage.

Reframe the "Use after research has identified what to change" clause as an explicit user-facing trigger (e.g. "Use when the user asks to write or apply a documentation fix") so the "when" is phrased as something a user would say.

Consider naming the artifact type once ("documentation page") in the action list to further reduce overlap with code-fixing skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Makes the minimal change, formats, self-reviews, and commits" — naming the domain and multiple specific steps with only minor gaps in coverage.	4 / 5
Completeness	Has a clear "what" (minimal change, format, self-review, commit) and an explicit "when" ("Use after research has identified what to change"), though the trigger is workflow-stage-oriented rather than fully user-phrase-oriented.	4 / 5
Trigger Term Quality	Includes natural phrases users would say — "write the fix", "make the changes", "implement the fix for #1234" — with good keyword coverage, missing only a few synonyms.	4 / 5
Distinctiveness Conflict Risk	Scoped to "documentation fix on a branch" with issue-numbered trigger phrases, making it mostly distinct with only minor overlap risk against closely related editing skills.	4 / 5
	Total	16 / 20 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
Path: .agents/skills/write/SKILL.md
Commit: ff96ad1

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