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

71%

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

60%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 documentation-grade skill body with a clear phased pipeline and properly signaled bundle references. Its weaknesses are repetitive FREE/Deterministic refrains and a Run section that is comment pseudocode rather than executable commands.

Suggestions

Replace the comment-only Run block with at least one concrete, copy-pasteable command sequence (e.g., the actual ffmpeg center-crop + concat + explicit-map mux invocation) so the body is executable without reading PIPELINE.md.

De-duplicate the 'Deterministic, FREE, no paid calls' refrain — state the contract once in the Contract section and reference it elsewhere instead of restating.

Move the exact per-card treatment parameters (1.08×, ±1% scale, ±3px drift) fully into PIPELINE.md/config.example.json and keep the body's FREE assembly section at overview level to reduce inline duplication.

Dimension	Reasoning	Score
Conciseness	Mostly dense with earned signal (1.08×, ±1% scale, 124 BPM, -map 0:v -map 1:a), but the 'Deterministic, FREE, no paid calls' mantra repeats across the overview, FREE assembly, Run, and Contract sections and could be tightened.	3 / 5
Actionability	Provides concrete parameters and a phased Run section, but the Run code block is comments-only pseudocode with no executable commands, and the actual PIL impls are explicitly not vendored — execution requires reading PIPELINE.md and adapting external scripts.	3 / 5
Workflow Clarity	Clear Phase 0→4 sequence (assets → PAID Seedance+music gated → FREE PIL cards → FREE dice/intercut/mux → watch/QC) with checkpoints like 'verify ffprobe ≈ 192 kbps' and a Phase 4 QC pass; minor validation detail lives in PIPELINE.md rather than inline.	4 / 5
Progressive Disclosure	Well-signaled one-level-deep references (config.example.json, PIPELINE.md, README.md, all present in scripts/) with a clear overview, though the FREE assembly section inlines exact parameters that partly duplicate PIPELINE.md.	4 / 5
	Total	14 / 20 Passed

Description

83%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 dense, highly specific description that concretely enumerates the FREE assembly actions and names the niche format clearly. The main weakness is a terse single trigger phrase and limited synonym coverage.

Suggestions

Expand the 'Use for...' clause to list concrete user-facing triggers (e.g., 'Use when building a product-hypermotion sizzle, a kinetic-typography spec-card ad, or a 9:16 product video with intercut spec cards').

Add natural synonym phrases users might say (e.g., 'kinetic type ad', 'spec-card sizzle', 'vertical product video') to broaden trigger matching.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'dice ONE Seedance 2.0 hypermotion clip into 5-6 segments', 'intercut them with PIL kinetic-typography spec/CTA cards', 'center-crop 1:1 to 9:16', 'explicit-map mux a music bed', 'base64-decoded from the brand SVG' — with comprehensive coverage of the assembly pipeline.	5 / 5
Completeness	Clearly answers 'what' with detailed assembly actions and includes an explicit 'Use for the product-hypermotion format' trigger, but the 'when' is a single terse phrase rather than a fuller set of concrete trigger scenarios.	4 / 5
Trigger Term Quality	Good keyword coverage of the niche — 'product-hypermotion', 'kinetic-typography video format', 'Seedance 2.0 hypermotion' — that a user of this format would naturally say, though it lacks synonyms or file-extension variants.	4 / 5
Distinctiveness Conflict Risk	Targets a highly specific niche ('product-hypermotion + kinetic-typography video format') with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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: gooseworks-ai/goose-skills
Path: skills/ads/capabilities/render-hypermotion/SKILL.md
Commit: 2523432

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