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 |
tests/smoke-test.md
View on GitHub# Smoke Test
This capability is documentation-grade — it ships the config schema + assembly recipe, not
a runnable end-to-end script. The check is that the docs + config are present and coherent.
Pass when:
- `scripts/config.example.json` parses as valid JSON and carries the flat-vector-explainer
schema (concept + single countable point, character anchor, ordered `scenes[]` with
`kind` in character/slate/grid/cta, `product_grid` of real webps, voice, music, captions
with `suppress_on_scenes`, cutdowns, post_production toggles).
- `scripts/PIPELINE.md` maps every config field to its source script + phase + paid/free.
- `scripts/README.md` documents the FREE assembly steps: Remotion text/DOM overlay kept
SEPARATE from the Kling i2v motion layer (character-locked), PIL real-product grid,
word-synced caption burn, VO-forward audio mix, and the 50s -> 30s cut taken FROM the
animated silent master (never a static intermediate).
- The SKILL.md description is a single line with no ": " and states the paid gen steps
(keyframes, Kling i2v, VO, music) are separate capabilities the recipe orchestrates.
- No paid call is made by this capability. Paid caps route through the GooseWorks proxies
(bill the agent, no direct provider host).
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 |