Conciseness

The body is lean and table-driven ('Drop filler. Keep sentence structure.'), with zero space given to concepts Claude already knows; every line carries non-derivable facts such as the mode list, triggers, and the config resolution order 'env var > config file > full'. Matches the anchor for lean and efficient content where every token earns its place.

Actionability

Concrete user commands ('/caveman lite', '/caveman-commit'), copy-paste config snippets ('export CAVEMAN_DEFAULT_MODE=ultra' and the JSON config example), and exact deactivation phrases ('stop caveman', 'normal mode') make the guidance mostly executable. It is not 5 because 'Display this reference card... Output in caveman style' leaves the exact output form (verbatim tables vs. reformatted card) implicit.

Workflow Clarity

This is a simple single-task skill, so the simple-skill exception applies: the single action is unambiguous — 'Display this reference card when invoked. One-shot — do NOT change mode, write flag files, or persist anything.' The explicit negative constraints remove ambiguity, and there are no destructive or batch operations, so the validation cap does not apply.

Progressive Disclosure

The bundle contains no references/, scripts/, or assets/ directories — this is a small single-file skill, and the under-50-lines exception applies: the content is organized into clear sections (Modes, Skills, Deactivate, Configure Default Mode, More) with a clearly signaled external docs link (https://github.com/JuliusBrussee/caveman).

Specificity

Names the domain ('Quick-reference card for all caveman modes, skills, and commands') and one concrete behavior ('One-shot display, not a persistent mode'), matching the anchor for domain plus 1-2 concrete actions that are not comprehensive. It is not 4 because no several specific actions are listed, and not 2 because the scope and display behavior go beyond minimal or generic.

Completeness

Both questions are answered explicitly: the 'what' is 'Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode', and the 'when' is an explicit 'Trigger:' clause with concrete phrases. This matches the anchor for clearly and explicitly answering both what and when with concrete trigger phrases, and the explicit trigger guidance means the missing-'Use when' cap does not apply.

Trigger Term Quality

Explicit triggers '/caveman-help', 'caveman help', 'what caveman commands', and 'how do I use caveman' are natural user phrasings with good coverage. It falls short of 5 because common variants like 'caveman modes', 'list caveman commands', or 'caveman options' are missing.

Distinctiveness Conflict Risk

The description carves a clear niche within the caveman skill family with distinct triggers ('caveman help', 'what caveman commands'). It is not 5 because 'how do I use caveman' could plausibly match the core /caveman mode skill rather than this help card — minor overlap risk with a closely related skill.