Conciseness

The body is mostly efficient with well-organized sections, but includes unnecessary explanations of concepts Claude already knows: 'ratio above 1.0 indicates bearish bias; below 1.0 indicates bullish', the max pain definition ('the strike price at which the most options expire worthless'), 'vol compression (potential breakout ahead) or vol expansion (uncertainty increasing)', and a prerequisites list of options terminology. That is more than the 'minor instances' of the level-4 anchor but not the padded verbosity of level 2, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.

Actionability

Concrete guidance exists — example commands like 'python options_flow.py btc --summary' and 'python options_flow.py eth --iv-curve --format json', a specific credentials path, and '--min-notional 1000000 --period 24h' flags — but it is incomplete: the referenced 'options_flow.py' script and 'config/crypto-apis.env' are absent from the bundle (no scripts/ or config/ directories), step 2's 'Run Bash(crypto:options-*)' is a permission pattern rather than a command, and steps 3-9 ('Calculate the aggregate put/call ratio', 'Track max pain levels') are prose directions with no executable code or formulas. This matches 'some concrete guidance but incomplete; missing key details'.

Workflow Clarity

The 10 Instructions steps form a clear, logical sequence (authenticate, pull the chain, build OI heatmap, compute put/call, filter block trades, analyze IV term structure, track max pain, compare baselines, report, export), and the Error Handling table maps concrete failure modes ('API Rate Limit Exceeded', 'WebSocket connection dropped') to recovery actions, functioning as recovery checkpoints for a read-only, non-destructive workflow. Not level 5 because proactive validation checkpoints (verify authentication before pulling, validate data completeness before computing statistics) are implicit rather than explicit.

Progressive Disclosure

Scored against the actual bundle: only references/implementation.md is linked from the body ('See references/implementation.md for the full implementation workflow'), while the bundle's references/errors.md and references/examples.md are never referenced anywhere — buried and undiscoverable — even though the body inlines its own Error Handling table and Examples section that duplicate their content. Section structure within the body is good and the one reference is clearly signaled, so this fits 'some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline' rather than the minimal-structure level-2 anchor.

Specificity

The description names its domain clearly ('crypto options flow') and 1-2 concrete actions ('Track crypto options flow to identify institutional positioning and market sentiment'), but coverage is not comprehensive — the body's actual capabilities (put/call ratios, block trade detection, IV term structure, max pain) are absent. It sits at the 'Names domain and 1-2 concrete actions, but not comprehensive' anchor, not the level-4 anchor which expects 'several specific actions' listed.

Completeness

It clearly answers 'what' ('Track crypto options flow to identify institutional positioning and market sentiment') and 'when' both via an explicit 'Use when tracking institutional options flow' clause and concrete trigger phrases ('Trigger with phrases like "track options flow", "analyze derivatives", or "check institutional"'), matching the level-5 anchor of explicit what AND when with concrete trigger phrases. Voice is third-person imperative with no first/second person, so no penalty applies.

Trigger Term Quality

Explicit trigger phrases — 'track options flow', 'analyze derivatives', 'check institutional' — are natural things a user would say, giving good keyword coverage. Not level 5 because common variations and synonyms are missing ('crypto options', 'options sentiment', 'put/call ratio', 'block trades'), and 'check institutional' is awkward as a standalone phrase; not level 3 because multiple natural phrases are present rather than just 'some relevant keywords'.

Distinctiveness Conflict Risk

The crypto options flow / institutional positioning niche is clear with distinct triggers, giving minimal conflict risk with unrelated skills. It is not level 5 because 'analyze derivatives' is broad enough to also match general derivatives or non-crypto options analysis skills — a minor overlap with closely related skills, exactly the level-4 anchor.