Conciseness

The 24-line body is lean and dense — every step carries operational rules at parameter level ("pass them as `focus`", "`isolate` with `context: \"ghost\"`", "cite the exact `imagePath` and `view`") with zero concept explanation. The only trimmable clause is "Load this skill, then" in step 1, which is a single trivial phrase rather than instances of over-explanation, so this fits the anchor-5 example better than anchor 4.

Actionability

Guidance is fully executable at the tool-call level: exact cad.look patterns (focus, zoom-if-too-wide, isolate, context:"ghost", hide), a concrete conditional trigger for cad.inspect ("object identity, bounding boxes, source, distance, clearance"), defined P0/P1 criteria, citation requirements, and an exact empty-case output. As an instruction-only skill with actionable guidance, absence of code is not penalized.

Workflow Clarity

A clear 8-step numbered sequence with explicit decision points and feedback ("use a numerical `zoom` only if the first focused view is still too wide"), evidence-validity checkpoints ("Cite an isolated or hidden view only for geometry that remains visible in that view"; "every finding still requires image evidence"), an explicit termination contract, and a fallback path ("No P0 or P1 findings."). The review is read-only, so the destructive/batch validation cap does not apply.

Progressive Disclosure

The skill is under 50 lines, single-purpose, and requires no external reference files (none exist in the bundle); the body is well organized (scope intro → numbered Workflow → fallback → scope boundary), which satisfies the simple-skill exception for a top score.

Specificity

The description lists multiple concrete actions — "Independently audit one complete committed CAD build using cad.look image evidence and cad.inspect geometry facts" and "returns prioritized P0/P1 issues as ordinary text" — naming the domain, both tools, the evidence classes, and the output format with no gaps in coverage.

Completeness

Both what and when are explicit: the what is "Independently audit one complete committed CAD build using cad.look image evidence and cad.inspect geometry facts", and the when is "Use only for the Host-owned CAD handoff review", reinforced by an explicit when-not ("do not use for CAD editing, finite-element analysis, physical load certification, or export").

Trigger Term Quality

Good keyword coverage: "CAD", "audit", "review", "handoff", "build", "P0/P1 issues" are terms a requester would naturally use. A few natural variations are missing (e.g., "design review", "check the model", common CAD file extensions), keeping it below comprehensive.

Distinctiveness Conflict Risk

"Use only for the Host-owned CAD handoff review" carves out a clear niche with distinct triggers, and the explicit exclusion list (editing, FEA, load certification, export) minimizes overlap with any related skill.