Conciseness

The body is dense and rule-driven with almost no tutorial filler — tables for data attributes, numbered non-negotiables, and compact code blocks earn their tokens. It sits at anchor 4 rather than 5 because of minor over-explanation that could be trimmed, e.g. the multi-sentence 'Why this matters' rationale under Layout Before Animation and some restatement between the Scene Transitions rules and their WRONG/RIGHT examples.

Actionability

Guidance is copy-paste executable throughout: complete HTML/JS snippets (sub-composition template, video/audio elements, entrance/exit tween blocks), exact commands ('npx hyperframes inspect --json', 'node skills/hyperframes/scripts/animation-map.mjs <composition-dir>'), and precise formulas such as 'repeat: Math.ceil(duration / cycleDuration) - 1'. This matches anchor 5; common cases are covered with specific examples.

Workflow Clarity

The Approach section sequences the work (What → Structure → Timing → Layout → Animate), the Output Checklist enumerates validation gates, and the Quality Checks section provides explicit feedback loops: 'Re-run hyperframes validate until clean' and 'Re-run after fixes'. Anchor 5 (clear sequence, explicit validation, feedback loops, checklists) matches directly.

Progressive Disclosure

The References section is well-signaled (each entry says what it covers and 'Read when...'), but scored against the actual bundle it breaks down: visual-styles.md, house-style.md, patterns.md, and data-in-motion.md are linked in the body and references but do not exist in the bundle (house-style.md is load-bearing — the HARD-GATE and animation defaults depend on it), and the transitions chain nests three levels deep (SKILL.md → references/transitions.md → transitions/catalog.md → per-type css files). Broken navigation plus 2+-level nesting places this between anchors 3 and 4, closer to 3 because the missing files cause real navigation failures rather than mere organization gaps.

Specificity

The description lists many concrete capabilities — 'Create video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions' — covering the domain comprehensively. Anchor 5 ('multiple specific concrete actions; comprehensive coverage') matches; it is not score 4 because there are no meaningful coverage gaps in the skill's scope.

Completeness

Both 'what' and 'when' are explicit: the opening sentence states what the skill does, and 'Use when asked to build any HTML-based video content, add captions... generate text-to-speech narration... or add transitions between scenes' gives concrete trigger phrases. This matches anchor 5; the 'when' clause is explicit and specific, not merely present as at anchor 4.

Trigger Term Quality

Natural user phrasings are comprehensively covered with synonyms: 'captions or subtitles synced to audio', 'text-to-speech narration', 'beat sync, glow, pulse driven by music', 'marker sweeps, hand-drawn circles, burst lines, scribble, sketchout', 'crossfades, wipes, reveals, shader transitions'. It clearly exceeds anchor 4 ('a few natural terms missing'); synonyms are present throughout.

Distinctiveness Conflict Risk

The niche is clear ('HTML-based video' with a named framework, HyperFrames HTML) and the closing sentence — 'For CLI commands (init, lint, preview, render, transcribe, tts) see the hyperframes-cli skill' — explicitly de-conflicts with the closest related skill. Minimal conflict risk; matches anchor 5.