AI-Native Video Editing with Claude Code

From raw footage to publish-ready the same day — skills, FFmpeg, Hyperframes, B-roll library, and designed human approval gates

← AI Agents  ·  AI  ·  Tech  ·  HyperFrames  ·  Claude Skills

Source / credit: YouTube · watch?v=GlvH_waCx8w · hosted copy: static2.mikesblog.com/video-editing.mp4

Creator points to a free AI-native workshop at buildermethods.com/workshop. (Transcript says “Cloud Code” throughout — that is Claude Code.)

Actionable Summary: How to Do This

Outcome: record in the morning → post-production done the same day. Metric that matters: time from recorded footage to publish-ready (not “did an AI tool touch the timeline once”).

Mindset: this is not a single plugin. It is an AI-native rebuild of the whole editing process: custom skills, verification loops, and explicit human gates — same spirit as loops not prompts and Step 2–3 adoption (self-verify, multi-agent work, you review diffs / segments not every keystroke).

1. Stack (components)

Piece Role
Claude Code Orchestrator — runs the whole edit as skills, not a NLE UI
Video Editing skill End-to-end wrapper: phases, review gates, cleanup, publish prep
Video Use skill FFmpeg engine — cuts, stitch, grade, A/V alignment
Create Visuals + Hyperframes New motion graphics / branded B-roll (HyperFrames guide)
ElevenLabs Transcription; re-transcribe after edits for self-verify (costs more, worth it)
Tubery / Tubri Custom B-roll library + API — index, search, place, save new clips back
SparkDrop (optional) Publishing calendar / multi-channel content plan registration
Dropbox + local repo Raw backup off-machine; working 4K stays out of GitHub

2. How to shoot so the agent can edit

  • Number segments in the order they appear in the final video (1, 2, 3…)
  • Two segment types: (A) camera + teleprompter / multi-take scripted lines, (B) screen + camera riff (two feeds)
  • Back up raw files to Dropbox first, then copy into a local content repo not pushed to Git (4K is huge)
  • Good takes are “in there somewhere” — the agent (or a human editor) picks; multi-take is expected

3. Three phases + human gates

Phase 1 — Prep (~10–12 min)

Transcribe each segment · plan cuts / dead air · B-roll from library or “generate new” · color grade options · A/V sync plan · write review.md + per-segment plans. No final edit yet.

You: skim grade options, read planned transcripts, green-light Phase 2.

Phase 2 — First-pass edit (1–2 hrs)

Cuts · place B-roll · generate motion graphics (queued for branding consistency) · recut per feedback · re-transcribe for self-check. Can spawn background work — good time for thumbnails in Photoshop.

You: review each segment via transcript.md; mark [fix] notes; approve when clean.

Phase 3 — Stitch + cleanup

Assemble full video · export · backup final + raw · delete working 4K junk · push new B-roll to Tubery · register SparkDrop · auto YouTube chapters + description.

You: upload/schedule on YouTube (long-form often still manual).

4. Design the human interface as Markdown

  • review.md — Phase 1 checklist deliverable
  • Per-segment folders — working JSON for the agent; you mostly ignore internals
  • transcript.mdsource of truth for what is in the edit and for feedback
  • Lazy pattern: type [fix] (or short notes) in the transcript; agent recuts
  • When a class of bugs repeats: tell the agent to fix and bake a verification step into the skill so it never happens again

5. Self-verification (why re-transcribe)

After programmatic cuts, re-send audio/video to ElevenLabs and re-read the transcript. That catches double phrases, leftover dead air, and broken sentences the model introduced while stitching takes. Extra cost; higher trust — same idea as verification loops / end-to-end agent checks.

6. Motion graphics pipeline

  1. Skill marks script opportunities for new visuals (not only library B-roll)
  2. Hyperframes (or similar) as the render engine
  3. Create Visuals wrapper enforces brand, templates, sequence/queue so graphics stay consistent
  4. New assets go back into Tubery for reuse next video

7. Minimum viable system you can build

