The argument in one line.
A YouTube creator replaced his editor with a multi-skill Claude Code pipeline that transcribes, plans cuts, generates motion graphics, and re-checks its own work, while the human only approves at four fixed gates.
Read if. Skip if.
- You publish long-form video on a repeat cadence and post-production is the bottleneck between recording and shipping.
- You already direct Claude Code with custom skills or subagents and want a concrete blueprint for a longer multi-stage pipeline with real checkpoints.
- You're building (or want to build) an internal tool — like a b-roll library or a publishing calendar — that an agent can query and write to automatically.
- You want to see what 'human-in-the-loop' actually looks like in a working system, not just as a talking point.
- You're looking for a consumer app or plugin to install — this is a custom-engineered pipeline built over months, not a product.
- You don't use a coding agent at all — the entire system assumes a terminal-based agent orchestrating scripts, not a GUI editor with AI features bolted on.
The full version, fast.
Brian Casel now edits every video on his channel with a custom Claude Code pipeline instead of a human editor. A wrapper skill orchestrates sub-skills for FFmpeg cutting, ElevenLabs transcription, and branded motion-graphics generation, plus two custom apps: Tubery, a searchable b-roll library, and a publishing calendar. The process runs in three phases — prep, produce, export — and re-transcribes the edited footage after cutting specifically so Claude can catch its own mistakes (duplicated lines, cut-off b-roll, off-center picture-in-picture framing). Casel only steps in at four gates: approving the cut plan, reviewing the first-pass edit, approving fixes, and never touching the final stitch. A run that used to take over a week now finishes same-day, with an hour or two of unattended agent work in the middle he can spend on other tasks.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · Intro
States the problem: editing used to take over a week even with hired editors; a year of failed AI tools; as of a month ago, Claude Code edits every video on the channel, including this one.

02 · My AI video editing system
Maps the full system: raw footage in, Claude Code orchestrates a 'video editing' wrapper skill over 'video use' (FFmpeg) and 'create visuals' (Hyperframes), ElevenLabs for transcription, Tubery for b-roll. Shows the three-phase Prep/Produce/Export diagram with approval gates.

03 · What raw footage looks like
Shows raw scripted teleprompter takes with multiple retries, and unscripted screen-recording segments where he riffs and rambles — the messy input the agent has to cut down.

04 · Kicking off Claude Code
Walks his content repo and skill folder structure, explains why he's using Claude Fable 5 for this run (previously Opus 4.8), and kicks off Phase 1 (prep: transcribe, analyze cuts, propose b-roll and new visuals) with a one-line hint about the video's topic.

05 · Approving the edit plan
Reviews REVIEW.md and each segment's transcript.md with cut/b-roll/visual tags; approves the default color grade; drops in new b-roll clips and requests a teaser clip; gives the go-ahead into Phase 2 (first-pass edit + motion graphics), which will run unattended for 1-2 hours.

06 · Reviewing the edited segments
Returns after ~2 hours; reviews finished segments and generated motion graphics; requests fixes via screenshot + text (graphic overlap) and via '[FIX]' tags written into transcript.md (duplicate phrase, cut-off b-roll, off-center picture-in-picture framing that also gets written into the skill as a permanent check); approves final stitch.

07 · Final export and publishing
Fixes complete after another ~1 hour; final 4K master exported; automated cleanup renames and backs up the file to Dropbox, wipes working files, pushes new b-roll into Tubery, registers the video in the Sparkdrop publishing calendar, and auto-writes the YouTube description plus timestamped chapter list.

