video-hyperframes

Hyperframes / Remotion-compatible continuous frame animation with autoplay support.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/video-hyperframes/SKILL.md

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 tight, token-efficient template spec that gives precise structural and visual constraints for the output. Its main weakness is that the two machine-critical elements — the autoplay JavaScript and the HYPERFRAMES_META JSON format — are named but never shown, leaving the executable core underspecified.

Suggestions

Include the actual autoplay JavaScript snippet (3s interval switch, click/arrow-key handlers, progress bar) rather than describing it in one line.

Show a minimal example of the `` JSON structure (one frame's duration/transition/sceneSummary) so downstream Remotion conversion is deterministic.

Give a concrete default frame count heuristic (e.g., "6-8 frames for a short script, +2 per major argument") instead of leaving N to inferred information density.

Dimension	Reasoning	Score
Conciseness	Nine dense bullets, ~40 lines total, with zero padding — no explanation of what Remotion is, what autoplay means, or any concept Claude already knows. Phrases like "字号巨大 (text-9xl), 一句话即可, 不要堆砌" and the concrete marker syntax earn every token. This matches 'Lean and efficient; assumes Claude's competence; every token earns its place'.	5 / 5
Actionability	Many concrete specifics are given (w-[1920px] h-[1080px] frames, `<!-- frame:N duration:3000 transition:fade -->`, text-9xl, single neon accent), but two key pieces are named without being provided: the autoplay JavaScript is only referenced ("顶部加一段 JavaScript 自动播放") with no snippet, and the `HYPERFRAMES_META` JSON has no example shape. This matches 'Some concrete guidance but incomplete; missing key details'. Not 4 because the single most fragile component (the player script) must be invented from scratch.	3 / 5
Workflow Clarity	As a simple single-task template spec under 50 lines, it defines the output unambiguously: frame sizing, narrative order (hook → arguments → conclusion + CTA), interaction model, and a final metadata comment. Not 5 because frame count is left to judgment ("N 由信息密度决定") with only loose bounds, and no assembly/verification order is given; not 3 because every structural requirement needed to produce the artifact is stated.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no external references needed, and the body is a well-organized flat checklist under a single title — per the rubric's simple-skill guidance this earns 5. There are no nested references and nothing that belongs in a separate file is inlined.	5 / 5
	Total	17 / 20 Passed

Description

48%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.

The description names a concrete, niche output format but is a verb-less artifact label rather than a capability statement, and it entirely lacks any 'when to use' trigger guidance. Users searching for 'video' or 'mp4' generation would not naturally surface it. It is distinctive but incomplete.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to turn content into a Remotion/Hyperframes video or asks for an autoplaying frame-based animation or mp4 script."

Add action verbs and enumerate capabilities, e.g. "Generates N continuous 1920×1080 HTML frames with autoplay, click/keyboard controls, a progress bar, and Remotion-ready frame metadata."

Include natural user-facing synonyms (video, animation script, mp4, slideshow) so the description matches how users actually phrase the request.

Dimension	Reasoning	Score
Specificity	The description "Hyperframes / Remotion-compatible continuous frame animation with autoplay support" names the domain but contains no action verbs at all — it is a noun phrase describing the output artifact, matching the anchor 'Names the domain but actions are minimal or generic'. Not 1 because the domain and output format are concretely named; not 3 because there is not even one explicitly stated action (e.g., 'Generates' or 'Creates').	2 / 5
Completeness	The 'what' is reasonably clear (produces a Remotion-compatible continuous-frame animation artifact), but there is no 'when' clause — no "Use when..." or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is concrete rather than vague; not 4 because 'when' is entirely absent, not just weakly specified.	3 / 5
Trigger Term Quality	It includes relevant keywords like "Hyperframes", "Remotion-compatible", "frame animation", and "autoplay", but misses the natural terms a user would most plausibly say — "video", "mp4", "slideshow", or "animation script". This fits 'Some relevant keywords but missing common variations or synonyms'. Not 4 because the most common user-facing term (video) is absent from the description itself.	3 / 5
Distinctiveness Conflict Risk	Naming the specific tools "Hyperframes / Remotion-compatible" carves out a clear niche that most other skills would not claim — 'Mostly distinct; minor overlap risk with closely related skills'. Not 5 because it could still overlap with sibling video/animation-template skills in the same category, and no trigger phrase pins it down further.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/video-hyperframes/SKILL.md
Commit: 1b47e60

Reviewed: 3 days 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.