remotion-video
Use when the user wants to generate a rendered promotional video (not just a script) for a PR, feature, or product change — produces a Remotion project, iterates with preview, and outputs mp4 + poster for X/LinkedIn/social.
AlemTuzlak · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add AlemTuzlak/skills --skill remotion-videoAbout this skill
name: remotion-video description: Use when the user wants to generate a rendered promotional video (not just a script) for a PR, feature, or product change — produces a Remotion project, iterates with preview, and outputs mp4 + poster for X/LinkedIn/social.
Remotion Video
Turn a PR into a rendered short-form promo video with a hook, code moments, and CTA, using Remotion. Iterate with live preview in Remotion Studio, then render video.mp4 and poster.jpg for X/LinkedIn/social.
Unlike /video-script (which produces a textual script), this skill produces the actual video file.
Triggers
Invoke when the user says: "make a video for this PR", "remotion video", "render a promo video", "video for X/LinkedIn", or when selected from /marketing-pipeline.
Process Flow
Resolve input
→ Phase 1: Discovery
→ Phase 2: Configuration
→ Phase 3: Narrative planning
→ Phase 4: Scaffold
→ Phase 5: First draft + iterate
→ Phase 6: Render
→ Phase 7: Cleanup
Phases 1, 3, 5, and 7 have explicit approval gates. Phase 2 is an interactive Q&A. Phase 5 is a freeform iteration loop that can run many rounds.
"Use Sane Defaults" / "Don't Ask Questions" — What It Does and Doesn't Override
When the user invokes the skill with phrasing like "use sane defaults", "don't ask questions", "non-interactive", "just ship it", or any equivalent — interpret it precisely:
It DOES override (skip the prompt, pick the default):
- Q2.1 duration → derive from scope using the ladder in Q2.1 (still in the 15–60s window); pick the midpoint of the matched scope band and proceed without asking
- Q2.2 aspect ratio → 16:9 landscape
- Q2.3 project location →
marketing/<feature-slug>/remotion/ - Q2.4 brand confirmation (the "use these / customize / provide your own?" question)
- Phase 1.4 scope confirmation
- Phase 3.0 motif confirmation
- Phase 3.1 story-pattern confirmation
- Phase 3.3 scene-plan approval
- Phase 5 freeform iteration loop (the "what would you like to change?" prompt)
It does NOT override (must always run regardless):
- Brand color/font/logo scanning (Q2.4 detection — see HARD-GATE in Q2.4). Hardcoding colors from training-data assumptions about a project is a forbidden shortcut.
- Phase 5 preview (Remotion Studio must start and the studio URL must be opened in the browser before the render runs). Even in fully unattended mode, the user can interrupt; the agent must not pre-decide for them.
- Phase 6 pre-render audits (storytelling, hook rules, motif presence, pacing variance, value-prop timing, contrast). These exist to prevent shipping a generic video.
- Phase 7 cleanup question (the user owns project disposition).
If you're tempted to skip a HARD-GATE because the user "said no questions" — re-read this section. The user said no questions, not no gates.
Input Resolution
Resolve the argument (if provided) in this order:
- Path to a marketing brief (
.mdcontaining "Executive Summary" or "Key Messages") → marketing brief - Path to a blog post (
.mdwith blog post structure) → blog post - Path to a changelog → changelog
- GitHub PR URL or
#\d+pattern → PR - Matches
<ref>..<ref>or<ref>...<ref>(alphanumeric +/,_,.,-on each side) → git ref range - Resolves to an existing file/directory → codebase feature
- Otherwise → freeform text
If no argument is provided, ask: "What should the video be about? You can provide a PR URL/number, marketing brief, blog post, changelog, git ref range, file/directory path, or just describe the feature."
When invoked from the pipeline with a PR and upstream marketing-brief/blog-post paths, read both: PR for technical accuracy, upstream content for positioning/tone.
(Detailed phase specs begin below — see Phase 1.)
Phase 1: Discovery
Step 1.1 — Check remotion-best-practices availability
Attempt to invoke the remotion-best-practices skill via the Skill tool. If unavailable, present:
"The
remotion-best-practicesskill isn't installed. Options: a) proceed with baseline Remotion knowledge (quality may be reduced) b) wait while you install it c) cancel"
If the user picks (a), emit a warning in the final summary noting reduced quality.
Step 1.2 — Analyze input
| Input type | What to read |
|---|---|
| Marketing brief | positioning, key messages, audience |
| Blog post | headline, narrative, examples |
| Changelog | highest-impact entry |
| PR | gh pr view <n> --json title,body,files,labels, diff (gh pr diff), commit messages, linked issues |
| Git refs | git diff <range> + git log <range> --oneline |
| Codebase path | read the specified files/directories |
| Freeform | parse the user's description |
For PRs with 20+ files, filter to user-facing changes only — skip tests/, ci/, .github/, lockfile changes, dep bumps.
Error handling:
ghnot available → tell the user, ask for an alternative (diff file, freeform description)- Invalid PR/ref → ask user to verify
- File not found → ask for the correct path
Step 1.2a — PR deep analysis (when input is a PR)
When the input is a PR, the brief table in Step 1.2 is not enough. PR bodies are routinely vague, outdated, or focused on implementation rather than user value, and a video built off the body alone tends to overclaim or miss the headline angle entirely. Before continuing to Step 1.3, run this structured analysis and produce a written PR analysis block that becomes the source of truth for Steps 1.4 (scope confirmation), Q2.1 (duration ladder), and Phase 3 (narrative planning).
Mandatory steps — do all of them:
- Pull metadata and identify the base branch.
Recordgh pr view <n> --json number,title,body,baseRefName,headRefName,files,labels,commits,additions,deletionsbaseRefName(usuallymain/master/develop) — that is the diff reference.gh pr diff <n>automatically compares the PR head against this