8. What not to expect day one

  • Perfect taste without your gates — the video still needs your pacing/brand judgment
  • Zero iteration — he improved the skill on every run; bake fixes back into the skill
  • Free transcription forever if you re-transcribe for verify — budget for it
  • Models: he ran successfully on Opus 4.8; used Fable 5 when available for smoothness — the skill quality matters more than max model for every run

Related Guides

HyperFrames

Video as code for motion graphics agents call in this pipeline.

Read →

Claude Skills

How to package reusable skills like Video Editing / Create Visuals.

Read →

Loops, Not Prompts

Orchestrate multi-step agent work instead of one-shot prompts.

Read →

Stop Babysitting Agents

Verification loops and background routines while Phase 2 runs.

Read →

Agentic Setup Checklist

Harness, worksheets, self-healing docs — same design discipline.

Open checklist →

AI Content Marketer

Content OS thinking around publish calendars and distribution.

Read →

Full Transcript

Complete transcription of the walkthrough. Video embedded above; original on YouTube.

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, not even including the time it took me to plan and script and record the actual footage.

And even when I hired video editors, it was still a major bottleneck in my process because I take such a detail-oriented approach to my edits and the specific B-roll clips and the sequencing and the pacing, and there's a lot that goes into it that you may not notice on the surface.

And so for well over a year, I've been on the hunt for ways that I can incorporate AI into how I edit my videos.

And I've tried all the tools out there, but none of them really made an impact on the one metric that matters, which is the actual amount of time it takes to go from recorded footage to publish ready, until now.

So as of about a month ago, all of my videos on this channel have been completely edited using Cloud Code, including this video that you're watching right now.

And so that enables me to record a video in the morning and have all of the post-production done by the end of the same day.

From editing out my bad takes, to generating custom motion graphics, to selecting B-roll and stitching it all together, all of that is now handled with a complex set of agent skills orchestrated using Cloud Code.

So today I'll show you the entire process from end to end.

But what I really want you to take away from this is a glimpse into what it looks like to take an AI-native approach to our work.

Now, this is one of the more complex AI systems that I've assembled in my business.

It took a lot of iteration and trial and error, and I'm still improving it on every run.

But this is what it looks like to rethink, at a fundamental level, the most important processes that drive our business, and see how we can retool those using AI.

And most importantly, I'll show you the points where the human in the loop, me, giving my input and my approval, really matters, and how I design that into this process.

So let me start by mapping out all the components at play in my video editing system.

We start with my raw recorded footage of me on camera and my screen recordings.

And then I use Cloud Code to initiate and orchestrate the entire process.

I invoke a custom skill that I created, which I call Video Editing, which interacts with a different skill called Video Use.

And that is sort of an engine that operates FFmpeg.

My Custom Wrapper skill is what dials in the editing process for exactly how I need it for the way that my videos need to come together.

Transcripts drive a lot of this, so I'm using Eleven Labs for that.

And you'll see how I actually retranscribe the video multiple times throughout this process.

So that costs a bit more, but it's how the Cloud Code agent is able to self-verify its own editing work.

Now, selecting and placing B-roll clips throughout my videos has historically been a really time-consuming process.

And so I built this custom app that I call Tubery, and that's where I store and index my library of B-roll clips that I ever use and reuse throughout my videos.

And Cloud is able to analyze the script of the current video and choose the most relevant B-roll clip from my library and place it in.

But for most of my videos, we also generate new visuals like motion graphics.

And for that, I created another custom skill called Create Visuals, and that one makes use of a different skill called Hyperframes.

So that's the engine that helps me create motion graphics like the one that I'm showing you here.

And so my Custom Wrapper skill dials in the branding and the consistency that you see across all of my motion graphics.

Now, while the vast majority of the work is done by Cloud Code, there are some critical points where I, as the human in the loop, need to give my approval and my input.

Here's how that process plays out.

We start with my raw recorded footage, and then Cloud runs phase one, where it does a bunch of prep work.

It's running transcriptions, it's analyzing where to make the cuts, where to place B-roll, where we need to create new B-roll, and it preps all of that for my initial review.

And so once I approve, that kicks off phase two, and that's where Cloud works for a while and does its first pass edits.

It creates and generates some motion graphics, and it presents each segment for my review.

