Conciseness

The body is dense, rule-driven, and free of teaching Claude things it already knows — tables of data attributes, exact GSAP/CSS snippets, and CLI invocations with flags dominate. It misses 5 because of minor padding: the daemon-dispatch rationale is stated twice (scaffold step 4's sandbox-exec explanation, then again "Reserve the daemon dispatch for render/inspect/preview... Do not run HyperFrames render yourself" a few paragraphs later), and the "OpenDesign integration" section re-explains the cache-slot rationale twice. It is above 3 because there is no concept-splaining filler, only operational content with a few redundant passages.

Actionability

Guidance is fully executable: a copy-paste-ready bash scaffold + daemon dispatch + wait-loop (with exit-code semantics 0/2/5), exact GSAP tween code with eases and positions, concrete CSS for scene layout, and CLI commands with specific flags ("--samples 15", "--at 1.5,4,7.25", "--no-contrast") plus fix hints for each failure mode. This matches the anchor of copy-paste-ready commands covering the common cases; the only placeholders ("<descriptive-name>.mp4") are deliberately user-supplied.

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints and feedback loops: the 5-step Approach, the scaffold → edit → dispatch → wait render flow, an Output Checklist ("lint and validate both pass", "inspect passes, or every reported overflow is intentionally marked"), and explicit retry loops ("Re-run hyperframes validate until clean", "Re-run after fixes"). This matches the anchor-5 example's validate → fix → re-validate pattern; not 4 because checkpoints are explicit rather than implicit at every fragile step.

Progressive Disclosure

The References section is well-signaled (each entry has a "Read when..." activation condition and stays one level deep), but scoring against the actual bundle reveals broken navigation: `visual-styles.md`, `house-style.md`, `patterns.md`, and `data-in-motion.md` are referenced from the body yet absent from the bundle — two of them load-bearing (the HARD-GATE step 3 requires visual-styles.md; house-style.md is the mandated fallback when no style is specified). Additionally the animation-map command points at `design-templates/hyperframes/scripts/animation-map.mjs` while the actual script is `scripts/animation-map.mjs`. Structure and signaling are good (above anchor 2's inlined-content problem), but "references mostly clear and working" (anchor 4) is not met when four referenced files are missing and a script path is wrong.

Specificity

The description lists many concrete actions ("video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions") and goes further with concrete sub-features ("marker sweeps, hand-drawn circles, burst lines, scribble, sketchout"; "crossfades, wipes, reveals, shader transitions"), matching the comprehensive-coverage anchor. It is not score 4 territory because coverage of the domain's capabilities has no noticeable gaps, and not below because every clause names a specific capability rather than generic language.

Completeness

Both questions are explicitly answered: the "what" opens the description ("Create video compositions, animations, title cards, overlays, captions, voiceovers...") and the "when" is an explicit "Use when asked to build any HTML-based video content, add captions or subtitles synced to audio, generate text-to-speech narration..." with concrete trigger phrases. This is the anchor-5 pattern; it is not 4 because the when-clause is already fully explicit and specific.

Trigger Term Quality

Natural trigger phrases are well covered ("HTML-based video content", "captions or subtitles synced to audio", "generate text-to-speech narration", "beat sync", "add transitions between scenes"), matching the good-coverage anchor. It falls short of 5 because no file extensions or format synonyms appear (.mp4, .html, "render a video", "kinetic type") alongside otherwise strong keyword coverage, and it is clearly above 3 since multiple common variations users would actually say are present.

Distinctiveness Conflict Risk

It carves a clear niche ("in HyperFrames HTML", "HTML-based video content") and even disambiguates the sibling skill ("For CLI commands (init, lint, preview, render, transcribe, tts) see the hyperframes-cli skill"), giving minimal conflict risk with adjacent video/CLI skills. It is not 4 because the boundary to the nearest overlapping skill is drawn explicitly rather than left as minor overlap risk.