Conciseness

The body is dense and prescriptive, assumes competence (never explains git, Drizzle, Effect, or SolidJS) and cites repo-specific files like 'cire/api/src/services/directory.ts', but the skeleton-preservation warning is repeated roughly four times (Step 0, the bold 'never rewritten' paragraph, the Step 2 shape check, and the final check) — emphatic prose that could be trimmed, matching the 4 anchor rather than the 5 anchor's every-token-earns-its-place.

Actionability

Guidance is fully executable throughout: a verbatim heredoc that writes the report skeleton, 'BASE=$(git config --get branch.$(git branch --show-current).gh-merge-base || echo main)', an exact grep routing table with concrete patterns, 'grep -c' shape-check commands, 'grep -rn \'<gateName>('\'', and a copy-paste finding template — matching the 5 anchor's copy-paste-ready coverage of common cases.

Workflow Clarity

Steps 0→1→2 are clearly sequenced, with an explicit mid-run validation checkpoint ('Check the shape once, as soon as the first finding is in the file'), a feedback loop for recovery ('If it prints less... restore the 4 headings, put the finding back under the right one, and edit from then on'), and a final two-count check — the 5 anchor's explicit validation with error-recovery loops, not merely the 4 anchor's 'most checkpoints'.

Progressive Disclosure

The single reference file 'references/checklists.md' exists, is one level deep, and is clearly signaled both by the routing table's '(references)' markers and a dedicated section explaining when to open it and why the split exists ('no scenario in this repository's eval suite exercises them'), with the core defect class kept inline — matching the 5 anchor's well-signaled, appropriately split structure.

Specificity

The description enumerates concrete defect classes ('redundant database round trips, N+1 queries, unbounded reads, per-request layer rebuilds, wasted client fetches, and build steps that ship a broken artefact') and specifies the output format ('P-C/W/I IDs in the four-field format'), giving comprehensive concrete actions with no coverage gaps — the 5 anchor, not 4.

Completeness

It opens with an explicit 'Use when reviewing a branch diff for performance defects' trigger clause and concretely states what it does (detect the named defect classes, report findings with tiered P-C/W/I IDs in a four-field format), clearly answering both what and when — matching the 5 anchor rather than 4, where the 'when' would be less explicit.

Trigger Term Quality

'reviewing a branch diff', 'performance defects', and 'N+1 queries' are phrases users would naturally say, giving good keyword coverage, but common synonyms such as 'slow', 'latency', 'perf', or 'optimize' are missing — above the 3 anchor's partial coverage, short of the 5 anchor's synonym completeness.

Distinctiveness Conflict Risk

The performance-review niche with tiered P-C/W/I findings is mostly distinct, but the trigger 'reviewing a branch diff' overlaps with general code-review and PR-review skills, so it is minor overlap risk (4) rather than the 5 anchor's minimal conflict risk.