Now, that phase can sometimes take over an hour, which is a good time for me to do other work like creating the thumbnail for this video.

I sometimes suggest a few fixes, and all I need to do there is write a few notes into the text transcript, and then Cloud recuts those segments with my feedback incorporated.

And once I approve, Cloud proceeds to its phase three, and that's where it stitches together all the segments and exports the final video.

So then we have a few final cleanup tasks, like deleting the working files and saving new B-roll clips to my library in Tubri, and then prepping everything for publishing on YouTube.

And all of that is automated using my skill with Cloud Code.

So that's the process.

Now, let's run it on a real video.

Now, just to show you what we're working with here, here's a look at some of my raw footage.

Some of my segments are scripted, where I speak off of a teleprompter, and I do multiple takes for most of the lines.

Take a look.

Or I went out to dinner, took a walk, it might have even been closer to two hours that it worked on that phase of, might have even been closer to two hours that it worked on that phase, I saw that it spawned multiple backgrounds.

Eventually, my good takes are in there somewhere, but it takes a talented editor to piece it all together, or a well-crafted AI agent.

All right, so my starting point for this whole process is to take the raw footage that I've already recorded, which lands in my Dropbox folder, so that I have backups over there for all of the raw footage, and that's right here.

So I usually record the footage sort of like this, where I number each segment of the video.

And I'm either recording just directly to camera, where I'm reading off of a teleprompter, or I'm recording my screen and my camera in two different feeds, where I'm showing something on screen, and I'm sort of riffing without a script while I turn to the camera.

If you've seen any of my videos, those are like the two types of segments that I do.

And then I number them and organize them like in the sequence that they will end up in the video like that.

So basically, I back these up into Dropbox first, and then I move these into another video folder, and that's here in this repo.

So here I'm working in my content development repo.

It's darkened here because I don't want to push this folder and its contents into GitHub, because there are a lot of really large 4K video files in there.

Now, this repo has a whole bunch of custom skills.

Most of these are custom, like two of them are third-party skills, but the rest are my custom designed and engineered and crafted skills that follow my entire content process.

And I've gone through multiple weeks of iterations on these things.

The one we're going to be focused on today is mainly this video editing skill, and this is going to run the entire process from end to end.

Now, within this, we're sort of like wrapping and referencing multiple other skills, such as this video use skill.

We're also calling on the hyperframe skill, and actually we're going to be using another one of my skills called create visual, and that's what we'll be using to generate custom motion graphics that will be shown throughout this video, as you've probably seen in some of my other videos.

So all of that stuff is going to be handled with Claude code following my process that I've built into these pretty complex set of skills.

Now, to kick off the whole process, my first move here is to just run video editing.

So I'm just going to give it a hint, and I'll just say today we're editing the video about using Claude as a business brain.

So that is actually the topic of the video that we're going to be editing here today.

Probably by the time that this video drops, that video will have already published.

So you can actually see the final result of the video that we are going to be editing today.

It should already be live on my YouTube channel.

Now, when I kick this off, it's going to start what I call phase one.

There are basically three big phases that we're going to run through throughout this editing process, and phase one is what I think of as like a prep phase.

So once I initiate this, Claude is going to, you know, gather up all that raw footage.

It's going to transcribe it by sending it to 11 labs and getting the initial transcripts for each of the segments.

And then Claude is going to do a deep analysis of the content within all of the segments that I've recorded.

It's going to actually like mark up the transcript to decide where it's going to make some cuts, where it's going to remove dead space.

It's also going to find B-roll that it could use.

Perhaps we have existing B-roll that we've already produced in previous videos that we can reuse here.

And for that piece, it would actually go into my custom built app that I call Tubery.

And that is my library of B-roll content that we've developed over the last several months.

And all of this is like filed away with, you know, really descriptive descriptions and keywords and things.

And so Claude is able to access this using the API that I built on it.

That's how it finds the right B-roll to apply.

But actually more times than not, it's going to find opportunities in the script to generate new B-roll, mostly new custom motion graphics.

So it's going to find all those opportunities, it's going to mark them up, find the right spots, plan out where it's going to make all the cuts.

It's also going to do some color grading and it's going to, you know, give me a few options on that.

