When should you use it?
- You record short talking-head or screen videos often and editing is the bottleneck
- Most edits are removing pauses, false starts and retakes
Not for: Stylized edits with music timing and b-roll; a human editor is still better
What do you need, and what do you get?
You need
- The raw recording
- A local transcription tool with word timestamps (the poster used whisper.cpp)
- ffmpeg and a coding agent to write and run the edit script
You get
- An edit list of keep and cut ranges, with reasons
- A rendered cut
- Check results: frames at each cut and audio levels
How does it work, step by step?
- Transcribe with timestampsRun local transcription so you get word-level times.
- Pick cuts from textUse our prompt to mark pauses, retakes and filler as cuts and keep the best take of each line.
- Render with known rulesWrite the gotchas you've hit (rotation, speed changes, audio fades at cuts) into a rules file the agent must follow.
- Verify the outputGrab a still at every edit point and check loudness before you trust the render.
The prompt
Our own prompt, inspired by u/ustype on r/automation and written to work in Claude Code and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Here is a transcript with word timestamps from a raw recording: {transcript}. Make an edit list for a tight cut: 1. Remove pauses longer than {pause_seconds} seconds, filler at the start of sentences, and false starts. 2. Where a line was said more than once, keep the cleanest complete take and say why. 3. Output keep-ranges as start and end times, with a one-line reason for each cut. 4. Follow these render rules: {rules_file} (for example: read display dimensions, add {fade_ms} ms audio fades at cuts). 5. After rendering, list the checks to run: a frame at every cut, total duration versus the edit list, and audio loudness. Show me the edit list before rendering.
Inspired by u/ustype on r/automation: Automating video editing from the transcript. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Phone video often has a rotation flag; read display dimensions or vertical clips get letterboxed.
- Add short audio fades at each cut, or every join will pop.
Our take
Most short business videos need the same edit: remove dead air, false starts and the retakes you did when you fumbled a line. That's a language problem more than a video one, which is why cutting from the transcript works well; the agent reads the text, keeps the best version of each sentence, and turns that into timestamps. The more valuable part of this post is what came after. The poster found that the real trouble was renders that finished without errors and still came out wrong, such as rotated phone footage letterboxed, speed changes that silently undid themselves, and audio popping at each cut. Writing those lessons into a rules file and checking frames and loudness after every render is the habit to copy, for video and for any automation that produces files. Our prompt produces an edit list with reasons before anything renders, so you can approve it. In our dry run on a made-up 2-minute transcript with timestamps, it marked 11 cuts (pauses over 0.8 seconds, two full retakes, one 'um, let me start over'), kept the cleaner second take both times, and listed the frame and audio checks to run after rendering.
Where the time goes back: Hours of trimming pauses and retakes become a reviewed edit list and an automatic render.
FAQ
Why do the cutting from the transcript?
What went wrong most often?
Source and credit
Inspired by u/ustype on r/automation. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Automating video editing from the transcript
- Creator
- u/ustype on r/automation
- Published on
- Original date
- Oct 15, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 20, 2026: passed. Dry-run tested by our AI test agent on sample input. Produced a reviewable edit list and the verification checks.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.