motion-graphics

A short, design-led motion graphic where motion is the message — kinetic typography, stat count-up, chart/data-viz hit, logo sting / brand lockup, lower-third / callout / social overlay, animated map (highlight regions, connect places, zoom to a location), animated tweet / news-article / headline, webpage / UI animation (scroll, cursor, callouts), or fusing a real image's geometry into a chart. Usually under 10s (up to ~30s), no narration or live-action subject; renders to MP4 or transparent overlay. Longer / narrated / multi-scene → /general-video. Unclear → /hyperframes.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/motion-graphics/SKILL.md

Quality

Content

77%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 tightly written, highly actionable dispatch-entry skill with an excellent sequenced workflow, explicit validation gates, repair feedback loops, and a resume table. Its chief weakness is progressive disclosure: the body signals many reference files that are absent from the provided bundle, so most navigated paths do not resolve.

Suggestions

Ship the referenced bundle files (agents/director.md, agents/builder.md, agents/finalize.md, phases/source/guide.md, catalog-map.md, categories/<id>/module.md, references/preview-render.md, references/intent-interview.md) alongside SKILL.md so the signaled navigation actually resolves.

If some paths are intentionally external to this skill (e.g. under SKILL_DIR or ../hyperframes-core), mark them as such (e.g. '<SKILL_DIR>/agents/director.md') so a reader knows they live outside the local bundle rather than appearing missing.

Replace the '<proof-times>' placeholder with a concrete default example (e.g. '--at 0,1.5,end') so the verify step is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Dense and information-rich, assuming Claude's competence (it delegates detail to subagent docs rather than re-explaining); minor trimmable content in the category tables and the maintainer-only 'Design notes' section, which is appropriately flagged as not read during execution.	4 / 5
Actionability	Provides concrete, mostly copy-paste-ready bash ('npx hyperframes init ... --skill=motion-graphics', 'npx hyperframes lint .', 'npx hyperframes render ... -o ./renders/video.mp4') and explicit subagent dispatch prompts; minor gaps like the '<proof-times>' placeholder and the 'illustrative — see phases/source/guide.md' source command keep it just below fully executable.	4 / 5
Workflow Clarity	A clear sequenced flow (Step 0 init → plan → source → design → build → verify → approve → render) with explicit validation gates ('lint', 'check', 'snapshot'), a repair feedback loop ('dispatch the repair subagent ... then rerun the failed gate'), and a resume table mapping state to the correct re-entry point.	5 / 5
Progressive Disclosure	The body is well-structured as a dispatch entry with clearly signaled one-level-deep references (agents/director.md, phases/source/guide.md, categories/<id>/module.md, references/*), but most referenced paths do not exist in the shipped bundle — only references/builder-contract.md, references/motion-vocabulary.md, and references/shot-plan-ir.md are present — so navigation largely leads to missing files.	3 / 5
	Total	16 / 20 Passed

Description

75%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 rich, concrete description that clearly scopes a distinct niche (short unnarrated motion graphics) with extensive action coverage and explicit boundary routing. Its main weakness is the absence of an explicit positive 'Use when...' trigger clause, which holds completeness at the cap of 3.

Suggestions

Add an explicit 'Use when ...' clause naming the natural trigger phrases (e.g. 'Use when the user wants a short kinetic-text, stat count-up, logo sting, lower-third, animated map, or animated tweet/news graphic') so the positive trigger is stated, not just implied by routing.

Surface a few more lay synonyms users say ('motion graphics', 'animated text', 'count-up animation', 'lower third') alongside the technical category names to broaden natural-term coverage.

Keep the boundary routing line — it is effective — but pair it with the positive trigger so 'when' is as explicit as 'what'.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'kinetic typography, stat count-up, chart/data-viz hit, logo sting / brand lockup, lower-third / callout / social overlay, animated map ... animated tweet / news-article / headline, webpage / UI animation ... fusing a real image's geometry into a chart' — plus concrete constraints ('under 10s', 'renders to MP4 or transparent overlay'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	The 'what' is clear and detailed, but the 'when' appears only as boundary routing ('Longer / narrated / multi-scene → /general-video. Unclear → /hyperframes') with no explicit 'Use when...' clause; per the rubric guideline this caps completeness at 3.	3 / 5
Trigger Term Quality	Strong natural terms users would say ('motion graphic', 'logo sting', 'lower-third', 'animated map', 'count-up') with format synonyms (MP4/webm overlay), but trigger guidance is routing-based rather than a positive 'use when X' clause, leaving a few natural entry phrases implied.	4 / 5
Distinctiveness Conflict Risk	A clear niche — short, unnarrated, design-led motion graphics — with explicit boundary routing to /general-video and /hyperframes that minimizes conflict with adjacent skills.	5 / 5
	Total	17 / 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
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: heygen-com/hyperframes
Path: skills/motion-graphics/SKILL.md
Commit: 0f8eb89

Reviewed: 6 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.