Conciseness

About 25 lean lines with zero explanation of concepts Claude already knows; every line encodes project policy Claude cannot infer ('A second identical failure is a defect, not a flake: diagnose it instead of a third retry'), so every token earns its place.

Actionability

Concrete where it counts — it names the checks file 'docs/development/quality-gates.md' and gives an executable command 'git merge-base --is-ancestor origin/main HEAD' — but steps 1, 7, and 8 ('Inspect the merged tree for conflict markers', 'Return every touched checkout to a clean, synchronized state') state what to do without the specific commands, matching 'mostly executable guidance with minor gaps'.

Workflow Clarity

A clear 1–8 sequence with explicit validation checkpoints (re-run quality gates, monitor merged-commit CI, inspect the tree) and a genuine feedback loop with error-recovery discipline (verify base before retrying, diagnose a second identical failure); merging to main is destructive-adjacent but validation is present, and the closing gate 'Do not call work complete while required merged-commit workflows are still running' anchors the end state.

Progressive Disclosure

A single-purpose skill well under 50 lines with no bundle files; the one reference ('docs/development/quality-gates.md') is a clearly signaled, one-level-deep external pointer rather than inlined bulk, so per the simple-skill guideline well-organized sections score full marks.

Specificity

Lists four concrete actions ('run pre-push parity', 'monitor merged-commit CI', 'leave repositories clean') with only minor coverage gaps; it falls just short of anchor 5 because 'Land completed Fallow work' relies on project-internal jargon rather than fully self-contained concrete actions.

Completeness

Explicitly answers both what (land reviewed work, run parity, monitor CI, clean repos) and when (an explicit 'Use when...' clause with concrete trigger phrases 'ship, merge, or move approved work to main'), exactly matching the anchor-5 example structure.

Trigger Term Quality

'Use when asked to ship, merge, or move approved work to main' contains natural phrases a user would actually say, matching 'good keyword coverage; a few natural terms missing' — synonyms like 'publish', 'release', or 'land' are absent, keeping it below anchor 5.

Distinctiveness Conflict Risk

Scoping terms ('after review', 'approved work', the project-specific 'Fallow') carve out a clear niche, but 'ship/merge to main' has minor overlap risk with generic git-merge or release skills, matching 'mostly distinct; minor overlap risk'.