Conciseness

The body is mostly lean, but the 'Why This Works' section explains framing/solutionism reasoning Claude already knows ('Most bad decisions don't fail at execution — they fail at framing') and philosophical asides like 'Founder-market fit is the strongest predictor of survival' add padding. This matches anchor 3 — efficient with some unnecessary explanation that could be trimmed — rather than anchor 4's 'minor instances'.

Actionability

Every question is given exact wording plus per-question evaluation criteria ('‘We’ll execute better’ is not a defense'), the output is a copy-paste-ready brief template with a GREEN/YELLOW/RED assessment scale, and routing rules are explicit. For an instruction-only skill this is fully executable guidance covering the common cases, matching anchor 5.

Workflow Clarity

The sequence is clear — trigger conditions, founder answers all six in writing before any C-role weighs in, brief produced, then gated routing — with an explicit validation gate (GREEN required before routing) and a feedback loop (YELLOW → 'sharpen Q[N] before proceeding'; RED → 'kill or redefine'). No destructive or batch operations, so the validation cap does not apply.

Progressive Disclosure

This is a self-contained single-file skill with no bundle files; nothing in the body clearly belongs in a separate file, and sections are well-organized and easy to navigate. Cross-references to sibling commands are clearly signaled in dedicated 'Related Commands' and 'Routing' sections, matching the simple-skill pattern where good organization alone earns a 5.

Specificity

Names the domain ('YC-style 6 question founder interrogation before any advice') and enumerates concrete coverage across 'problem, customer, distribution, defensibility, capital, and founder fit'. It is one action with six named facets rather than multiple discrete actions, matching anchor 4 rather than 5, and is clearly above the 1-2 concrete actions of anchor 3.

Completeness

It explicitly answers what ('YC-style 6 question founder interrogation before any advice. Forces clarity on problem, customer, distribution, defensibility, capital, and founder fit') and when ('Use when a founder question is too vague to route — e.g. ‘should we grow faster?’ — or before drafting a strategy brief') with a concrete trigger example, matching the anchor-5 example exactly.

Trigger Term Quality

'Use when a founder question is too vague to route — e.g. ‘should we grow faster?’ — or before drafting a strategy brief' provides natural phrases a user would actually say, including a verbatim example utterance. Coverage is good but misses common variations like 'office hours', 'startup advice', or 'pitch feedback', so it falls short of anchor 5.

Distinctiveness Conflict Risk

A clear niche (founder interrogation gate before strategy work) with distinct triggers that are unlikely to fire for unrelated skills. Minor overlap risk exists with the sibling '/c-level-agents:brief' command via the 'before drafting a strategy brief' trigger, placing it at anchor 4 rather than 5.