Conciseness

A ~48-line index that covers 33 skills, 37 tools, and 68 references with zero concept explanations — every line carries names, counts, commands, or paths, and it explicitly disclaims scope ("This is the bundle index, not an advisor"). Matches the lean, every-token-earns-its-place anchor.

Actionability

Concrete, executable detail throughout: commands ("/cs:setup", "~45 min", "/cs:update", "/cs:boardroom"), paths ("~/.claude/company-context.md", "~/.claude/decisions/{raw,approved}/"), and a role-to-domain mapping ("CFO (capital/burn), CRO (pipeline/sales)"). Not 5 because how to actually invoke each of the 14 role advisors is left unstated — only board-meeting's invocation is given.

Workflow Clarity

The board-meeting flow is explicitly sequenced with a hard checkpoint: "(1) context gathering → (2) independent contributions (isolated) → (3) critic analysis → (4) synthesis → (5) founder review (full stop) → (6) decision extraction", and onboarding has a cadence ("Refresh quarterly with /cs:update"). Not 5 because there are no error-recovery/feedback loops and the remaining workflows are delegated to other files rather than detailed here.

Progressive Disclosure

Good index structure: a "Start Here" section, grouped inventory, an inline routing quick reference with an explicit pointer to the full matrix ("Full matrix in ../chief-of-staff/SKILL.md and ../chief-of-staff/references/routing-matrix.md"), and one-level-deep references with a section anchor ("../agent-protocol/SKILL.md → 'Decision Memory (Canonical Layout)'"). Not 5 because the referenced sibling paths cannot be resolved from this skill's own bundle (no references/ or scripts/ directories ship with it) and the depth-varying relative paths (../, ../../, ../../../) make navigation fragile.

Specificity

Names the domain and several concrete functions ("Index and router", "deciding which advisor skill fits a question", "finding the entry points (cs-onboard interview, chief-of-staff routing, board-meeting protocol)"). Not 5 because the core actions "index" and "router" remain somewhat abstract with no concrete outputs or artifacts named; not 3 because more than 1-2 specific actions are given.

Completeness

Explicitly answers both: what ("Index and router for the C-level advisory bundle: 33 skills covering 14 C-suite roles, orchestration, cross-cutting capabilities, and culture") and when ("Use when exploring what the c-level-advisor bundle contains, deciding which advisor skill fits a question, or finding the entry points"), with concrete trigger phrases matching the anchor-5 pattern.

Trigger Term Quality

Includes natural domain terms users would say: "C-level advisory bundle", "C-suite roles", "advisor skill", plus concrete entry-point names (cs-onboard, chief-of-staff, board-meeting). Not 5 because common user phrasings like "executive", "CEO advice", or role-specific triggers are missing.

Distinctiveness Conflict Risk

Clear niche (the bundle's index/router) with distinct triggers, but "deciding which advisor skill fits a question" overlaps the routing function of the sibling chief-of-staff skill it points to — a minor overlap risk with a closely related skill, so not 5.