render-flat-vector-explainer

Assemble the FREE steps of the flat-vector-explainer video format — a flat-illustration creator-character walks a countable N-step product routine, one step per beat, and Remotion composites every chip/numeral/tagline/slate/CTA as an animated DOM overlay ON TOP of the Kling i2v character clips (text is NEVER baked into a keyframe — i2v warps type), the closing 'N products' grid is a PIL composite of the REAL product photos (not AI), full-sentence VO drives word-by-word burned captions over a VO-forward music bed, and the ~50s animated silent master is re-cut to a 30s deliverable FROM the animated master (never a static intermediate). Documentation-grade — ships config.example.json + PIPELINE.md + a README of the free assembly; the paid gen steps (keyframes, Kling i2v, VO, music) are separate capabilities the recipe orchestrates. Use for the flat-vector-explainer format.

Quality

64%

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-flat-vector-explainer/SKILL.md

Quality

Content

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

The body is well-structured as a documentation-grade overview with real bundle references and a clear assembly sequence, but it is held back by redundant restating of the non-negotiables across sections, no executable code blocks, and only implicit validation checkpoints for a batch render workflow.

Suggestions

Collapse the 'two non-negotiable separations' and 'Contract' sections so each non-negotiable is stated once, cutting redundant tokens.

Add an explicit validate-fix-retry loop for the batch/render steps (e.g. frame-diff after the 30s cut, re-burn captions if motion is not localized) to lift workflow clarity above 3.

Either inline a minimal executable ffmpeg/Remotion snippet for one beat or make the pointer to scripts/README.md a clearly labeled navigation block.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude knows the toolchain (ffmpeg, Remotion, PIL, libass, sidechaincompress) without padding, but the 'two non-negotiable separations', 'free assembly steps', and 'Contract' sections restate the same non-negotiables (text never baked, real vs AI, cut from animated master) redundantly.	3 / 5
Actionability	Steps carry concrete parameters (cfg 0.5, loudnorm I=-15, setpts <=1.6x) but there are no executable code blocks in the body; the actual ffmpeg/Remotion/PIL commands are deferred to scripts/README.md, so guidance is specific but not copy-paste ready.	3 / 5
Workflow Clarity	The free assembly is clearly sequenced (Remotion overlay -> PIL grid -> captions -> audio mix/master -> 30s cut), but for a batch/render workflow the validation checkpoints are only implicit ('frame-diff to prove localized motion', 'TEST one scene before batching') rather than structured validate-fix-retry loops.	3 / 5
Progressive Disclosure	The body is an overview that signals one-level-deep, real bundle references (scripts/README.md, scripts/PIPELINE.md, scripts/config.example.json) and splits content into clear sections; references are clear but mentioned inline rather than in a dedicated navigation block.	4 / 5
	Total	13 / 20 Passed

Description

76%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 is highly specific and distinctive, clearly carving out a niche format with concrete assembly actions and an explicit use clause. Its main weakness is trigger-term breadth: the natural trigger is a single format name with little synonym coverage, slightly capping completeness and trigger quality.

Suggestions

Broaden the 'Use for...' clause with natural trigger variations, e.g. 'Use for flat-vector product-routine explainer videos, DTC-style routine walkthroughs, or when the user asks for an animated N-step product routine.'

Consider trimming the dense parenthetical asides (e.g. 'text is NEVER baked into a keyframe — i2v warps type') that are implementation detail rather than trigger guidance.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Remotion composites every chip/numeral/tagline/slate/CTA as an animated DOM overlay', 'PIL composite of the REAL product photos', 'full-sentence VO drives word-by-word burned captions', 're-cut to a 30s deliverable' — covering the assembly comprehensively.	5 / 5
Completeness	Clearly answers 'what' with concrete assembly actions and includes an explicit 'Use for the flat-vector-explainer format' trigger, but the 'when' is a single narrow format-name clause that could be more specific about the situations that call for it.	4 / 5
Trigger Term Quality	Names the domain ('flat-vector-explainer video format') and component terms (Remotion, Kling i2v, PIL, VO, captions), but the natural user-facing trigger is essentially a single phrase ('Use for the flat-vector-explainer format') with no synonyms or common variations.	3 / 5
Distinctiveness Conflict Risk	Targets a clearly named niche ('flat-vector-explainer video format') with distinct, highly specific triggers, making overlap with other skills minimal.	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
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-flat-vector-explainer/SKILL.md
Commit: 2523432

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