So all of that is just prep work, but even before it even starts to get to work.

So it's going to start that phase one now when I kick off this process.

And so I'm going to pause here and I will return once that prep phase is all done and ready for me to review and green light into the next phase.

By the way, I want to mention that for today's video edit, I'm actually using Claude Fable 5.

Now, all of the video edits that I've done on the previous videos published in the last couple of weeks on my channel, those were done using Claude Opus 4.8.

Now I'm recording this on the day after Claude Fable 5 finally came back and became available again to use.

So I'm going to take advantage of it while I can, especially while we are here before this July 7th cutoff date when they're going to actually start to charge extra for it.

So I'm going to make use of it.

But I just want to note that I have been able to run this process totally successfully without a hitch using Opus 4.8.

I expect Fable 5 will be a little bit smoother, but really it's just following all of the specific instructions in my very complex video editing skill here with all sorts of like instructions and scripts and things built in.

So today we are using Fable 5.

Okay, so Claude's initial phase where it did all of the prep work, that is all done.

I think that initial phase took maybe about 10, 12 minutes.

What do we have here?

So inside of the editing folder in this little project folder, there's a whole lot of new files that Claude sort of cooked up here.

Now, most of these files that are within these different segment folders, most of these are like working files.

There's a lot of like JSON stuff in here.

There are like little fragments of things that it's doing.

It's sort of like doing its own little analysis and storing all these working files.

So most of that stuff I don't really need to touch.

That's just for Claude's technical use throughout this project.

But I did design the process to prepare things in a way that's easy for me to quickly review and give my input back.

The whole idea when I design a complex agent skill like this is to make it really optimal for me to just step in and do my input and then walk away and do something else.

So the main starting point for me at this first gate is for me to look at this review.md.

So Claude created this.

This is sort of like its main deliverable to me.

And it's sort of like a checklist of things that are ready for me to read through and review.

Now, I actually kind of skip past this one and I go directly into each of these segments.

So these numbered segments are like the segments that will make up the video.

There's going to be like a camera introduction and then there's going to be like a screen segment and then another camera and then another screen segment and then an ending segment.

Right.

So that's like one, two, three, four, five.

Now, something to be clear about.

Claude has not started actually editing any video yet, and it also has not yet created any motion graphics.

This is all prep work.

It's kind of laying the groundwork so that I can then give it the go ahead to start that phase two.

So we're going to dive into the first segment here.

And what do we have in here?

So first thing I like to look at is this grade folder.

And basically, Claude is going to do a little bit of color grading on my camera to either warm it up or make it a little bit punchier.

So this first one is like the default footage that comes out of my camera, like warm cinematic color grade.

It's kind of hard to tell the difference between these.

But, you know, you can see it closely.

I think that this one works fine.

So I'm actually not going to give it any course correction on this.

It's just going to go ahead and default to this color correction for all of the camera shots throughout the video.

So that'll be good.

That's a nice touch.

The other thing that it's doing, like under the hood a little bit, and I had to go through some iteration on this is, you know, I had to make sure that my audio from the mic is directly aligned with my mouth and the camera footage.

Sometimes it was off by a couple of seconds based on my camera setup here.

So I actually built in a process for Claude to self fix that.

He does that through some of these like wave files.

So it's like matching up wave files to video files and it gets a little bit technical in there.

The other thing that I will immediately start to look at in each of these segments is transcript.md.

And throughout this process, I'm going to use this transcript.md for each of the segments as my source of truth to see what's happening in the edit and to give my feedback on the edit.

So I designed this sort of like interface using Markdown files between me and the editor throughout the process.

So what do we have here initially?

At the very top is sort of like an overview for me.

But ultimately, we have like time stamped line by line transcriptions of everything from this particular segment.

This is the intro segment.

This is probably the first three or four minutes of the video.

So it did send it out to Eleven Labs.

It came back.

We have this transcript now.

And Claude went ahead and time stamped everything.

Or Eleven Labs did that, but Claude put it into this format.

Now, you'll also notice that there are these little tags like this says cut and then it's sort of like a closing tag.

So I worked with Claude to create this little like syntax where we have like these wrapping tags sort of like HTML that defines exactly what Claude is going to remove.

