Conciseness

The body is lean and table-driven — routing matrix, complexity scoring, and templates carry almost no padding, and it assumes Claude's competence throughout. Not 5: the 'Keywords' section duplicates trigger terms that belong in the description, and the 33-skill enumeration in 'Ecosystem Awareness' is partly filler.

Actionability

Concrete throughout for an instruction-only skill: exact invocation syntax with worked examples ('[INVOKE:cfo|What's the right runway target...]'), +1 complexity criteria, board-meeting and synthesis output templates, and explicit decision-log file paths. Not 5: minor gaps remain, e.g. 'Load company context via context-engine skill' offers no fallback if that skill is unavailable.

Workflow Clarity

The 5-step Session Protocol is clearly sequenced, gated by complexity scoring, with loop-prevention rules including an explicit deadlock fallback and a pre-delivery Quality Standards checklist as a validation checkpoint. Not 5: there is no re-validation or feedback loop after synthesis/board meetings, only the upfront checklist.

Progressive Disclosure

Both referenced files (references/routing-matrix.md and references/synthesis-framework.md) exist in the bundle, are clearly signaled at point of use ('Full rules in...', 'Full framework in...'), are one level deep, and are summarized inline with details pushed out, plus a closing References section. This matches the 5 anchor verified against the actual bundle structure.

Specificity

The description lists five concrete actions with objects — 'Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions' plus 'Loads company context automatically' — giving comprehensive coverage of the skill's job. Not 4: the anchor for 4 requires 'minor gaps in coverage', and no capability area is missing.

Completeness

Explicitly answers both 'what' (routes, triggers board meetings, synthesizes, tracks decisions, loads context) and 'when' ('Use when a founder question needs routing to the right advisor — e.g. 'should we raise now or cut burn?' — or when a multi-domain decision needs a board meeting convened') with a concrete trigger example. This matches the 5 anchor exactly.

Trigger Term Quality

Includes natural phrases a founder would actually say — 'founder question', 'board meeting', and the verbatim example 'should we raise now or cut burn?'. Not 5: common synonyms like 'executive advice' or 'ask the board' are missing; well above 3, which only expects 'some relevant keywords'.

Distinctiveness Conflict Risk

A clear niche as the C-suite routing/orchestration entry point with distinct triggers ('Every C-suite interaction starts here'), but that gateway claim creates minor overlap risk with the sibling role and orchestration skills it routes to. Mostly distinct, matching the 4 anchor.