Edit any video by conversation. Transcribe, cut, color grade, generate overlay animations, burn subtitles — for talking heads, montages, tutorials, travel, interviews. No presets, no menus. Ask questions, confirm the plan, execute, iterate, persist. Production-correctness rules are hard; everything else is artistic freedom.
SkillScore78Maintained
Automatic
◆Marketing & Content pack
Last verified 8/20/2026
What it changes
Passed 16 of 21 test cases with the skill, and 13 of 21 without it.
Without skill61%
With skill78%
Checks it passed that the model alone missed
Pads speech cut boundaries within a 30 to 200 millisecond window.
Snaps cut edges to word boundaries from the word-level transcript.
Applies a 30 millisecond audio fade-out at the end of each segment.
and 4 more in the full report
5 fixed13 passed either way4 still failing1 broke
Pass-rate lift
+17 pp
Tokens
+201%
Agent turns
0%
Response time
-50%
Model gemini-3.6-flashMeasured 8/20/2026v118 of 23 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
I need to store project session logs, take selections, and edit state across multiple editing passes on a video project. Where should session notes and state tracking files be saved relative to the project files and skill files?
What was checked, without and with the skill
Checked
Without skill
With skill
Saves session project notes inside the edit directory within the user footage directory.
Missed
Passed
case-10 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md317 linessingle file
Video Use
Principle
LLM reasons from raw transcript + on-demand visuals. The only derived artifact that earns its keep is a packed phrase-level transcript (takes_packed.md). Everything else — filler tagging, retake detection, shot classification, emphasis scoring — you derive at decision time.
Audio is primary, visuals follow. Cut candidates come from speech boundaries and silence gaps. Drill into visuals only at decision points.
Ask → confirm → execute → iterate → persist. Never touch the cut until the user has confirmed the strategy in plain English.
Generalize. Do not assume what kind of video this is. Look at the material, ask the user, then edit.
Artistic freedom is the default. Every specific value, preset, font, color, duration, pitch structure, and technique in this document is a worked example from one proven video — not a mandate. Read them to understand what's possible and why each worked. Then make your own taste calls based on what the material actually is and what the user actually wants. The only things you MUST do are in the Hard Rules section below. Everything else is yours.
Invent freely. If the material calls for a technique not described here — split-screen, picture-in-picture, lower-third identity cards, reaction cuts, speed ramps, freeze frames, crossfades, match cuts, L-cuts, J-cuts, speed ramps over breath, whatever — build it. The helpers are ffmpeg and PIL. They can do anything the format supports. Do not wait for permission.
Verify your own output before showing it to the user. If you wouldn't ship it, don't present it.
Hard Rules (production correctness — non-negotiable)
These are the things where deviation produces silent failures or broken output. They are not taste, they are correctness. Memorize them.
Subtitles are applied LAST in the filter chain, after every overlay. Otherwise overlays hide captions. Silent failure.
Per-segment extract → lossless -c copy concat, not single-pass filtergraph. Otherwise you double-encode every segment when overlays are added.
30ms audio fades at every segment boundary (afade=t=in:st=0:d=0.03,afade=t=out:st={dur-0.03}:d=0.03). Otherwise audible pops at every cut.
Overlays use setpts=PTS-STARTPTS+T/TB to shift the overlay's frame 0 to its window start. Otherwise you see the middle of the animation during the overlay window.
Never cut inside a word. Snap every cut edge to a word boundary from the Scribe transcript.
Pad every cut edge. Working window: 30–200ms. Scribe timestamps drift 50–100ms — padding absorbs the drift. Tighter for fast-paced, looser for cinematic.
Word-level verbatim ASR only. Never SRT/phrase mode (loses sub-second gap data). Never normalized fillers (loses editorial signal).
Cache transcripts per source. Never re-transcribe unless the source file itself changed.
Parallel sub-agents for multiple animations. Never sequential. Spawn N at once via the Agent tool; total wall time ≈ slowest one.
Strategy confirmation before execution. Never touch the cut until the user has approved the plain-English plan.
All session outputs in <videos_dir>/edit/. Never write inside the video-use/ project directory.
Everything else in this document is a worked example. Deviate whenever the material calls for it.
Directory layout
The skill lives in video-use/. User footage lives wherever they put it. All session outputs go into <videos_dir>/edit/.
AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.