explainer-video-guide▌
inferen-sh/skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Complete guide for scripting, producing, and assembling explainer videos via inference.sh CLI.
- ›Provides three script formulas (Problem-Agitate-Solve, Before-After-Bridge, Feature Spotlight) with timing breakdowns, word counts, and pacing rules for 30–120 second videos
- ›Covers scene generation via video AI models, voiceover production with TTS, music ducking, and caption integration through a multi-step assembly pipeline
- ›Includes practical tables for pacing (120–170 wpm by content type
Explainer Video Guide
Create explainer videos from script to final cut via inference.sh CLI.
Quick Start
Requires inference.sh CLI (
infsh). Install instructions
infsh login
# Generate a scene for an explainer
infsh app run google/veo-3-1-fast --input '{
"prompt": "Clean motion graphics style animation, abstract data flowing between connected nodes, blue and white color scheme, professional corporate aesthetic, smooth transitions"
}'
Script Formulas
Problem-Agitate-Solve (PAS) — 60 seconds
| Section | Duration | Content | Word Count |
|---|---|---|---|
| Problem | 10s | State the pain point the viewer has | ~25 words |
| Agitate | 10s | Show why it's worse than they think | ~25 words |
| Solution | 15s | Introduce your product/idea | ~35 words |
| How It Works | 20s | Show 3 key steps or features | ~50 words |
| CTA | 5s | One clear next action | ~12 words |
Before-After-Bridge (BAB) — 90 seconds
| Section | Duration | Content |
|---|---|---|
| Before | 15s | Show the current frustrating state |
| After | 15s | Show the ideal outcome |
| Bridge | 40s | Explain how your product gets them there |
| Social Proof | 10s | Quick stat or testimonial |
| CTA | 10s | Clear next step |
Feature Spotlight — 30 seconds (social)
| Section | Duration | Content |
|---|---|---|
| Hook | 3s | Surprising fact or question |
| Feature | 15s | Show one feature solving one problem |
| Result | 7s | The outcome/benefit |
| CTA | 5s | Try it / Learn more |
Pacing Rules
| Content Type | Words Per Minute | Notes |
|---|---|---|
| Standard narration | 150 wpm | Conversational pace |
| Complex/technical | 120 wpm | Allow processing time |
| Energetic/social | 170 wpm | Faster for short-form |
| Children's content | 100 wpm | Clear and slow |
Key rule: 1 scene per key message. Don't pack multiple ideas into one visual.
Scene Duration Guidelines
- Establishing shot: 3-5 seconds
- Feature demonstration: 5-8 seconds
- Text/stat on screen: 3-4 seconds (must be readable)
- Transition: 0.5-1 second
- CTA screen: 3-5 seconds
Visual Production
Scene Types
# Product in context
infsh app run google/veo-3-1-fast --input '{
"prompt": "Clean product demonstration video, hands typing on a laptop showing a dashboard interface, bright modern office, soft natural lighting, professional"
}'
# Abstract concept visualization
infsh app run bytedance/seedance-1-5-pro --input '{
"prompt": "Abstract motion graphics, colorful data streams connecting floating geometric shapes, smooth fluid animation, dark background with glowing elements, tech aesthetic"
}'
# Lifestyle/outcome shot
infsh app run google/veo-3-1-fast --input '{
"prompt": "Happy person relaxing on couch with laptop, smiling at screen, bright airy living room, warm afternoon light, satisfied customer feeling, lifestyle commercial style"
}'
# Before/after comparison
infsh app run falai/flux-dev-lora --input '{
"prompt": "Split screen comparison, left side cluttered messy desk with papers and stress, right side clean organized minimalist workspace, dramatic difference, clean design"
}'
Image-to-Video for Scenes
# Generate a still frame first
infsh app run falai/flux-dev-lora --input '{
"prompt": "Professional workspace with glowing holographic interface, futuristic but clean, blue accent lighting"
}'
# Animate it
infsh app run falai/wan-2-5-i2v --input '{
"prompt": "Gentle camera push in, holographic elements subtly floating and rotating, soft ambient light shifts",
"image": "path/to/workspace-still.png"
}'
Voiceover Production
Script Writing Tips
- Short sentences. Max 15 words per sentence.
- Active voice. "You can track your data" not "Your data can be tracked."
- Conversational tone. Read it aloud — if it sounds stiff, rewrite.
- One idea per sentence. One sentence per visual beat.
Generating Voiceover
# Professional narration with Dia TTS
infsh app run falai/dia-tts --input '{
"prompt": "[S1] Tired of spending hours on reports that nobody reads? There is a better way. Meet DataFlow. It turns your raw data into visual stories... in seconds. Just connect your source, pick a template, and share. Try DataFlow free today."
}'
Pacing Control in TTS
| Technique | Effect | Example |
|---|---|---|
Period . |
Medium pause | "This changes everything. Here's how." |
Ellipsis ... |
Long pause (dramatic) | "And the result... was incredible." |
Comma , |
Short pause | "Fast, simple, powerful." |
Exclamation ! |
Emphasis/energy | "Start building today!" |
Question ? |
Rising intonation | "What if there was a better way?" |
Music & Audio
Background Music Guidelines
- Volume: 20-30% under narration (duck 6-12dB when voice plays)
- Style: match the brand tone (corporate = ambient electronic, startup = upbeat indie)
- Structure: intro swell (first 3s) -> subtle loop under narration -> swell at CTA
- No vocals: instrumental only under narration
# Generate background music
infsh app run <music-gen-app> --input '{
"prompt": "upbeat corporate background music, modern electronic, 90 BPM, positive and professional, no vocals, suitable for product explainer video"
}'
Assembly Pipeline
Full Production Workflow
# 1. Generate voiceover
infsh app run falai/dia-tts --input '{
"prompt": "[S1] Your script here..."
}'
# 2. Generate scene visuals (in parallel)
infsh app run google/veo-3-1-fast --input '{"prompt": "scene 1 description"}' --no-wait
infsh app run google/veo-3-1-fast --input '{"prompt": "scene 2 description"}' --no-wait
infsh app run google/veo-3-1-fast --input '{"prompt": "scene 3 description"}' --no-wait
# 3. Merge scenes into sequence
infsh app run infsh/media-merger --input '{
"media": ["scene1.mp4", "scene2.mp4", "scene3.mp4"]
}'
# 4. Add voiceover to video
infsh app run infsh/video-audio-merger --input '{
"video": "merged-scenes.mp4",
"audio": "voiceover.mp3"
}'
# 5. Add captions
infsh app run infsh/caption-videos --input '{
"video": "final-with-audio.mp4",
"caption_file": "captions.srt"
}'
Video Length by Format
| Format | Length | Platform |
|---|---|---|
| Social teaser | 15-30s | TikTok, Instagram Reels, YouTube Shorts |
| Product demo | 60-90s | Website, landing page |
| Feature explainer | 90-120s | YouTube, email |
| Tutorial/walkthrough | 2-5min | YouTube, help center |
| Investor pitch video | 2-3min | Pitch deck supplement |
Transition Types
| Transition | When to Use | Effect |
|---|---|---|
| Cut | Default between related scenes | Clean, professional |
| Dissolve/Crossfade | Time passing, mood shift | Soft, contemplative |
| Wipe | New topic or section | Clear separation |
| Zoom/Push | Drilling into detail | Focus attention |
| Match cut | Visual similarity between scenes | Clever, memorable |
Common Mistakes
| Mistake | Problem | Fix |
|---|---|---|
| Script too wordy | Voiceover rushed, viewer overwhelmed | Cut to 150 wpm max |
| No hook in first 3s | Viewers leave immediately | Start with the problem or surprising stat |
| Visuals lag narration | Confusing disconnect | Visuals should match or slightly precede words |
| Background music too loud | Can't hear narration | Duck music 6-12dB under voice |
| No captions | 85% of social video watched silent | Always add captions |
| Too many ideas | Viewer retains nothing | One core message per video |
Related Skills
npx skills add inference-sh/skills@ai-video-generation
npx skills add inference-sh/skills@video-prompting-guide
npx skills add inference-sh/skills@text-to-speech
npx skills add inference-sh/skills@prompt-engineering
Browse all apps: infsh app list
How to use explainer-video-guide on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add explainer-video-guide
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches explainer-video-guide from GitHub repository inferen-sh/skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate explainer-video-guide. Access the skill through slash commands (e.g., /explainer-video-guide) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★54 reviews- ★★★★★Mia Gupta· Dec 28, 2024
explainer-video-guide is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Shikha Mishra· Dec 24, 2024
Useful defaults in explainer-video-guide — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ganesh Mohane· Dec 20, 2024
explainer-video-guide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Henry Malhotra· Dec 20, 2024
I recommend explainer-video-guide for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Benjamin Singh· Dec 20, 2024
Solid pick for teams standardizing on skills: explainer-video-guide is focused, and the summary matches what you get after install.
- ★★★★★Benjamin Shah· Dec 16, 2024
We added explainer-video-guide from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Henry Jain· Dec 8, 2024
explainer-video-guide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Henry Bansal· Nov 23, 2024
explainer-video-guide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Mia Nasser· Nov 19, 2024
explainer-video-guide reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Yash Thakker· Nov 15, 2024
explainer-video-guide has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 54