Conciseness

The body assumes Claude's competence throughout — no basic-concept explanations — and nearly every sentence carries a directive or a concrete fact (e.g., "measured: 5 short scenes ≈ 9 min inline vs ≈ 21 min packetized"). It is 4 not 5 because rhetorical framing in the companion section ("Arrive as the director, not the contractor.", "The ceiling belongs to the concept, not the toolbox.") and the very long §5 plan paragraph could be tightened without losing instruction.

Actionability

Copy-paste-ready commands with exact flags cover every stage: `npx hyperframes init "videos/<project>" --non-interactive --example=blank --skill=general-video`, `node <MEDIA_DIR>/scripts/prefs.mjs record --hyperframes <PROJECT_ROOT>`, `node <SKILL_DIR>/scripts/frame-packets.mjs --project ... --storyboard ...`, `npx hyperframes catalog --query "<the look, in plain English>" --json`, `npx hyperframes lint` / `check`. Placeholders are defined inline ("Here `<MEDIA_DIR>` is the installed `/media-use` skill directory..."). Full executability with common cases covered matches the 5 anchor.

Workflow Clarity

A clear state table routes entry (specific edit / brief exists / resume / fresh), then an explicitly ordered dependency chain (plan → review → resolve → build → merge → assemble → verify → final approval) with validation checkpoints and feedback loops: lint after the first HTML pass, `npx hyperframes check` as the final gate, and a §7 done-checklist requiring checks to pass and the rendered file to be verified. Explicit validation plus error-recovery gating matches the 5 anchor.

Progressive Disclosure

Structure is good: the body is an overview routing to clearly signaled, one-level-deep references (`../hyperframes/references/brief-contract.md`, `/hyperframes-creative` → `references/house-style.md`), and the referenced `scripts/frame-packets.mjs` exists in the bundle. It is not 5 because the §5 dispatch detail (packet contents, worker role assembly) is inlined rather than placed in a reference, and the referenced `sub-agents/frame-worker.md` is not present in the actual bundle, leaving a dangling path.

Specificity

"Author or edit a custom HyperFrames composition" names two concrete actions, and the enumerated artifact list ("brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds") gives specific coverage. It stays at 4 rather than 5 because the action verbs are limited to author/edit — it does not name further concrete operations (render, verify, assemble) the way the 5-anchor example lists four distinct actions.

Completeness

The what is explicit ("Author or edit a custom HyperFrames composition") and the when is explicit with concrete triggers ("when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces..."). Both are stated with trigger phrases, matching the 5-anchor; it cannot be lower since both halves are present and specific.

Trigger Term Quality

Natural production vocabulary is present — "sizzle reels", "montages", "static loops", "static title cards", "footage remixes", "multi-scene" — terms a user planning a video would plausibly say. It is not 5 because some common user phrasings (e.g., "promo video", "make me a video", "highlight reel") are absent, and the odd "freeform builds" is more internal jargon than a natural trigger.

Distinctiveness Conflict Risk

It actively disambiguates against sibling skills: "Use motion-graphics instead for a short unnarrated motion-first unit, including an animated title" and "Route fresh creation through hyperframes before using this skill." This is a clear niche with explicit conflict-avoidance guidance, exceeding the 4-anchor's 'minor overlap risk'.