hyperframes-core

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured technical contract that excels at progressive disclosure and provides concrete, actionable rules with a real validation checklist. The remaining gains are minor tightening of verbose passages and an inline minimal composition example for first-touch actionability.

Suggestions

Inline a minimal standalone composition HTML skeleton (a few lines) at the top of 'Building a composition' so the first executable example does not require opening references/minimal-composition.md.

Tighten the transport-rule and host-id-convention callouts into terse one-liners, moving the rationale into references/sub-compositions.md.

Convert the 'Building a composition' sections into a short numbered build sequence with an explicit 'lint → check → snapshot → preview → render' checkpoint chain so the workflow reads as a single gated path.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no primers on HTML/CSS/GSAP), with most tokens earning their place on non-obvious domain rules; a few explanatory passages such as the transport rule and host-id convention could be tightened.	4 / 5
Actionability	Gives concrete, executable fixes — `gsap.fromTo(el, { x: -40 }, { x: 0 })`, id every `<audio>`, prefix ids `#<id>-hero`, `position:absolute; inset:0` for fills — but defers a full runnable composition example to `references/minimal-composition.md` rather than including one inline.	4 / 5
Workflow Clarity	A clear sectioned build flow precedes an explicit Validation checklist with approval gating ('render only after the user approves') and feedback notes about lint errors masking audits; the build sequence is sectioned rather than a tightly numbered validate-gated list.	4 / 5
Progressive Disclosure	An overview body pairs with a 19-row reference table giving each file's 'Read it to…' purpose, references are one level deep, every inline section points to a specific file, and all referenced files verified present on disk.	5 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states the skill's purpose and when to use it, with comprehensive concrete capability coverage and a distinct niche. The only soft spot is that trigger terms are predominantly technical jargon rather than natural user phrasings.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — composition structure, `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, media playback, determinism rules, validation, Tailwind, STORYBOARD.md/SCRIPT.md — giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both 'what' (build one renderable project; the composition contract surface) and 'when' ('Use for…'; 'Read before writing composition HTML') with concrete trigger phrases, so it is not subject to the missing-trigger cap.	5 / 5
Trigger Term Quality	Good domain keyword coverage including file-format names (STORYBOARD.md, SCRIPT.md) and concrete concepts (tracks, sub-compositions, Tailwind), but the terms lean technical and omit a few natural lay-user phrasings.	4 / 5
Distinctiveness Conflict Risk	'The HyperFrames composition contract' names a clear niche with distinct, domain-specific triggers, and the scoped Tailwind/plan-format coverage stays inside that niche, minimizing conflict with sibling skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: heygen-com/hyperframes
Path: skills/hyperframes-core/SKILL.md
Commit: a562946

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.