remotion-vlog Checked
Installation
Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.
Install the "remotion-vlog" skill by following the instructions at https://skill123.me/install/remotion-vlog.
Run in your terminal — downloads and installs to ~/.claude/skills/.
curl -fsSL https://skill123.me/install/remotion-vlog.sh | bash
Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.
⬇ Download v1.0.0 · 7 KBNot live-tested yet — this skill is rated on static analysis only.
About this skill
Import and edit Pocket, phone, action-camera, or similar footage into a concise Remotion vlog with selective cuts, researched location context, titles, maps, transition captions, optional face-adjacent comic bubbles, licensed background music, beat-aware timing, preview approval, verified camera eject, and final render verification. Use for personal trip, family-day, garden, outing, and location-based vlog requests; do not use for generic presentation videos or pause-only cleanup.
Remotion Vlog
Turn raw outing footage into a short story that remains easy to inspect and revise as a Remotion project. Preserve the original media and treat the user's editorial exclusions as hard requirements.
Documentation
Import and edit Pocket, phone, action-camera, or similar footage into a concise Remotion vlog with selective cuts, researched location context, titles, maps, transition captions, optional face-adjacent comic bubbles, licensed background music, beat-aware timing, preview approval, verified camera eject, and final render verification. Use for personal trip, family-day, garden, outing, and location-based vlog requests; do not use for generic presentation videos or pause-only cleanup.
Remotion Vlog
Turn raw outing footage into a short story that remains easy to inspect and revise as a Remotion project. Preserve the original media and treat the user's editorial exclusions as hard requirements.
Interpret the request
- Resolve the requested camera or mounted volume, date scope, output folder, title, people, place, and render gate from the user's messages. Treat “today” using the user's local timezone.
- Inspect files and metadata before choosing clips. Do not mix in footage outside the requested event merely because it is adjacent on disk.
- If the destination or event can be inferred confidently from the footage and request, proceed. Ask only when two materially different events remain plausible.
- Prefer an existing Remotion project in the requested output folder. Create a new one only when none exists.
- When available, load
remotion-best-practicesbefore editing Remotion code. Use a speech-cleaning workflow only when spoken content determines the cuts.
Protect the footage
- Never modify, rename, move, or delete camera originals.
- Put selected, trimmed, consistently encoded proxies under the Remotion project's
public/tree. Keep temporary transcripts and contact sheets outside the project unless the user asks to retain them. - Preserve unrelated user changes in an existing project.
- If the user wants to eject a camera or card, copy only the selected source originals when capacity allows, then verify every destination against its source with a byte comparison or checksum before saying it is safe to eject. If capacity only permits proxies, say explicitly that full originals were not preserved locally.
### Verified import and automatic eject
When the user asks to import footage and automatically eject the camera or card:
View full documentation
1. Resolve the exact date or event scope and choose a dedicated media-source/<event-date>/originals destination outside public/.
2. Check destination capacity before copying and leave enough free space for the edit. Prefer selected full-resolution originals plus relevant camera stills. Camera-generated LRF proxies are optional when verified local edit proxies already exist. If the full date set does not fit, state what will and will not be imported before proceeding.
3. Copy without changing the source files. Verify the destination file count and total bytes, then perform a byte comparison or SHA-256 comparison for every copied file.
4. Eject only after all requested copies pass verification. Target the resolved mounted volume explicitly, confirm the eject command succeeds, and confirm that the mount path is gone.
5. On a copy, capacity, or verification failure, keep the device mounted and report the exact blocker. Never describe proxy-only storage as a full original import.
Select scenes editorially
Keep scenes that contribute at least one of these:
- establish the destination, route, or atmosphere;
- reveal a visually distinct area or meaningful transition;
- contain a concise, authentic interaction;
- explain a place-specific fact;
- provide a satisfying opening or ending.
Remove or shorten scenes that are repetitive, unstable, accidental, private, or unrelated to the outing. Default to removing clothing changes or personal-preparation footage, random logistics, office/library/café planning, stray ethnicity references, and other conversation that interrupts the location story. Do not promote a throwaway complaint such as “too hot” into a comic bubble unless the user explicitly wants it.
For a talking-head opening, compare repeated greetings or takes and start from the take the user selected. Screen the visible lead-in for grooming, ear or nose touching, clothing or microphone adjustments, and other setup gestures; remove them when requested, but use a coherent phrase boundary or a cutaway when the gesture overlaps useful speech.
When dialogue drives the decision:
1. Transcribe candidate clips in the likely spoken language, with word timestamps when practical.
2. Search for the user's target phrases and inspect the neighboring sentence or visual beat.
3. Prefer removing one coherent shot or beat over cutting a single word and leaving an audible fragment.
4. Cross-check ambiguous transcription against representative frames or a stronger model before deleting valuable footage.
5. Treat detected pauses and filler words as cut candidates, not automatic deletions. Inspect both the spoken phrase boundary and the moving image at every internal join, preserve a natural pace around the final sentence, and keep enough audio handle or silence to avoid clipped consonants and clicks.
If the plan changes late in the day, keep the original story coherent and treat the alternate activity as a clearly titled epilogue or appendix when that creates a satisfying turn. A small opening bubble may tease an end twist without revealing it; the ending must still make sense to a viewer who ignores the hint.
For a short practical demonstration inside a vlog, derive the steps from visible actions rather than writing a generic tutorial. Align each step overlay to the action, retain only useful narration, and remove isolated trailing words or recognition artifacts with word-level timing or a brief audio fade while leaving the visual intact. Add a concise safety qualifier when the footage does not show every precaution.
Research the location
- Browse current official or primary sources for the address, scale, notable areas, history, hours, or admission when these facts improve the story.
- Use only a few facts that correspond to scenes actually present in the footage. Avoid turning a personal vlog into an information deck.
- Keep source URLs for the handoff and avoid unsupported claims.
For an opening location map, use an accurate map source such as OpenStreetMap. Show a visible location pin, place name, and concise address. Crop browser chrome and retain the required map attribution. Never substitute an AI-generated map for a real one.
Build the Remotion composition
Use 1920×1080 at 24 fps by default unless the footage or user specifies otherwise. Keep one ordered scene list as the timing source of truth.
Include only the elements the story needs:
- an opening title with the vlog title, location, and featured person when supplied;
- an early location map, usually overlaid for roughly four to six seconds without needlessly lengthening the edit;
- chapter or garden-area title cards at meaningful transitions;
- a short bottom caption at the start of every retained scene or transition;
- occasional comic dialogue bubbles for memorable lines;
- restrained crossfades or other transitions that match the footage.
When the user supplies a handwritten note or reference image as an insert, honor the requested corner and size, preserve its aspect ratio, and verify readability in a rendered still at normal viewing scale. Re-check that it does not cover the speaker's face and that chapter titles, captions, and other cards do not collide with it. Treat requested title and card positions as layout constraints rather than universal defaults.
When the user wants section titles distinguished without boxes, remove pills, panels, borders, and card shadows; use scale, weight, position, and a restrained text shadow instead. Match the opening title's type family and hierarchy, then verify the larger text remains inside the safe area on representative section stills.
Track each B-roll image and video by asset and timeline range. When the user asks to use footage only once, do not repeat the same visual at a later beat or chapter; one simultaneous foreground-plus-background treatment of a vertical clip counts as one editorial use. Prefer returning to the talking head or choosing a genuinely different source over recycling the same shot without intent.
If the user asks for a spoken farewell, retain the complete final sign-off and end on that shot. Do not append a silent title or end card after it unless the user req
Score breakdown
Assessment methodology
Version history
Imported from jykim/claude-obsidian-skills@main
