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

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

Quality

Content

57%

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 with good progressive disclosure to real bundle files and a clear step sequence, but it is held back by repetition of the same two rules, a lack of inline executable commands, and missing explicit validation checkpoints in the assembly workflow.

Suggestions

State the two non-negotiable separations once (e.g. in the Contract) and reference them from the steps instead of restating them in three sections.

Inline at least one concrete executable command per free step (e.g. the loudnorm/sidechain ffmpeg line or a Remotion snippet) rather than delegating all detail to README.md.

Add explicit validate-then-proceed checkpoints to the free assembly (e.g. 'frame-diff to confirm localized motion before recutting'; 'spot-check one beat's captions before batch-burning').

Dimension	Reasoning	Score
Conciseness	The body is dense and operational without explaining basic concepts, but restates the two non-negotiable separations three times (the 'two non-negotiable separations' section, the free-steps bullets, and the Contract), which is redundant padding — 'mostly efficient but could be tightened'. Not a 3 due to that repetition.	2 / 3
Actionability	Tools and parameters are named ('Remotion DOM overlay', 'PIL', 'loudnorm I=-15', 'setpts <=1.6x', 'sidechaincompress') but the body gives no executable commands or code — it defers the actual ffmpeg/Remotion/PIL detail to scripts/README.md, fitting 'some concrete guidance but incomplete; missing key details'. Not a 3 because nothing in the body is copy-paste ready.	2 / 3
Workflow Clarity	The 'Free assembly steps' form a clear 5-step sequence (Remotion overlay -> PIL grid -> captions -> audio mix -> 30s cut), but validation checkpoints are implicit rather than inline; 'frame-diff to prove localized motion' and 'TEST one scene before batching' live in the Contract/paid-steps, not the workflow, leaving batch/cut operations without an explicit validate-fix-retry loop — 'steps listed but validation gaps'.	2 / 3
Progressive Disclosure	The body is an overview that clearly signals one-level-deep references to real bundle files — 'see scripts/README.md for the ffmpeg/Remotion/PIL detail', 'scripts/PIPELINE.md', and 'scripts/config.example.json' (all verified present) — matching 'clear overview with well-signaled one-level-deep references; content appropriately split'.	3 / 3
	Total	9 / 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.

The description is highly specific, complete, and distinctive with an explicit trigger, but is overloaded with implementation jargon that weakens the natural trigger-term quality a user would actually voice. It also leans verbose for a description field.

Suggestions

Trim implementation parameters (cfg 0.5, loudnorm I=-15, sidechaincompress) from the description; they belong in the body/scripts, not the trigger summary.

Broaden natural trigger terms beyond the single phrase 'flat-vector-explainer' (e.g. 'flat vector explainer video', 'DTC product routine explainer') so users can match it more naturally.

Shorten the description so the 'what' and the 'Use for...' trigger land without a wall of clause-level detail.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Remotion composites every chip/numeral/tagline/slate/CTA as an animated DOM overlay ON TOP of the Kling i2v character clips', 'PIL composite of the REAL product photos', and 're-cut to a 30s deliverable FROM the animated master' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers what ('Assemble the FREE steps of the flat-vector-explainer video format...') and when ('Use for the flat-vector-explainer format.'), satisfying the 'clearly answers both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	The natural term 'flat-vector-explainer' / 'flat-vector-explainer video format' is present, but it is swamped by implementation jargon ('Kling i2v', 'cfg 0.5', 'loudnorm I=-15', 'sidechaincompress', 'DOM overlay') a user would not actually say, and common variations are thin — fitting 'some relevant keywords but missing common variations'. Not a 3 because natural-term coverage is narrow rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	The 'flat-vector-explainer' niche with its bespoke motion/text and real/AI separations is highly specific and unlikely to trigger for the wrong skill, matching 'clear niche with distinct triggers; unlikely to conflict'.	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-flat-vector-explainer/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.