← ClaudeAtlas

tiny-video-editorlisted

Use when the user wants to cut, trim, tighten or re-order video from raw footage — draft the edit as a YAML cutlist, hand them a browser editor to fine-tune the in/out points by eye and ear, then render the final file with ffmpeg. Triggers on "edit this video", "cut this footage", "trim the silence", "make a demo video", "assemble a cut", "tighten this recording".
sponno/tiny-video-editor · ★ 1 · Code & Development · score 72
Install: claude install-skill sponno/tiny-video-editor
# Tiny Video Editor Editing video is one job split between two parties. You are good at deciding **what to keep** — you can read a transcript, spot dead air, and sequence a story. You are bad at deciding **exactly which frame** a cut lands on, because you cannot see or hear the result. The human is the opposite. So: you draft, they fine-tune, you render. The edit lives in a YAML file. Nothing ever modifies the footage. ## The four steps 1. **Survey** the footage and draft `cutlist.yaml` 2. **Hand over** the editor so the human tunes the cuts 3. **Wait** — do not proceed while they are editing 4. **Render** with `render.py` once they say they're done Do not skip step 2 by rendering straight from your draft. Your in/out points are guesses derived from a waveform and a transcript; the human's take half a minute to fix and will be better. --- ## Step 1 — Survey and draft ### Check the tools `ffmpeg` and `ffprobe` are required. If missing, say so and stop: `brew install ffmpeg` (macOS) or the platform equivalent. ### Probe every source ```bash ffprobe -v error -show_entries stream=codec_type,width,height,r_frame_rate \ -show_entries format=duration -of default=nw=1 FOOTAGE.mp4 ``` Note the **fps** (the cutlist needs it), the resolution, and whether there is an audio stream. Watch for two things that will bite later: - **Cover art.** Some `.m4v`/`.mp4` files carry an `mjpeg` "attached_pic" stream alongside the real video. `render.py` handles it, but if you write