Conciseness

The body is operational and repo-specific rather than explanatory, but the skeleton/shape discipline is explained four separate times (Step 0's two long paragraphs, the Step 2 mid-run check, "Report shape", and the final check), with rhetorical padding ("a run that leaves a differently-shaped file has produced nothing, however good the analysis inside it") and a factual slip ("Eight more sections" introduces a list of ten). This fits the mostly-efficient-but-could-be-tightened anchor at 3 rather than the minor-trimmable-instances anchor at 4, and is well above the noticeably-verbose anchor at 2.

Actionability

Guidance is fully executable: a verbatim heredoc that writes the report skeleton, exact base-branch resolution and diff-routing commands, a grep routing table mapping patterns to mandatory sections, a `grep -c` shape check, a copy-paste finding template, and a named in-repo fix idiom (`cire/api/src/services/directory.ts` and its `inWedding` column) to copy rather than invent.

Workflow Clarity

The sequence (write skeleton → route the diff → work mandatory sections → assemble the report) is explicit, with validation checkpoints at three points (mid-run `grep -c` after the first finding, a final two-count check, and the recovery loop "restore the 4 headings, put the finding back under the right one, and edit from then on") and per-bullet verdict recording to catch skimming. This matches the clear-sequence-with-explicit-validation-and-error-recovery anchor.

Progressive Disclosure

Ten checklist sections are routed to a single one-level-deep reference (`references/checklists.md`, verified to exist with matching headings) and clearly signaled ("open the file whenever Step 1 routes to one of them"), with the highest-frequency section kept inline. It falls short of the 5 anchor on minor organization gaps: the miscounted "Eight more sections" heading, no markdown link to the reference file, and the very long two-gate bullet under Shared middleware that could itself live in the reference.

Specificity

The description enumerates the concrete defect classes it handles ("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 exact output convention ("P-C/W/I IDs in the four-field format"), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

Completeness

It opens with an explicit trigger clause ("Use when reviewing a branch diff for performance defects") and pairs it with a concrete what (the named defect classes plus "reporting findings with P-C/W/I IDs in the four-field format"), clearly and explicitly answering both what and when with concrete triggers.

Trigger Term Quality

Natural trigger phrases like "performance defects", "branch diff", "N+1 queries" and "database round trips" are present, but common synonyms a user might say ("slow queries", "latency", "perf") are missing, which fits the good-coverage-with-a-few-gaps anchor rather than the comprehensive-synonyms anchor at 5.

Distinctiveness Conflict Risk

The performance-only scope and named defect classes give it a clear niche, but the trigger phrase "reviewing a branch diff" overlaps with general code-review skills that would also fire on a plain review request, placing it at mostly-distinct with minor overlap risk rather than minimal conflict risk at 5.