So all of this was probably like bad takes.

Like I said something a few times and it's going to keep the good take, which is typically the last time I say it.

So there are these like cuts throughout and I don't really need to do anything, but I do see them here.

If I see something that's off, I could course correct it, but I really don't touch it.

I'm just going to let it go with these proposed cuts that it's going to do when it goes ahead and creates this.

The other thing that it does is it checks my B-roll library to see if I have any B-roll clips that we want to use anywhere.

I'm going to come back to that in just a second.

But it's also proposing that, hey, in this part of the script, I think it would be good to generate a new motion graphic.

We can create something new that helps to visualize the model that I was describing in the script.

So Claude just identified that and said, hey, it's a moment at six minutes and 19 seconds.

That's where we should put this new motion graphic.

And here's a quick concept for what that should be.

And actually, I think that's perfect.

I think that's I think that really fits.

So I'm just going to leave it in and not going to course correct it.

Good to go.

Let's jump over to the second segment, which I think is a screen, which is like a screen and picture and picture segment.

In these segments, which are not scripted, it's just me riffing.

That means I'm rambling a lot.

So you can see that it made significant cuts and it's sort of like summarized all of the cuts that it made.

And here I'm I instructed Claude to have a lot more creative freedom and empower it to go ahead and just cut out the fluff.

You know, I tend to describe things a lot and maybe I say the same thing multiple times in different ways.

But really, we only need the best take of that.

Claude is going to do its best to cut that stuff out.

It's also going to, you know, remove any like dead air, dead space.

It's going to eventually cut out all of the ums and the ahs.

And I do a lot of those when I'm screen casting and I'm just riffing.

So it's going to try to catch most of those while keeping it natural.

One thing I forgot to do before I initiated this process, and it's fine to do it now.

Actually, that's the purpose of having this checkpoint in the process is I did need to record some new B-roll.

This is not motion graphics.

This is like screen recordings.

So for that, I usually just like whip out a screen studio for these like quick, like five second recordings.

Here's what I'm telling Claude.

I'm saying I have some new B-roll clips that I just dropped into the B-roll folder.

Use one titled brain files around where I talk about this, where I say that in the script and then use the AI native workshop.

When I mentioned that in the promo segment, be sure to push those clips into Tubary.

That is my custom app for this is Tubary here's have like.

So I have this like clips library where store all of B-roll clips and it's kind of nice.

I hover over it and it has these little previews of what each of these B-roll clips are.

And I have my agent or Claude code go in and it automatically summarizes all of these.

So it uses these detailed descriptions to automatically pick out past B-roll clips and reuse them in relevant parts of new scripts.

Right.

So it's really handy to have this custom built app that is just my library for all of my B-roll.

I have like hundreds of clips that we're generating all the time.

And then one more thing is near the end of the first segment, I sort of introduced the video.

Sometimes I like to have Claude create a clip of a future part of the video where it shows me in the meat of the video.

I like to tease that near the beginning.

And so that's exactly what I'm telling Claude to do here.

And the video editing skill knows that that's a pattern that I like to do.

And it's expecting me to ask for that or just knows how to do that.

So I'm going to just give it those things.

And then finally, I'm just going to say everything else is good to proceed with the next phase.

OK, so it is just getting to work now and we're now entering that phase two where it's going to actually start to generate some custom motion graphic B-roll clips.

It's going to actually edit every one of these segments and it's going to make all the cuts.

So it's going to go ahead and actually do all these edits.

I'm going to let that cook.

It's going to take a while.

It might even take like up to an hour or so.

I'm going to let it work on that and I'm going to take a break and go to dinner.

By the way, if we haven't met yet, I'm Brian Castle, and this channel is about working A.I. natively, not just reaching for A.I. here and there, but taking the core processes that run your business and rebuilding them around A.I. Exactly like what you're watching me do here with my video editing right now.

And if you want to make that shift yourself, I put together a free workshop on going from A.I. dabbler to A.I. native.

I walk you through the method behind systems like this one so that you can start to retool your own work.

It's completely free over at builder methods dot com slash workshop.

All right, let's keep going.

