Conciseness

The body is dense and prescriptive throughout, assuming Claude's competence (no explanations of what timelines, captions, or video editing are), but the opening 'Plugin installs' paragraph is wasted tokens: it refers to 'setup or freshness commands' and 'the update instructions below', neither of which exists in this file.

Actionability

Guidance is fully executable for an instruction-only skill: exact attributes ('data-composition-src', 'data-track-kind="captions"', per-kind 'data-track-index'), a kind-to-attribute table, concrete safe-box percentages (90%/5%, 80%/10%) traced to named source constants, and the copy-paste command 'Run hyperframes check'. Not 4 — there are no missing key details; the verification target is enumerated to the row ('a base row, one row per scene host, one caption row and the audio rows').

Workflow Clarity

Sequences are clear and tabular (message-triage table in § 0, the five-step Brief→Notes build-order table in § 5), and validation is explicit with a fix loop and checklist: 'Run hyperframes check (it runs lint) and fix every finding. Then open the project in Studio and check that the timeline shows a base row, one row per scene host, one caption row and the audio rows.' Protective checkpoints ('never overwrite locked frames', 'never overwrite BRIEF.md or STORYBOARD.md') are embedded in the steps themselves.

Progressive Disclosure

References are one level deep and clearly signaled with full skill paths ('/hyperframes-core references/creator-editing-recipes.md', '/hyperframes references/pitch-round.md', '/hyperframes-creative references/storyboard-recipe.md'), and content is appropriately split ('Each step has an owner; follow it and do not restate it here'). Not 5 because the pre-heading 'Plugin installs' paragraph dangles — its 'update instructions below' target does not exist in this file — a minor navigation gap.

Specificity

Multiple concrete capabilities with specific detail: 'the plan, storyboard and build order that the HyperFrames launch films follow', '(one caption track, one element kind per track, every scene a sub-composition)', '(safe zones)', and named exclusions '(split, trim, retime, volume, copy, swap)'. Not 4 — coverage spans conversation handling, new-film planning, timeline layout, and safe zones with no meaningful gaps.

Completeness

Explicitly answers both parts: 'Use when working with a person on a HyperFrames project in Studio' (when) plus an enumerated what (message triage, launch-film plan/storyboard/build order, timeline layout, safe zones) and an explicit 'Don't use for how to perform an individual edit' exclusion. Both what and when are explicit with concrete trigger phrases.

Trigger Term Quality

Good natural-term coverage — 'HyperFrames project', 'Studio', 'new film', 'timeline', 'captions', 'storyboard', 'plan', 'build' — including negative triggers for edits. Not 5 because common synonyms a user might say ('video', 'subtitles', 'composition') are absent.

Distinctiveness Conflict Risk

Clear niche (Studio project and timeline conventions) with explicit de-confliction against the closest sibling: 'Don't use for how to perform an individual edit (split, trim, retime, volume, copy, swap): that is creator-editing-recipes.md in /hyperframes-core.' Minimal conflict risk.