Conciseness

The body is dense with specifics and assumes competence (no explanation of what CI or a squash merge is), but has minor trims available: step 5 states the head-moved recovery twice ("If it doesn't, someone pushed: redo steps 2-4" and "If the head moved, someone pushed. Redo steps 2-4"), and step 3's lane-recovery explanation runs long. Fits anchor 4 ('Efficient; minor instances of over-explanation that could be trimmed'), not 5's every-token-earns-its-place.

Actionability

Every step carries copy-paste-ready commands: `gh pr list --head ... --json number,url,author`, `pnpm prep:urgent`, `corepack pnpm ship:push -m ...`, `gh pr merge <number> --squash --admin --match-head-commit <head-oid>`, plus post-merge `gh run list --commit ... --json ...`. The only placeholder is the commit subject, which is inherently task-specific. Matches 'Fully executable; copy-paste ready code or commands'.

Workflow Clarity

The six steps are clearly sequenced with explicit validation checkpoints and feedback loops around a risky admin merge: re-reading the live PR (open, base main, ownership), matching `headRefOid` to `git rev-parse HEAD`, `--match-head-commit` on the merge, redo-steps-2-4 recovery when the head moved, confirming the merge commit in `origin/main`, and post-merge monitoring that treats failed/empty queries as 'unknown, not green'. The destructive-operation cap at 3 does not apply because validation is thorough.

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), and none are needed: the body is a single cohesive ~87-line procedure with clear sections (## Steps, ## After the merge) and no content that belongs in a separate file. References to sibling skills (`ship`, `babysit-pr`, `/new-branch`, `ship-and-monitor`) are one-level and clearly named, matching anchor 5's easy navigation.

Specificity

The description lists multiple concrete actions with an exact command: "local `pnpm prep:urgent`, push, and an immediate admin merge without waiting for remote CI or the 10-minute gate". Coverage is comprehensive for the skill's scope, matching the anchor 'Lists multiple specific concrete actions; comprehensive coverage'. Not 4 because no meaningful action in the workflow is left unnamed.

Completeness

Both halves are explicit: what — "Fast-path the current branch to main... push, and an immediate admin merge"; when — "Use only when the user explicitly asks to merge immediately". This matches the anchor 'Clearly and explicitly answers both what AND when with concrete trigger phrases'; the 'Use when' cap at 3 does not apply.

Trigger Term Quality

Natural phrasing is present ("merge immediately", "fast-path", "urgent"), so a user asking to merge now would plausibly match. A few natural synonyms are missing (e.g. 'merge now', 'ship it now'), which fits anchor 4 ('Good keyword coverage; a few natural terms missing') rather than 5's comprehensive synonym coverage.

Distinctiveness Conflict Risk

"Use only when the user explicitly asks to merge immediately" gives the skill a clear niche and a distinct trigger that separates it from the ordinary `ship` flow, so minimal conflict risk. It is above anchor 4 because the exclusivity clause resolves the one adjacent-skill overlap rather than leaving it as a risk.