Conciseness

The body is lean and format-driven — a routing table instead of prose, terse decision guidance ("Pick 2-4 rules from rules-index.md, glue them together with a single paused GSAP timeline, done"), and no explanation of concepts Claude already knows. It misses level 5 because the Critical Constraints section restates a substantial chunk of hyperframes-core's contract ("single paused timeline, data-duration governs length, no Math.random / Date.now / performance.now, no repeat: -1, no page-load gsap.set...") immediately after saying "Don't restate the full contract here" — that parenthetical could be trimmed to a pointer.

Actionability

Mostly executable guidance: a concrete script invocation ("node skills/hyperframes-animation/scripts/animation-map.mjs <composition-dir> --out <composition-dir>/.hyperframes/anim-map") with its output contract, and a routing table mapping each need to a specific file. It falls short of level 5 because the default path ("compose atomic rules") never shows even a minimal timeline-composition snippet, so the primary workflow relies on referenced files rather than copy-paste-ready guidance here.

Workflow Clarity

The decision flow is clear and ordered: default is composing rules, explicit conditions for when to load a blueprint ("The scene matches an existing pre-designed multi-phase template... or You want runnable ground-truth code for a complex 4-5 phase choreography"), runtime selection guidance, and a post-authoring validation step ("Use it to audit choreography (dead zones, stagger consistency, lifecycle warnings) after authoring") via the animation-map script. It is not level 5 because there is no explicit feedback loop (audit → fix → re-audit) and no validation step before the audit for the authoring workflow itself.

Progressive Disclosure

Excellent structure: a routing table covering every need with well-signaled, one-level-deep references, explicit non-speculative reading guidance ("Do not read it speculatively"), and pointers to sibling skills in See Also. It falls short of level 5 because the routing table references many paths (rules-index.md, rules/<name>.md, blueprints-index.md, blueprints/<id>.md, transitions/overview.md, transitions/catalog.md, techniques.md, adapters/*.md) that are not present in the shipped bundle — only references/motion-blur.md and scripts/ exist — so navigation is broken for most routes as bundled.

Specificity

The description lists multiple concrete actions with comprehensive coverage: "pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer)", plus "auditing an existing composition's choreography (animation map)" and "24 named text-animation effects". It matches the level-5 anchor (multiple specific concrete actions, comprehensive); it is not level 4 because there are no meaningful coverage gaps — even runtime-specific lookups and the audit use case are named.

Completeness

Both what and when are explicit: what — "atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters"; when — "Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API". This mirrors the level-5 anchor exactly; level 4 would require the 'when' to be less explicit, but here the trigger clause enumerates concrete usage modes. Voice is imperative/third-person, matching the good examples — no person-penalty applies.

Trigger Term Quality

Natural trigger terms a user would actually say are comprehensively covered: "motion or animation task", "animation", "scene transitions", "motion-design", "choreography", "text-animation", plus all seven runtime names (GSAP, Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU) with concrete API examples ("GSAP eases / Lottie player / Three.js mixer"). It matches the level-5 anchor; no common synonyms for this domain are missing.

Distinctiveness Conflict Risk

It occupies a clear niche ("All animation knowledge for HyperFrames", "HyperFrames-native: single paused timeline, seek-safe, deterministic") with distinct triggers (motion/animation/runtime-specific APIs) that would not collide with sibling skills like hyperframes-core, -creative, or -cli, which cover non-animation concerns. It matches the level-5 anchor (clear niche, minimal conflict risk); it is not level 4 because the HyperFrames scoping plus runtime-specific API examples leave virtually no overlap ambiguity.