gooseworks-ai/goose-skills / skills/video/render-flat-vector-explainer
render-flat-vector-explainer
VerifiedAssemble the FREE steps of the flat-vector-explainer video format — a flat-illustration host character (who, where, tone, voice and music come from the recipe choices) 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.2 KB |
| scripts/PIPELINE.md | markdown | 4.4 KB |
| scripts/README.md | markdown | 5.6 KB |
| scripts/config.example.json | config | 10.7 KB |
| skill.meta.json | config | 183 B |
| tests/smoke-test.md | markdown | 1.2 KB |
scripts/README.md
View on GitHub# render-flat-vector-explainer — free assembly how-to
This capability is **documentation-grade**: the format's source recipe is a
documented recipe, not a runnable end-to-end app. There are no standalone scripts here to
`--config` and fire. Instead this folder ships:
- **`config.example.json`** — the full config schema (the Greenmoth "Happy Plants = 4
Products" worked example). Copy its structure to `config.json`; fill the
creative fields (host, setting, tone, voice, music) from the recipe's choices and the
brand fields (palette, products, copy) from the new brand — never the demo's values.
- **`PIPELINE.md`** — the field-by-field map from every `config.json` key to the
per-project script that builds each step of the demo (in the project's
`working/`), and which phase / paid-or-free it is.
- **this README** — the FREE assembly steps the agent runs by hand with ffmpeg + Remotion +
PIL after the paid gen steps have produced the character clips, VO, and music.
The paid generative steps (keyframes, clean plates, Kling i2v, VO, music) are **separate
capabilities** the recipe orchestrates and gates — see the recipe. Everything below is
free and deterministic.
## The two separations that make this format work
1. **Motion layer != text layer.** i2v only ever animates a **text-stripped clean plate**.
ALL words/numerals/chips/taglines/slate/CTA are composited on top as an **animated
Remotion DOM overlay** — never baked into the keyframe. Baked text warps under i2v and
you lose the ability to retime/restyle it.
2. **Real assets != AI assets.** The per-step product photo and the closing "N products"
grid are the **real product webps composited with PIL**. AI duplicates SKUs in a grid.
Only the character vignettes + backgrounds are generative.
## Free assembly steps
Run these after the paid steps have delivered the per-scene Kling clips (character beats),
the VO (with char-level timestamps), and the music bed.
### 1. Remotion overlay -> animated silent master (character-locked)
Build a Remotion composition that imports each Kling clip as the moving base and
composites the scene's `overlay` (numeral, chip, tagline, slate headline, CTA pill,
wordmark, url) as **animated DOM on top**. Keep the **motion layer and text layer
strictly separate** — the Kling footage is the only moving base; text is DOM.
- `kind: character` scenes -> Kling clip base + DOM overlay.
- `kind: slate` / `grid` / `cta` scenes -> Remotion text only, **no i2v** (a solid brand
`ground` color + the headline / grid / CTA).
- Use the brand palette + display font from the config for crisp glyphs at the exact brand
color. Real DOM type = crisp; never let i2v render the type.
Render the composition to `working/silent-master.mp4` — the **animated** master.
Everything downstream slices from this, never from an earlier static intermediate.
### 2. PIL real-product grid
Composite the closing "N products" lockup from `product_grid.images` (the real product
webps) onto `product_grid.ground` in the configured `layout` (e.g. 2x2). **Preserve each
product's aspect ratio — never stretch, never AI-generate the grid** (AI dupes SKUs). The
same real webps are also the per-step callout photos in the character beats. Product webps
are git-LFS in the brand folder — fetch + checkout first (pointers are ~131-byte stubs).
### 3. Caption burn (word-synced)
Build word-by-word burned captions from the eleven_v3 with-timestamps **char-level
timings** (libass; Klap is the hosted equivalent). Style per `captions.style` (e.g. Inter
56 white + 4px outline, bottom-third MarginV 360). **Suppress captions on the
slate/grid/CTA scenes** (`captions.suppress_on_scenes`) — those carry their own on-screen
text and two text layers collide. Burn captions **LAST**, after the audio mux.
### 4. Audio mix + 50s master
Place each scene's VO line at its scene start; duck the music under the VO with
`sidechaincompress`; `loudnorm I=-15` VO-forward (music `loudnorm I=-25 + volume 0.5`,
final `alimiter limit=0.89`, ~-15 LUFS / -1 dBTP). Mux the silent master + mixed audio,
then burn captions last -> `finals/master-final.mp4` (~50s full-story master).
### 5. 50s -> 30s cut (from the ANIMATED master)
Slice each beat's region OUT of `working/silent-master.mp4` — the **animated** master,
**never** an earlier static Ken-Burns / segs round (the mtime is the tell; a finished audio
mix can hide frozen characters). Trim short beats (never freeze a frame); gently slow long
beats (`setpts`, clamp <=1.6x) so motion stretches instead of holding. Re-burn scaled
captions offset to the new scene starts; keep suppression on the slate/grid/CTA scenes.
Output `finals/master-final-30s-v1.mp4` — the shipped 30s deliverable.
Optional v2 cutdown: hook-led montage (hook -> slate -> grid pulled forward -> rapid
4-product montage of number + product only -> CTA), >=4 cuts / 10s.
## QC before ship (mandatory)
- **Frame-diff a character scene** (blend=difference heatmap): **localized** face/hand
glow = real motion; whole-outline glow = a static pan = you sliced the wrong (static)
source — re-point the cut at `silent-master.mp4`.
- `/watch` the final: real localized motion, correct duration (~30s ±0.3s), caption sync,
correct numerals/labels, no AI text leak in the i2v footage, N distinct real products in
the grid (no AI dupes), VO-forward mix (~-15 LUFS).
- Canvas 1080x1920, 30fps, h264, aac present.
## Requires
Node + Remotion, `Pillow` (PIL), `ffmpeg` with libass. All free — the paid keys
(`FAL_API_KEY`, `ELEVENLABS_API_KEY`) belong to the separate paid capabilities, which
route through the GooseWorks proxies so the calls are charged to your GooseWorks credits.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |