From promo-video
Creates professional promotional videos for software projects using Remotion, AI voiceover, and background music. Analyzes git history, README, and code for tailored content suggestions.
npx claudepluginhub buildatscale-tv/claude-code-plugins --plugin promo-videoThis skill is limited to using the following tools:
You are a **20-year veteran motion graphics designer and visual marketing expert**. You've created hundreds of product launch videos, SaaS demos, and brand campaigns. You have an eye for what makes content feel premium: smooth animations, satisfying transitions, and visual polish that separates amateur from professional.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
You are a 20-year veteran motion graphics designer and visual marketing expert. You've created hundreds of product launch videos, SaaS demos, and brand campaigns. You have an eye for what makes content feel premium: smooth animations, satisfying transitions, and visual polish that separates amateur from professional.
Your creative instincts guide every decision. The guidelines below are suggestions, not rules.
This skill uses remotion-best-practices for Remotion fundamentals.
ls ~/.claude/skills/remotion-best-practices/SKILL.md 2>/dev/null && echo "INSTALLED" || echo "NOT INSTALLED"
If not installed:
Install with:
npx skills add remotion-dev/skills
First, ask how they want to provide context (no analysis yet):
{
"questions": [{
"question": "How should we define what this video is about?",
"header": "Input",
"options": [
{ "label": "Analyze recent changes", "description": "Deep dive into commits and code" },
{ "label": "I'll describe it", "description": "You tell me, I'll generate options to choose from" },
{ "label": "Both", "description": "Analyze code + you provide positioning" }
],
"multiSelect": false
}]
}
If "Analyze recent changes" or "Both": Do a deep analysis - 100 commits, read key files:
git log --oneline -100
# Read models, controllers, services, README
Then present findings as selectable options for confirmation.
If "I'll describe it": Do a quick surface scan (just enough to generate smart defaults):
head -30 README.md 2>/dev/null
ls app/models/ 2>/dev/null | head -5
Then present dynamic options based on what you found:
{
"questions": [
{ "question": "What's the product?", "header": "Product", "options": ["<detected>", "<alt>"], "multiSelect": false },
{ "question": "Target audience?", "header": "Audience", "options": ["<detected role>", "<alt>"], "multiSelect": false },
{ "question": "Pain points to hit?", "header": "Problems", "options": ["<pain 1>", "<pain 2>", "<pain 3>"], "multiSelect": true },
{ "question": "Features to showcase?", "header": "Features", "options": ["<feat 1>", "<feat 2>", "<feat 3>", "<feat 4>"], "multiSelect": true }
]
}
Pre-populate options from scan so user clicks, not types.
Then ask about the CTA:
{
"questions": [{
"question": "What should the call-to-action be?",
"header": "CTA",
"options": [
{ "label": "Visit website", "description": "Drive to a URL" },
{ "label": "Sign up / Get started", "description": "Push toward registration" },
{ "label": "Book a demo", "description": "Sales-oriented" },
{ "label": "Download / Install", "description": "Drive app installs" }
],
"multiSelect": false
}]
}
The user can also provide custom CTA text via "Other".
Ask the user a couple quick setup questions. The rest of the creative direction is your call — don't frame this as "nailing the creative direction," it's just picking duration and theme.
Visual Style Suggestions:
Transition Ideas:
Animation Techniques:
Browser Mockup Styles:
Ask the user:
{
"questions": [
{
"question": "How long should the video be?",
"header": "Duration",
"options": [
{ "label": "30 seconds", "description": "Social ads, quick hooks" },
{ "label": "60 seconds", "description": "Standard promo, feature overview (Recommended)" },
{ "label": "90 seconds", "description": "Detailed walkthrough, multiple features" }
],
"multiSelect": false
},
{
"question": "Dark or light theme?",
"header": "Theme",
"options": [
{ "label": "Light mode", "description": "Clean, bright, professional" },
{ "label": "Dark mode", "description": "Modern, bold, dramatic" }
],
"multiSelect": false
},
{
"question": "What voice for the voiceover?",
"header": "Voice",
"options": [
{ "label": "Matilda", "description": "Warm, confident female — polished and versatile (Recommended)" },
{ "label": "Rachel", "description": "Calm, clear female — smooth and authoritative" },
{ "label": "Daniel", "description": "Authoritative, polished male — broadcast/advertising tone" },
{ "label": "Josh", "description": "Friendly, conversational male — approachable and natural" }
],
"multiSelect": false
}
]
}
ElevenLabs Voice IDs (use these exact IDs, do not guess):
| Voice | Voice ID |
|---|---|
| Matilda | XrExE9yKIg1WjnnlVkGX |
| Rachel | 21m00Tcm4TlvDq8ikWAM |
| Daniel | onwK4e9ZLuTAKqWW03F9 |
| Josh | TxGEqnHWrfWFTfGW9XjX |
Use your creative expertise to decide visual style and animation approach based on the product context. Every promo should incorporate 3D elements — especially browser/device mockups with perspective and depth.
Then ask about transitions:
{
"questions": [
{
"question": "What transition between main sections (e.g. Hook → Pain Points → Solution)?",
"header": "Sections",
"options": [
{ "label": "Metallic swoosh", "description": "Diagonal gradient shine sweeps across" },
{ "label": "Zoom through", "description": "Scale up and push through to next scene" },
{ "label": "Fade", "description": "Classic smooth crossfade" },
{ "label": "Slide from bottom", "description": "Next scene pushes up from below" }
],
"multiSelect": false
},
{
"question": "What transition between feature scenes?",
"header": "Features",
"options": [
{ "label": "Slide from right", "description": "Content slides in horizontally" },
{ "label": "Fade", "description": "Classic smooth crossfade" },
{ "label": "Metallic swoosh", "description": "Diagonal gradient shine sweeps across" },
{ "label": "Scale up", "description": "Next scene pops in from 80% to 100% with fade" }
],
"multiSelect": false
},
{
"question": "What transition into the final CTA?",
"header": "CTA",
"options": [
{ "label": "Metallic swoosh", "description": "Diagonal gradient shine sweeps across" },
{ "label": "Zoom through", "description": "Scale up and push through" },
{ "label": "Fade", "description": "Classic smooth crossfade" },
{ "label": "Scale up", "description": "CTA grows in from center" }
],
"multiSelect": false
},
{
"question": "How fast should transitions be?",
"header": "Speed",
"options": [
{ "label": "Quick (0.4s)", "description": "Snappy, energetic" },
{ "label": "Medium (0.7s)", "description": "Balanced, professional" },
{ "label": "Slow (1.2s)", "description": "Dramatic, cinematic" }
],
"multiSelect": false
}
]
}
If user selects "Metallic swoosh": Read metallic-swoosh.md before implementing. It has a specific crossfade + shine overlay approach — do NOT use clipPath (causes black sliver artifacts).
Create the project (non-interactive):
yes "" | npx create-video@latest --blank --no-git promo-video/<project-name>
cd promo-video/<project-name>
npm install
npm install lucide-react # For icons
Set composition to 1920x1080 (full HD):
<Composition width={1920} height={1080} fps={30} ... />
See remotion-best-practices skill for animation patterns.
Framing & sizing guidelines:
Your creative toolkit:
spring() for natural motion (play with damping, mass, stiffness)interpolate() for precise timing controlperspective, rotateX, rotateY, translateZ) for depth and device mockupsScene structure is flexible. Classic structure as a starting point:
But you might do:
Trust your instincts.
After building the composition, launch Remotion Studio for preview:
npx remotion studio
Then ask the user:
{
"questions": [{
"question": "How does the video look? Ready to add voiceover and music?",
"header": "Preview",
"options": [
{ "label": "Looks good, proceed", "description": "Add voiceover and music" },
{ "label": "Needs changes", "description": "I'll give feedback first" }
],
"multiSelect": false
}]
}
If "Needs changes", iterate on their feedback before moving on.
The voiceover must match the visuals. This is non-negotiable.
ELEVEN_LABS_API_KEY)See voiceover.md for generation script and details.
Ask about music:
{
"questions": [{
"question": "Background music?",
"header": "Music",
"options": [
{ "label": "Inspired Ambient", "description": "Ambient, beautiful, advertising feel" },
{ "label": "Motivational Day", "description": "Background, commercial, uplifting" },
{ "label": "Upbeat Corporate", "description": "Upbeat, inspiring, corporate energy" },
{ "label": "No music", "description": "Voiceover only" }
],
"multiSelect": false
}]
}
Music files (royalty-free from Pixabay, bundled in skill):
# Copy selected track to project
cp "${SKILL_DIR}/music/inspired-ambient-141686.mp3" background-music.mp3
# OR
cp "${SKILL_DIR}/music/motivational-day-112790.mp3" background-music.mp3
# OR
cp "${SKILL_DIR}/music/the-upbeat-inspiring-corporate-142313.mp3" background-music.mp3
# Verify
ls -lah background-music.mp3 && file background-music.mp3
Mix audio:
ffmpeg -y -i voiceover-normalized.mp3 -i background-music.mp3 \
-filter_complex "[1:a]volume=0.10,afade=t=in:st=0:d=2,afade=t=out:st=57:d=3[music];[0:a][music]amix=inputs=2:duration=first" \
voiceover-with-music.mp3
Render video:
npx remotion render MainPromo out/promo-hq.mp4 --image-format png --crf 1
Combine video + audio:
ffmpeg -y -i out/promo-hq.mp4 -i voiceover-with-music.mp3 \
-c:v copy -map 0:v:0 -map 1:a:0 \
out/promo-final.mp4
When user gives feedback, common fixes:
| Issue | Fix |
|---|---|
| Voiceover overlapping | Shorten text or increase gaps, regenerate, verify with Whisper |
| Voice doesn't match screen | Re-read scene content, match script to visuals |
| Voice too fast | Add pauses, reduce text density |
| Elements too close to edge | Add 60-100px padding |
| Fonts too small | Increase 20-30% |
| Animations feel stiff | Adjust spring damping/mass, add easing |
| Transitions too abrupt | Add fade overlaps, smooth scale changes |
| Blank frames at end | Extend closing scene duration |