render-hypermotion

Assemble the FREE steps of the product-hypermotion + kinetic-typography video format — dice ONE Seedance 2.0 hypermotion clip into 5-6 segments and intercut them with PIL kinetic-typography spec/CTA cards (italic skew, 1.08x outline echo, 3D extrusion, slam-with-shake, inversion flash) plus a real-logo PIL end card (base64-decoded from the brand SVG), center-crop 1:1 to 9:16, and explicit-map mux a music bed. Deterministic, FREE (PIL + FFmpeg), no paid calls, the real logo and spec typography stay pixel-crisp. The paid steps (the ONE Seedance i2v, the music) are separate capabilities; the recipe orchestrates them. Use for the product-hypermotion format.

Quality

77%

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/ads/capabilities/render-hypermotion/SKILL.md

Quality

Content

70%

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

Well-structured documentation-grade content: a clear sequenced workflow with validation checkpoints and excellent progressive disclosure into real bundle files. The weaker spots are conciseness (contract duplication) and actionability (the in-body Run block is comment pseudocode rather than executable commands).

Suggestions

Make the '## Run' block executable (real ffmpeg/PIL commands or a copy-paste entrypoint) instead of comments-only pseudocode, since the full commands already exist in PIPELINE.md.

Drop the redundant '## Contract' section (or the parallel '## The FREE assembly' bullets) so the FREE/Deterministic guarantees are stated once, cutting repetition.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and avoids basic-concept padding, but it restates the FREE/$0/Deterministic contract twice (the '## The FREE assembly' bullets and the '## Contract' section) and duplicates content already in README.md, so it could be tightened.	2 / 3
Actionability	Concrete specifics are present (the crop filter intent, '-map 0:v -map 1:a', 'verify ffprobe ≈ 192 kbps'), but the '## Run' block is comments-only pseudocode with no executable commands, and full executable code is deferred to PIPELINE.md.	2 / 3
Workflow Clarity	A clear Phase 0→4 sequence is laid out with explicit validation checkpoints (GATE 1, the PAID gate, Phase 4 watch/QC, the ffprobe bit_rate verify) and a re-render-vs-re-fire feedback loop for error recovery.	3 / 3
Progressive Disclosure	The body is a clean overview that signals one-level-deep references to real bundle files (config.example.json, PIPELINE.md, README.md), each described by purpose, with content appropriately split for easy navigation.	3 / 3
	Total	10 / 12 Passed

Description

85%

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 specific, well-scoped description that names concrete assembly actions and gives an explicit use-trigger, with strong distinctiveness. Its main weakness is trigger-term quality: the trigger relies on a coined format name and technical jargon rather than natural user phrasings.

Suggestions

Broaden the 'Use for...' clause with natural user phrasings (e.g. 'Use for product sizzle ads, kinetic-typography spec videos, or vertical 9:16 product hype reels') so it triggers on how users actually ask.

Move deep implementation jargon ('1.08x outline echo', 'slam-with-shake') out of the description and into the body/bundle, keeping the description focused on what the skill produces.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'dice ONE Seedance 2.0 hypermotion clip into 5-6 segments and intercut them with PIL kinetic-typography spec/CTA cards', 'real-logo PIL end card (base64-decoded from the brand SVG)', 'center-crop 1:1 to 9:16', and 'explicit-map mux a music bed'.	3 / 3
Completeness	Explicitly answers both what (detailed assembly steps) and when ('Use for the product-hypermotion format'), satisfying the explicit-trigger requirement that would otherwise cap completeness at 2.	3 / 3
Trigger Term Quality	Has a 'Use for the product-hypermotion format' trigger, but it leans on a coined format name and heavy jargon (Seedance 2.0, '1.08x outline echo'), missing the natural keyword variations a user would actually say.	2 / 3
Distinctiveness Conflict Risk	The format is highly niche — one-call-many-cuts hypermotion + PIL kinetic-typography + real-logo end card — with distinct triggers that are unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: gooseworks-ai/goose-skills
Path: skills/ads/capabilities/render-hypermotion/SKILL.md
Commit: 8866b2a

Reviewed: 1 day 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.