$npx -y skills add MoizIbnYousaf/marketing-cli --skill cmo-remotionBrand-grounded Remotion video pipeline. Take a brief, ground it in brand/ (voice, audience, positioning, creative-kit), write a beat sheet, scaffold a fresh Remotion project, generate any required assets, compose with frame-driven animations, and bake a final MP4. Use this skil
| 1 | # /cmo-remotion — Brand-Grounded Remotion Video Pipeline |
| 2 | |
| 3 | The mktg-native end-to-end pipeline for **building a new Remotion video from a brief**. Brief in, MP4 out. Brand memory grounds it; `remotion-best-practices` powers the compose stage. |
| 4 | |
| 5 | ## North Star |
| 6 | |
| 7 | The user wants a Remotion video that is *theirs* — voiced like their brand, aimed at their audience, hitting their positioning. They do not want a generic motion-graphics template, and they do not want to recreate someone else's video literally. |
| 8 | |
| 9 | This skill is the Remotion equivalent of `/cmo-video`, with one key difference: `/cmo-video` is a *style transfer pipeline* — point it at a reference URL and it deconstructs the reference, generates fresh assets in that idiom, and ships a recreation. `/cmo-remotion` is a *brief-to-render pipeline* — start from a goal ("explain our product in 30s", "demo the CRT shader", "ad for our launch"), ground it in `brand/`, and ship. |
| 10 | |
| 11 | You collaborate with the user across six stages, the same way `/cmo` collaborates across the marketing skill stack: suggest, ask one question at a time, push back when the brief is too big, and never silently advance. Show the beat sheet, get a yes, then scaffold. Show the asset list, get a yes, then generate. Show a single frame at composition midpoint, get a yes, then bake the full render. |
| 12 | |
| 13 | ## When to use (vs other video skills) |
| 14 | |
| 15 | | User says | Route to | Why | |
| 16 | |---|---|---| |
| 17 | | "make a video like this <URL>" | personal `/cmo-video` | That pipeline is style-transfer from a reference. Stop after stage 2 if they only want the deconstruction. | |
| 18 | | "I have these PNG slides, make a video" | `/video-content` | Three-tier ffmpeg/Remotion pipeline that takes existing slides → video. No scaffold, no compose-from-scratch. | |
| 19 | | "make me a TikTok slideshow" | `/tiktok-slideshow` | Format-specific orchestrator that chains `/slideshow-script → /paper-marketing → /video-content`. | |
| 20 | | "build me a Remotion video about X" | **this skill** | New composition from a brief. Code-driven, frame-driven, brand-grounded. | |
| 21 | | "make a CRT shader / glitch / scanline video" | **this skill** | Stage 5 loads `remotion-best-practices/rules/html-in-canvas.md` and points you at the CRT template. | |
| 22 | | "edit my finished video" | Not this skill | Remotion is a video *generator*, not an editor. Use a real NLE for cuts on existing footage. | |
| 23 | | "transcribe / summarize this video" | `mktg transcribe` then `/summarize` | Different intent. | |
| 24 | |
| 25 | ## Workflow — the six stages |
| 26 | |
| 27 | ``` |
| 28 | 1. BRIEF capture goal + audience + runtime + aspect + one-line takeaway |
| 29 | 2. SCRIPT beat sheet (scene · duration · voiceover · onscreen · visual · motion) |
| 30 | 3. SCAFFOLD npx create-video@latest --yes --blank --no-tailwind <slug> |
| 31 | 4. ASSETS generate PNGs via /codex:image or /image-gen → rembg → public/ |
| 32 | 5. COMPOSE load remotion-best-practices, pick rule files by intent, build frame-driven |
| 33 | 6. BAKE single-frame midpoint check → npx remotion render → MP4 |
| 34 | ``` |
| 35 | |
| 36 | Each stage produces a checkpoint artifact under `marketing/video/<slug>/<n>-<stage>/`. The pipeline is **resumable** — read `pipeline.json`, pick a stage, continue. Never re-run a completed stage unless the user explicitly asks for "redo stage X". |
| 37 | |
| 38 | ### Stage 1 — |