Give
The Note
Once.
Split the edit into seven jobs. Give each job a tool. Turn every note into a rule. Your second video takes fewer notes than your first.
The Takeaways
The creator records and gives notes. Every other job in his edit goes to a separate tool, and Claude Code runs all of them from his own computer. The look of every video lives in one skill file he trained with notes over weeks. His last video cost about $27 to edit and shipped the same day he shot the footage.
One person, seven jobs
He keeps two jobs: press record and give feedback. The rest split into seven roles: editor, transcriber, animator, researcher, screen editor, sound designer, and finisher. Each role maps to one tool.
The editor is Claude Code
Claude Code in the desktop app acts as project manager for the whole video. Local mode lets Claude open his files, run programs on his machine, and write finished output into a folder.
The transcriber is Parakeet
Claude reads text, not audio. Parakeet, a free speech model from Nvidia, turns raw footage into a timestamped transcript. Claude reads the timestamps to find the right takes and cut around stumbles and restarts.
The animator is HyperFrames
Titles, logo pop-ins, and motion graphics once needed After Effects. HyperFrames, free from HeyGen, renders animations Claude writes as small web pages into 4K video, on his machine, at zero cost.
The researcher is the browser
When he mentions an announcement, Claude opens Chrome, finds the original post, page, or paper, and records a screenshot or scrolling clip as B-roll, with the exact line highlighted.
The screen editor is Tella
Tella records face and screen together. An MCP connector gives Claude Code control of everything inside Tella: cuts, zooms, layouts, and formatting.
The sound designer is Epidemic Sound
A paid music and effects library, connected to Claude. His taste: a suspenseful hook, then quiet lo-fi hip-hop beneath the body. Effects follow their own rules, a pop when something appears, a click when something gets clicked.
The finisher is FFmpeg
Free, more than 20 years old, and under the hood of most editing software. Claude uses FFmpeg to join pieces, remove black frames, and check audio sync before he sees a frame.
The skill holds the taste
None of the seven tools knows what his video should look like. His skill, YouTube-Edit, runs about 1,400 lines and spells out colors, fonts, animations, and sounds. Claude wrote the file. He supplied the opinions. The skill now holds 36 rules.
The setup, in order
- Download the Claude desktop app. A paid plan is required. He recommends $20 to start.
- New Claude Code session, local, attach a folder, auto permissions, a recent model for setup.
- Turn on web browsing in Claude Code settings.
- Prompt Claude to build a video editing system with HyperFrames, FFmpeg, Tella, and Epidemic Sound, step by step.
- Connect Tella and Epidemic Sound under Customize, then Connectors.
- Save the system as a skill, open a new thread, run a test.
He trained on hooks first
Short clips, timestamped notes on every edit. On day ten he added sound and tested eight to ten effects on one hook. After each round he told Claude to save the lesson into the skill. A note given once never came back as the same mistake.
The demo
A raw hook full of restarts went from 2 minutes 46 seconds to 31 seconds in a 10 to 20 minute run. His follow-up asked for a suspense track, then a final save to the skill. He now loads full footage at night and reviews in the morning.
Speed beats savings
He plans, shoots, edits, and publishes in one day, where human editors took three to seven days plus revisions. He gives his skill away free in his community, We Are No Code.
The cost, to the dollar
| Line | Monthly | Per video |
|---|---|---|
| Claude Max plan | $200, shared with all his work | About $24 in measured tokens, at most |
| Parakeet, HyperFrames, FFmpeg | Free | $0 |
| Tella | $13, annual plan | About $2 |
| Epidemic Sound | $9.99, annual plan | About $1 |
| Total | About $27 | |
| Human editor | $250 to $1,000 or more |
Give The Note Once.
Core Message
You fix the same things in every video because your notes live in your head or in a chat thread. Split the edit into seven jobs, give each job a tool, and turn every note into a rule inside one skill file. By the tenth video, you direct instead of edit.
Opening Premise
You know a weekly video would help clients, recruiters, and prospects find you. So you recorded one. Then you spent five hours in a free editor cutting restarts, nudging captions, and hunting for music, and the second video took five hours again. A freelance editor quotes $250 or more per video. The standard advice says batch your editing or learn the shortcuts. Both keep you at the timeline.
The creator of "I Fully Automated My Video Editing Using Claude Code" does not know how to edit and does not know how to code. He stopped editing and started directing: seven tools do the work, and one file remembers every note he ever gave.
Look at your last three edits. How many of the fixes were the same fix?
The Five Parts
Hire jobs, not apps.
New professionals shop for one app to do everything and end up with a template look. Start from the jobs an editor performs, then assign one tool per job.
| Job | What the job does | Tool | Starting cost |
|---|---|---|---|
| Editor | Picks takes, cuts, places zooms, runs the rest | Claude Code, local | Paid Claude plan |
| Transcriber | Turns audio into timestamped text | Parakeet | Free |
| Animator | Titles, logos, motion graphics | HyperFrames | Free |
| Researcher | Finds and captures proof as B-roll | Chrome, driven by Claude | Free |
| Screen editor | Face plus screen layouts | Tella via connector | About $13 a month |
| Sound designer | Music beds and effects | Epidemic Sound | About $10 a month |
| Finisher | Joins pieces, removes black frames, checks sync | FFmpeg | Free |
Do this
- Copy the table into job-map.md in your video folder.
- Log the minutes each job takes you by hand on one video.
- Start with the four free jobs. Add a paid tool only after the free version fails on two videos in a row.
- No screen recordings? Drop the screen editor row.
Train on the hook first.
A full video gives you forty problems at once and no way to tell which note fixed which. A 30-second hook gives you five. The creator trained on hooks for days and added sound on day ten, after the cuts looked right.
| Order | Layer | Done when |
|---|---|---|
| 1 | Cuts and takes | No restarts, no dead air, no lost words |
| 2 | Zooms and framing | Every zoom lands on a change of idea |
| 3 | Graphics and animation | Colors and fonts match your brand file |
| 4 | Sound effects | One effect per on-screen event, never two |
| 5 | Music | Bed sits below your voice the whole way |
Do this
- Record three hooks of 20 to 40 seconds. Keep your mistakes in. The cuts are the test.
- Give notes on one layer only, save, then run the next hook.
- Move up a layer after two hooks in a row need zero notes.
- For sound, ask for eight options on one moment and pick one.
Why hooks: the hook is the part viewers judge first and the part you rewatch most. Training there pays twice.
Give the note once.
His whole system rests on one habit. After every round of feedback, he tells Claude to save what it learned into the skill. A correction in chat helps one video. A correction in the skill helps every video after.
Write every note in four parts
| Time | The exact timestamp, such as 00:22 |
| See | What happens on screen now |
| Change | What should happen instead, with a number where possible |
| Type | RULE for every video, or ONE-OFF for this video only |
00:04 / Logo pops in at 40 percent width / Make the logo 60 percent width and hold 1.5 seconds / RULE
00:22 / Click sound and whoosh fire together / One effect per event, keep the click / RULE
00:31 / Wrong client name in the caption / Spell the name Okafor / ONE-OFF
Apply my notes. Then add every note tagged RULE to the skill as one line each, with the timestamp of the example. Ignore notes tagged ONE-OFF. Before saving, copy the current skill to a dated backup. List the rules you added.
- Keep a running count of notes per video. The count should fall every week.
- Read the rule list every fifth video. Delete rules you no longer agree with.
Show the page, not a claim.
His researcher pulls B-roll from the original post, page, or paper and highlights the exact line. For a new professional, proof on screen does more work than polish.
The researcher rules
- Capture from the original source only: the announcement, the filing, the official docs, the post itself.
- Keep the address bar or account name visible.
- Highlight one line per capture. Zoom on the line you speak.
- Check the date on every page. A stale page on screen reads as your mistake.
- Never let a generated image stand in for a screenshot.
- Log every address in sources.md and paste the list into your video description.
When I name a company, product, law, or number, open the original source in the browser, capture a screenshot with the address visible, highlight the sentence I quoted, and log the address and date in sources.md. If you find no original source, flag the timestamp and show nothing.
Your own proof counts too: a client result, a before and after, a calendar of booked calls. Same rules, client names blurred by default.
Price the video, then the week.
He measured the tokens one video used, then added each tool's share. Do the same before you call the system cheap, and track hours next to dollars.
| Column | How to fill |
|---|---|
| Raw minutes | Length of footage recorded |
| Final minutes | Length after the edit |
| Run time | Clock time from start of edit to first cut |
| Notes given | Count, split into RULE and ONE-OFF |
| Your minutes | Watching plus writing notes |
| Model cost | Ask Claude to report usage for the run |
| Tool share | Monthly tool bills divided by videos that month |
| Publish lag | Days from recording to posting |
Guard the machine
- Auto permissions apply to your real computer. Point Claude at one video folder, never your home folder.
- Copy raw footage to a second drive before every overnight run.
- Keep the laptop plugged in and awake for overnight runs.
One designer, one weekly video.
Theo, a first-year freelance UX designer with two retainer clients, wants a weekly 8-minute portfolio teardown. He records 22 minutes of raw footage and spends about five hours editing by hand, so he posts every other week.
| Map | Claude Code local, Parakeet, HyperFrames, FFmpeg, Chrome for proof. No paid tools in month one. |
| Folder | raw, renders, skill, sources. Raw footage copied to an external drive before every run. |
| Hook | Three 30-second hooks in week one. Cuts, then zooms, then brand graphics. |
| Note | Four-part notes, RULE or ONE-OFF. Save prompt after every round. Skill backed up first. |
| Proof | Portfolio pages with the address visible. One highlighted element per critique. Names blurred unless the owner agrees. |
| Price | $20 Claude plan, $0 in other tools. Per-video sheet every Friday. |
Planning estimates, first five runs
| Run | Asset | Notes | Rules in skill | His minutes |
|---|---|---|---|---|
| 1 | Hook | 14 | 9 | 35 |
| 2 | Hook | 9 | 14 | 25 |
| 3 | Hook | 5 | 17 | 15 |
| 4 | Full video | 11 | 23 | 60 |
| 5 | Full video | 6 | 26 | 40 |
Target by week six: about five hours of editing per video down to about 45 minutes of review, weekly instead of biweekly. Planning figures. Log four full videos and replace every number with your own.
The prompts.
Build a video editing system for me in this folder. Use Parakeet for transcripts with timestamps, FFmpeg for cutting and final checks, and HyperFrames for animations. Install what you need and tell me each step before you run the step. Read my brand file in /skill/brand.md for colors and fonts. Never delete or overwrite anything in /raw. Save the full system as a skill named video-edit, then tell me how to start a new session with the skill.
Use my video-edit skill on /raw/[file name]. Cut restarts, pauses over 0.6 seconds, and false starts. Follow every rule in the skill. When I name a company, product, or number, capture the original source as B-roll and log the address in sources.md. Render to /renders with today's date in the file name. Report raw length, final length, run time, and usage cost for this run.
Apply my notes below. Then add every note tagged RULE to the video-edit skill as one line each, with the timestamp of the example. Skip notes tagged ONE-OFF. Copy the current skill to /skill/backups with today's date first. List the rules you added and the total rule count. NOTES: [paste four-part notes]
Skill file starter
| Brand | Two hex colors, one font, logo file path |
| Cuts | Pause limit, how to treat restarts, hook length |
| Motion | Zoom on idea changes, one animation per 10 seconds at most |
| Sound | Hook mood, music bed level, one effect per event |
| Proof | Original source only, address visible, sources.md |
| Never | Delete raw files, publish, invent a screenshot |
Read the fine print.
The $24 sits on a $200 plan
He recommends $20 for setup and edits on the $200 Max plan. Usage limits on the smaller plan decide how many full edits fit in a month. Measure your own runs.
The price leaves out the weeks
36 rules and 1,400 lines came from weeks of timestamped notes. Your first month costs time, not money.
“While I was asleep” needs a director
The demo shows a 10 to 20 minute run, a person watching, and a second round of notes. A human stays in the loop.
Auto permissions run on your real machine
Skipping approvals also skips the chance to stop a bad command. Scope one folder. Back up raw footage first.
Transcripts mishear names
The auto transcript of this video writes Claude Code as "Cloud Code" and Tella as "Tellus." Add a names list to your skill.
Borrowed screens carry rights questions
Other people’s posts and papers belong to their owners. Show briefly, cite the source, skip anything behind a paywall.
A free skill is a borrowed taste
His skill is a lead magnet for his community and produces his look. Start from his structure, train on your own notes.
Tools age fast
Model names, connectors, and menus change within months. The job map, hook-first training, and the saved note carry over to any tool.
Seven days.
One skill.
Map the jobs
Fill job-map.md. Log the minutes each job took on your last video.
Build the folder
Create raw, renders, skill, and sources. Write brand.md with two colors and one font.
Run setup
Paste prompt 01 in a local session scoped to the folder. Save the skill.
Record three hooks
20 to 40 seconds each, mistakes left in.
Edit hook one
Notes on cuts only, four-part format, then the save prompt.
Edit hooks two and three
Compare note counts. Move to zooms once a layer needs zero notes.
Read the numbers
Fill the per-video sheet, count the rules, delete one, and decide: train another week, or run your first full video.
Give the note once.
Direct.
Don't Edit.
Build the system with other solo builders. Weekly field guides, live builds, and the prompts behind every issue.
Join the AigentLab