All right.

So Claude cooked on that for well over an hour.

I went out to dinner, took a walk.

It might have even been closer to two hours that it worked.

I saw that it spawned multiple background processes to get this done.

Also, part of the reason why it takes a while is because I have engineered the skill to work in a certain sequence, especially when it comes to generating custom motion graphic visuals.

In my earlier testing, I found that when I have it creating multiple motion graphics at the same time, using the hyper frames engine and the other scripts that are involved, 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.

So it creates all those.

It takes a while and then it goes through and it actually does edits for all the segments.

So, you know, there's been a lot of like iteration and technical tweaking to get this really finely tuned to the point where I could step away for hours and it just works.

And then I come back for this review session.

So this review session typically only takes me about 20, 25 minutes where I do a pretty deep review of its work.

And I'm going to do that now.

So what we have here is a finished edit for each of the five segments that are ultimately going to be stitched together to make the final video.

And here's the final message that Claude gave me.

You know, it says like all five segments are ready.

Looks like the total runtime for this video is going to come in somewhere around 19 minutes.

And that's pretty typical for my videos.

It gave me a few notes in here.

But really all I need to do is start to dive in to each of these segments and, you know, I watch them back.

So this first segment is only like a minute 32.

That's like the intro section.

Now, off camera, I did already review these closely and I have some fixes that I'm going to ask it to make and I'm going to show you those here.

But the other thing that I like to do before I even start to watch these back is I like to check out the new custom motion graphics that were created and generated.

And those are inside of this vis visuals folder.

And so these were created using hyper frames.

But then I have my own create visual skills with which gives it my branding and my specific structure and content templates and things like that.

So I did review these and these are mostly pretty good and I can sort of like look at these.

And so these are going to be graphics that show up in the video, but I'm also going to save them into my library and I can use them in things like social media posts.

Now, this is actually the one issue that I noticed across all of the custom graphics is that I don't like this little text thing sort of overlaps.

So I'm going to ask it to fix that, just like I would ask it, ask Claude to fix any other like UI bug in a website or something.

I'm going to take a screenshot, copy that to clipboard, and I'm going to paste it in here and I'm going to say this motion graphic, the can't see in and out text and the red circle come too close to the right edge of the box.

Let's move that red circle and its text to the center of the line between two boxes.

I think Fable will know what I'm going for there.

Okay, the next fix that I need to ask it to do is something that I've noticed multiple times in some of my previous edits, so I'm going to ask it to fix this, but I'm also going to ask it to bake this verification into the skill itself so that I don't need to ask it to fix this again on the next one.

If you notice, you know, my head sort of walks back and forth a little bit, but most of the time I find that my head is a little bit too far to the left within this framing.

So, you know, it doesn't perfectly like center my head and my body in this picture in picture frame.

And I've noticed that's the case in most of these segments.

I noticed in both of the screen picture in picture segments, my head is not horizontally centered in the PIP frame.

I'll need you to fix that in segments two and four.

And this is something that I've noticed in previous video edits, so I also want you to find the correct location in the skill instructions and add a verification step to look for this specific issue.

I want you to take multiple screenshots of picture in picture segments and check to see if my head is not horizontally centered.

And if so, fix that before finalizing the segment.

All right, so we've got that one in.

OK, so then I go through and I actually watch back every second of every segment, and as I do that, I usually kind of make the video small.

And I'll put it sort of like up here and then watch it back.

I will read through this transcript because this is where I can mark in any fixes that I want to make.

So this was actually one of the only glitches that I think it actually did a really good job this time, but I did notice this one.

So somewhere right around here, I sort of said the same thing twice back to back.

So basically at the end of this phrase, I actually running paid traffic because I'm focusing on organic traffic.

But then I say because first I need to focus on organic funnels.

So they're slightly different wording, but I'm saying the same thing twice, and it would be awkward to hear me say that like that back to back in the final video.

So I have actually set up the skill so that if I want to be really lazy about it, all I really need to do is just type in fix like that brackets.

And Claude will just find that and analyze the whole area around here and just know that like something is wrong here.

Brian pointed it out.

I need to fix it, and it typically will fix it.

