Conciseness

The body is dense and almost entirely repo-specific (no explanations of concepts Claude already knows), but at ~630 lines it could be tightened: the six-heading report shape is enforced in three separate places (Step 0, the bold-label rule, "Report shape" plus the closing grep check), "reports and changes nothing" is restated in Step 5 and the break-ui section, and rhetorical passages ("A number nobody measured... is the one fault this lens must not commit") pad beyond instruction. This fits the mostly-efficient-could-be-tightened anchor rather than the minor-trims anchor.

Actionability

Fully executable throughout: a verbatim heredoc report skeleton, exact base-branch resolution commands, per-section grep patterns, a three-step component-lookup procedure with literal git grep invocations, a complete runnable bun -e contrast script including the alpha-flattening helper, and exact finding templates with tier rules — copy-paste ready and covering the common cases.

Workflow Clarity

Steps 0–5 are clearly sequenced with explicit validation checkpoints (the closing grep -c shape check where "Both must print 6"), error-recovery paths ("When a step cannot run", the unmeasured protocol, resume-from-report-file behaviour), and per-step ordering rules (record each finding the moment you have it). The skill is explicitly read-only, so the destructive-operation cap does not apply.

Progressive Disclosure

No bundle files exist, and all external material — DESIGN.md sections, wiki pages, sibling skills' SKILL.md/STANDARDS.md — is referenced one level deep with explicit paths and section names, clearly signalled. It stops short of 5 because the 630-line single file inlines substantial always-referenced material (the hand-drawn-element table, the per-section patterns) that could be split out, leaving the overview role less lean than the clear-overview anchor.

Specificity

The description enumerates multiple concrete actions — "Lists every element the diff draws by hand and the component that already draws it", "checks tokens, shape and colour and contrast, focus, motion, type and copy, layout and the tests that hold a look", "measures every contrast or geometry claim", "reports U-C/H/M/L findings in the four-field format" — with comprehensive coverage of the skill's behaviour, matching the anchor for multiple specific concrete actions rather than the minor-gaps anchor below it.

Completeness

It explicitly answers both questions: the trigger clause "Use when reviewing how a branch changes the look of a screen, or sweeping one surface with --full" gives a concrete, specific when (including the --full variant), and the enumerated action list gives a clear what. This matches the anchor requiring both, with concrete trigger phrases, rather than the 4 anchor where the when could be more specific.

Trigger Term Quality

Good keyword coverage: "reviewing how a branch changes the look of a screen", "DESIGN.md", "component", "tokens", "contrast", "layout" are natural phrasings. It stops short of the 5 anchor because common synonyms a user would say — "design review", "design system", "UI", "visual" — are absent, and "design" appears only inside the filename DESIGN.md.

Distinctiveness Conflict Risk

The niche is tightly pinned to look/design review of branch diffs against named governing documents (DESIGN.md, wiki page) and named packages (@shared/ui, @cire/ui, @osn/auth-ui), with distinct triggers and minimal overlap risk against neighbouring review lenses (security, performance), matching the clear-niche anchor.