remotion-narrated-video-essay
Skill50 starsChanged 9 months agoMITView on GitHub
Edit narration-led Remotion video essays using talking-head footage, overlays, selective B-roll, comic callouts, and still-frame visual QA. Use for personal reflective essays; not for a generic slide deck or a final render without approval.
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Keep the talking-head shot as the default visual.
- Distinctive: line 13
Use full-screen material sparingly: reserve it for a visually rich event or a sustained screen capture that needs attention.
- Distinctive: line 15
If cleaning a recorded talk, remove only clear filler, dead air, or repeated explanation at sentence boundaries.
- Distinctive: line 16
Never alter the camera original.
- Distinctive: line 20
Before generating narration, audit long lists, parallel clauses, comparisons, and closing triads for phrases that the voice may run …
- Very specific: line 22
Do not assume commas or periods created an audible pause.
- Distinctive: line 28
Keep overlays clear of the eyes, face, and important gestures.
- Distinctive: line 29
Remove redundant eyebrow labels and tiny descriptive captions.
- Distinctive: line 36
Use comic bubbles only for short self-aware observations.
- Distinctive: line 39
Treat bubble placement as shot-specific.
- Distinctive: line 43
Do not final-render until the user approves it.
- Distinctive: line 45
Check that text is readable, no card or bubble touches the face, screen captures show only relevant content, and all media matches the …
- Distinctive: line 46
Run the project type check or lint.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Remotion Narrated Video Essay
Build a polished video around the recorded narration while preserving the speaker's pace and point of view.
Editorial shape
- Keep the talking-head shot as the default visual. Prefer contextual media as an overlay rather than cutting away repeatedly.
- Use full-screen material sparingly: reserve it for a visually rich event or a sustained screen capture that needs attention.
- Match each overlay to the actual speaking beat. When narration is shortened, derive every B-roll cue from the same original-to-edited timeline mapping rather than shifting timings by guesswork.
- If cleaning a recorded talk, remove only clear filler, dead air, or repeated explanation at sentence boundaries. Preserve natural breaths and any cut that would create a visible pose or gaze jump.
- Never alter the camera original. Create a separately named proxy or edited narration track.
Narration phrasing and timing
- Before generating narration, audit long lists, parallel clauses, comparisons, and closing triads for phrases that the voice may run together. When the user limits the edit by priority, change only the approved priority tier and preserve every word; punctuation-only approval does not authorize rewriting.
- Regenerate only the affected narration IDs, use versioned filenames, and keep unrelated visuals and audio unchanged except for timing adjustments required by the new duration.
- Do not assume commas or periods created an audible pause. Check the selected WAV with word timestamps and
silencedetect, and record the pause at every edited high-priority boundary. - Base scene safety on the final spoken-word end rather than the container duration. Leave at least 0.5 seconds before the next narration, music entry, transition overlap, or scene end. For a music cue triggered by a mention, measure from the end of the mentioned phrase.
Layout and visual hierarchy
- Inspect the speaker frame before placing an overlay. Put cards opposite the face and change side when the speaker's position changes later in the recording.
- Keep overlays clear of the eyes, face, and important gestures. Use a consistent card size, corner treatment, and restrained shadow.
- Remove redundant eyebrow labels and tiny descriptive captions. A card should usually contain one large title and one legible explanatory line or two.
- Match card colors to the camera's actual palette rather than imposing a disconnected theme. Preserve enough contrast for small-screen viewing.
- For a tall analytics or dashboard screenshot, use a full-screen still and animate a slow, continuous vertical scroll across the useful content. Do not add browser chrome, ads, or unrelated page areas.
- Clearly distinguish real footage from reconstructed or AI-generated interface concepts. Do not imply that a concept visual is a real product capture.
Optional comic callouts
- Use comic bubbles only for short self-aware observations; avoid emotional memories, family scenes, and the closing reflection.
- Make the text large, centered, and comfortably fill the bubble. Use a locally bundled, Korean-capable display font so the final render is deterministic.
- Aim the tail at the speaker's face. The tail should be a naturally joined curved shape, with no visible base seam, and it should share the bubble's shadow direction.
- Treat bubble placement as shot-specific. Render a still for each bubble and adjust its tail, scale, and side until it reads as connected to the speaker rather than floating on the wall.
Review before final render
- Do not final-render until the user approves it.
- Render stills for the opening, every visual treatment, each overlay side change, every comic bubble, the start/end of any scrolling screen capture, and the ending.
- Check that text is readable, no card or bubble touches the face, screen captures show only relevant content, and all media matches the narration's claim.
- Run the project type check or lint. If it is blocked by unrelated existing code, report that precisely without modifying unrelated files.
- For a multi-part series, render and decode-check every part before assembling the full video. Then verify the merged duration, video and audio streams, the joins between parts, and the final frame. Do not substitute a low-resolution review render when the user asked for direct inspection or final output.
In this repository21 other files it gives its agents.
- ai4pkm-helperSkill
- create-vlog-scriptSkill
- docx-to-markdownSkill
- epub-to-markdownSkill
- gemini-image-skillSkill
- gobi-onboardingSkill
- interactive-writing-assistantSkill
- markdown-slidesSkill
- markdown-videoSkill
- obsidian-canvasSkill
- obsidian-cliSkill
- obsidian-linksSkill
- obsidian-markdown-structureSkill
- obsidian-mermaidSkill
- obsidian-yaml-frontmatterSkill
- remotion-vlogSkill
- video-add-chaptersSkill
- video-cleaningSkill
- video-full-processSkill
- voice-clone-skillSkill
- youtube-transcript-summarizerSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