I want to be a little bit more descriptive.

I can add it into the prompt, and that's actually what I'm going to do here.

I'm just going to say segment two.

I sort of said the same thing twice here.

I added a fix marker.

I want you to delete the first duplicate phrase, which was that this is actually a good moment to tell you how the self-correction system is built in.

So what happens is this transcript is not the original transcript that we had at the very beginning of the process.

This was a retranscription of the video after Claude made all of its edits.

So I do have Claude show me the initial transcript where it says what its editing plan is going to be, like it marks what it's going to cut out and where it's going to put B-roll and whatnot.

Then it makes all those edits.

It cuts a lot of the content out of the original footage, and then it sends it to Eleven Labs again, and then it gives me this transcript.

So why do I do that same cycle and actually pay for that extra transcription process?

Well, that's how it actually can catch its own mistakes, right?

So it reanalyzes the transcript after it does all the programmatic editing work to spot things like that, like where I say a phrase twice or maybe some dead air that was inadvertently left in the script or something just doesn't make sense, and so it needs to piece together some of my sentences.

It's going to look for those things, and if it spots its own errors, it's going to just read and run the whole edit again, and that's why it takes like two hours for it to do that work.

But again, I could be doing something else while it works, and I know that when I come in here, there's only like one or two small fixes that I need to ask it to make.

So it's incredible.

All right, one more issue that I noticed also in the second segment near the end of it around 35, we show some B-roll.

It was, you know, one of the motion graphics that was created.

We show that here, and so what I noticed was that it sort of cut off that B-roll a little bit too soon.

It didn't give it enough time to play out, which is a little weird for the viewer, and I think that there was actually an extra word thrown in there.

So the B-roll clip is not played for long enough.

Also, there seems to be an extra word stuck in there.

I added a fix marker in that spot.

All right, so it's going to find that and clean it up.

All right, so now here is one more thing that I noticed in segment four, which, you know, the editor really wouldn't have picked up on its own, and that is there are like two spots in here where I'm describing something.

And I didn't realize this at the time I was recording it, but I was sort of showing something on the screen that was here at the bottom right corner of the screen, which means it's going to get covered up by the picture in picture.

So there was about a minute in the beginning and a minute near the middle where I do that, and it's going to be really confusing for the viewer if this thing is hiding what I'm showing.

So I sort of prepared these two.

In segment four, we need to fix this picture in picture covering up some content on the screen.

Here are the details.

So I gave it like the span of time where I want the picture in picture to sort of fade out and then fade back in.

And then the only final issue, which was in the final segment, like the ending, just didn't use the B-roll for when I talk about the AI native workshop.

So I'm just going to add that in.

Other than these issues, all other segments are locked and good to go.

Please go ahead and make these fixes, and then when you're finished, you can immediately proceed to the final phase, which is to merge all of the segments together and export the final 4K MP4 file.

In my previous edits, I probably would have had it just make those fixes, and then I would review them again, and then I would give it the go ahead to do the final stitching.

But the issues here were so minor, and I'm using Cloud Fable on this, so I have a pretty high level of trust that it's going to be good to go.

So I sort of just want to get the whole thing done.

And if there are any remaining issues after that, I could always go back and ask it to fix that segment and rerun it if I have to.

But I'm pretty confident it's going to be good to go.

So it's going to make those edits, and that's probably going to take another, you know, at least 30 minutes or so.

So I'm going to work on that, and meanwhile, I can go, you know, work on something else, like I started working on the thumbnail for this, which I still do in Adobe Photoshop.

So, yeah, I'm going to work on that a bit while that's cooking, and then this thing should be pretty close to ready to go.

All right, so all of those fixes are now complete.

That took a little while longer than I expected.

It took, again, over an hour to make those edits because it went through multiple rounds of checking its work and, you know, tuning some things, and I didn't have to step in at all.

I just waited for it while it went through, and I just worked on the thumbnail and some other stuff while it worked.

So here we are.

It is all done.

The final video came in about 19 minutes, so that looks good.

But, you know, I did just go through here, and I found those—actually, I watched the whole thing through, but I did notice that all those specific fixes that I asked for have been completely made.

