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

92%

Does it follow best practices?

Impact

99%

1.35x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Evaluation results

100%

40%

Quickstart Guide Deployment Command Fix

Front matter and commit format

Criteria

Without context

With context

Branch name pattern

100%

Branch from main

100%

keywords added

100%

title present

100%

description present

100%

Flag corrected

100%

Minimal change only

100%

Commit subject prefix

100%

Commit references issue

100%

Commit body: what was wrong

100%

Commit body: what was changed

100%

Co-Authored-By trailer

100%

Deployment Guide Environment Variable Update

Vendor protection and staging discipline

Criteria

Without context

With context

Branch name pattern

100%

_vendor/ untouched

100%

monitoring.md untouched

100%

Content fix correct

100%

Commit subject prefix

70%

100%

Commit references issue

100%

Commit subject length

100%

Commit body: what was wrong

100%

Commit body: what was changed

100%

Co-Authored-By trailer

100%

97%

28%

API Reference Health Endpoint Correction

Lint fixes and minimal change discipline

Criteria

Without context

With context

Branch name pattern

100%

Status code corrected

100%

Headings have surrounding blank lines

100%

No skipped heading levels

100%

Code blocks have language

100%

Minimal change only

70%

Commit subject prefix

100%

Commit references issue

100%

Commit body: what was wrong

100%

Commit body: what was changed

100%

Co-Authored-By trailer

100%

Repository: docker/docs
Commit: 2ea4a02

Evaluated: 9 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Quickstart Guide Deployment Command Fix Deployment Guide Environment Variable Update API Reference Health Endpoint Correction

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.