08 · The AI-native approach
Closing framing: the point isn't the specific tool but the approach — rebuilding a core business process around AI while deliberately designing the moments where human approval still matters.
Lines worth screenshotting.
- Claude Code now edits every video on this channel end to end, cutting turnaround from over a week to same-day.
- The pipeline re-transcribes the footage a second time after editing specifically so the agent can catch its own mistakes, like a repeated phrase or a b-roll clip cut off too early.
- Motion graphics are generated one at a time in a queue, not in parallel, because running the graphics engine on multiple clips simultaneously was more error-prone in testing.
- A full first-pass edit — cuts, b-roll placement, and motion-graphics generation — runs unattended for one to two hours before the creator reviews anything.
- Human approval happens at exactly four gates: the cut plan, the first-pass edit, the fix pass, and never again once the final stitch starts.
- Feedback is given by writing plain notes directly into a timestamped transcript file, including a shorthand '[FIX]' tag the agent expands into a full diagnosis on its own.
- A custom-built b-roll library app stores hundreds of past clips with AI-written descriptions, so new scripts can automatically reuse existing footage instead of resourcing it from scratch.
- A recurring defect — the presenter's head not centering in the picture-in-picture frame — got fixed once, then written directly into the skill's own instructions as a permanent verification step so it never has to be flagged again.
- Camera color grading and audio-sync correction between a separate microphone and camera feed are handled automatically with zero per-video input from the creator.
- The final cleanup step auto-generates the YouTube chapter list with real timestamps derived from the finished cut, replacing manual scrubbing through the timeline.
- The entire system runs on Claude Code, a general-purpose coding agent, not a video-specific AI product — every editing rule lives in custom-written skill instructions layered on top of it.
- The creator reports a same-video comparison: total review time across all human checkpoints is roughly 20-25 minutes, versus multiple hours of unattended agent work in between.
Four checkpoints turn a long agent run into something you can actually trust.
The value isn't that an AI edits video — it's a pipeline broken into fixed phases with named approval gates, so hours of unattended agent work never run further than the point you last signed off on.
- Editing used to take over a week even with hired editors; a wrapper skill over an FFmpeg-driving engine now takes it end-to-end same-day.
- For well over a year, none of the off-the-shelf AI editing tools moved the one metric that mattered — total time from raw footage to published video.
- The system runs on Claude Code, a general-purpose coding agent, not a dedicated video product — the editing logic lives entirely in custom skill instructions layered on top.
- Re-transcribing the footage a second time after cutting is a deliberate, paid-for step that lets the agent catch its own mistakes instead of the human catching them.
- Every unscripted screen-recording segment gets far more aggressive cutting latitude than scripted camera segments, because rambling needs a heavier edit than a scripted take.
- Running multiple motion-graphics generations in parallel was more error-prone in testing, so the skill was redesigned to queue them one at a time.
- A one-line topic hint is enough to kick off the entire prep phase — the heavy lifting is in the skill instructions, not the prompt.
- Feedback is written as plain notes directly into a timestamped transcript file, including a lightweight '[FIX]' shorthand tag the agent expands into a full diagnosis on its own.
- A searchable b-roll library with AI-written descriptions lets new scripts automatically reuse hundreds of past clips instead of resourcing new footage for every mention.
- A recurring visual defect gets fixed once, then the fix is written back into the skill's own instructions as a permanent check — the system accumulates institutional memory instead of repeating the same correction on every video.
- Total human review time across every checkpoint is roughly 20-25 minutes on a ~19-minute finished video, versus multiple hours of unattended agent work in between.
- Automating the tedious final steps — renaming files, backing up to Dropbox, wiping working folders, writing YouTube chapters with real timestamps — removes dozens of small manual tasks with one command.
Terms worth knowing.
- Skill (Claude Code)
- A packaged, reusable set of instructions and scripts that gives a coding agent a repeatable specialized workflow — here, video editing, b-roll placement, and motion-graphics generation are each their own skill.
- Video-use skill
- The underlying skill that operates FFmpeg directly to perform cuts, stitching, and export — a lower-level engine that a higher-level 'video editing' skill wraps and directs.
- Hyperframes
- The motion-graphics generation engine used by this pipeline; a separate 'create visuals' skill wraps it to apply consistent branding and layout templates.
- Tubery
- A custom-built web app that stores and indexes a creator's b-roll clip library with searchable, AI-written descriptions, so an agent can find and reuse relevant past footage.
- Approval gate
- A fixed checkpoint in an agent pipeline where the automated process stops and waits for a human to review and approve before continuing to the next phase.
Things they pointed at.
Lines you could clip.
“Back when I started making videos on my YouTube channel, it used to take me well over a week to get one of my videos edited and ready to publish.”
“That's how the Claude Code Agent is able to self verify its own editing work.”
“When I have it creating multiple motion graphics at the same time... it's more error prone when it's doing all that processing all at the same time. So I designed the skill to work in a sequence and put them into a queue.”
“The issues here were so minor and I'm using Claude Fable on this so I have a pretty high level of trust that it's gonna be good to go.”
“I took one of the most important and most time-consuming processes in my business and I retooled it from the ground up using AI. And then I designed the specific moments where I, as the human in the loop, still need to give my input.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
Brian Casel spent over a year testing AI editing tools that never moved the one metric he cared about: time from recorded footage to published video. This is the system that finally did — a set of custom Claude Code skills that now edit every video on his channel, while he steps in at exactly four checkpoints to approve, redirect, or fix.
Named ideas worth stealing.
Three-Phase Edit Pipeline (Prep / Produce / Export)
- Prep — transcribe, plan cuts, propose b-roll/visuals (renders nothing)
- Produce — cut, composite, place b-roll/visuals, self-verify every cut
- Export — stitch all segments, export one 4K master
The full pipeline is three sequential phases, each ending at a human approval gate, running from raw footage to a finished, published video.
AI Video-Editing System Architecture
- Raw footage (camera + screen recordings)
- Claude Code (orchestrator)
- video-editing skill (wrapper) -> video-use skill -> FFmpeg
- create-visual skill (wrapper) -> hyperframes engine (motion graphics)
- ElevenLabs (transcription)
- Tubery (b-roll library app)
A layered skill architecture: thin creator-specific wrapper skills sit on top of general-purpose engine skills (FFmpeg for cuts, Hyperframes for graphics), with a custom app as the searchable memory layer for reusable assets.
How they asked for the click.
“It's completely free over at buildermethods.com/workshop.”
Mid-roll self-ad read while Phase 2 is running unattended, framed as directly related to the video's topic (going AI-native); repeated as the closing CTA alongside a subscribe ask.








































