So all of that is good to go.

And so now I have the final MP4 file here, but still all of the original working files, which included, you know, a lot of, like, raw footage and, like, little sub cuts and lots of little working files and things.

Lots of stuff is sort of just accumulated in this folder.

So we need to do some cleanup, but actually there's a number of, like, final cleanup items that I need to do at the end of every video editing project.

And so, you know, I figured out, like, what all those little cleanup tasks are, and I just built them all into the very end of the process in this skill so that with literally one click of a button, all of it can just be done automatically.

So I'm not going to go too deep into the weeds here, but basically what we're going to do is we need to rename that final file, you know, which currently, like, named with the date, and it's sort of, like, temporary.

Now, you know, obviously it's really easy for me to just click and rename it right now, but that's just, like, one of several little tedious steps that has to be done right every time.

So I like to rename it and make it sort of a keyword-friendly file name, which is then ready to actually upload to YouTube.

We're going to do that.

It's also going to move this file out of this folder into another location on my system, which is backed by Dropbox.

So I have, like, the final version, and I have the original unedited raw footage all backed up in Dropbox.

And so once it verifies that it has moved it there and it is there, it's going to go ahead and just wipe this working folder so that we get that stuff off of my hard drive.

It's taking up a lot of space because this is a lot of 4K video.

So it's going to delete that for me after it kind of does the file management stuff.

A couple of other things.

We're going to take all the new B-roll that we created during the course of this project, and it's going to push that stuff up to Tubri.

Tubri is my custom-built app that I use to, you know, manage all of my B-roll so that, like, next time if I cover a topic that covers the same topic, I can easily just pull one of those pre-existing motion graphics that we generated here.

I also have a custom app, another custom app called SparkDrop, and that's where I manage my pipeline and my publishing calendar.

I'm going to publish this video manually.

I usually do that for the long-form YouTube videos, but I still like to get it registered in my publishing calendar so that I see I have, like, LinkedIn posts and tweets and newsletters and stuff, like, where all of my videos are popping in my content plan.

So it's going to handle getting it up in there.

Oh, and one more thing, and this is a really tedious thing that it's going to do automatically for me.

It's going to create the chapters list for YouTube.

So I do already have the packaging all planned out for this video.

In this case, I'm going to test out two different titles, and I've already created the thumbnails for these, so that's good to go.

This is, like, my template YouTube description.

What Claude is going to do is write the intro of the description, which describes this video and what it's about, and then it's also going to fill in down below this list of chapters.

That's not just a list, that has to be timestamped with the exact time that each chapter begins.

So it's going to analyze the script, analyze the final recording, and it's going to actually make that text list of timestamps rather than me having to scrub through the video and find those timestamps and do it manually.

All of it is done automatically from Claude.

Okay, so that is the cleanup process.

Let's kick it off.

Here we go.

All the cleanup tasks have been done automatically.

The final video has landed in the correct place.

It's backed up in Dropbox along with the original footage, and so that is here.

You know, my next step would be to actually upload that into YouTube.

I also created the thumbnail for this video, so actually I created an A and a B. I like to do some A-B testing on those.

I did this in Photoshop while the video editor was working, so again, I'm able to actually multitask and be so much more efficient than I used to be before I was doing it this way.

All right, so that is all set, and we have the description and timestamps all set up.

So here is the description.

It wrote that up.

I like to keep it kind of short, and then down at the bottom, we've got the list of chapters all with the timestamps good to go, and I really like the way that it broke it up, the way that I like it.

It sees the way that I like to, so this is basically all ready to go for me.

My next step is just to throw it up into YouTube and schedule it to publish.

So that's the whole system end-to-end.

It's a lot, but the point is the approach.

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.

And that's what taking an AI-native approach actually looks like.

And you can get instant access to my free workshop on shifting to AI-native by going to buildermethods.com slash workshop.

And hit subscribe so you don't miss my next video on going deeper with AI.

Let's keep building.

Credit: Original YouTube video · Workshop mentioned: buildermethods.com/workshop · Local host: static2 video file

Comments

Approved comments appear below. Log in once with GFAVIP — it applies across the whole site. GFAVIP login

View comments archive