Source: raw/How_I_Get_Claude_To_Edit_My_Videos_No_Code_Needed.md

Creator: Matt Wolfe · URL: https://www.youtube.com/watch?v=ep4psgAFOqc · Duration: 32:45 · Platform: YouTube · Uploaded: 2026-11-04 · Skill level: operator · Sponsor: VidIQ (he says he used it before the sponsorship)

Matt Wolfe edits his talking-head shorts with Claude on Opus 5.5, and says every short he has posted since a video about a Tesla car was AI-edited. To show the setup from zero he bought a fresh $20-a-month Pro account and built a Claude project with three connectors (VidIQ, HyperFrames, ElevenLabs), a working folder, and two skills Claude wrote after analysing his best shorts: one writes scripts, one edits. The editing runs headless through FFmpeg, with no Premiere or DaVinci Resolve. The first edit had problems; the method is to give feedback and have Claude update the skill each time.

Key Takeaways

  • The loop: paste a URL about the topic, get a script with a score, a view estimate, title ideas and a B-roll shot list; record the A-roll; drop the raw file into the project with no prompt; get back a cut short with B-roll, captions, music and sound effects.
  • What each tool does in his setup:
    • VidIQ (MCP connector): finds outlier videos on your channel or others’, and reads their transcripts, comments and retention.
    • FFmpeg: does the actual editing.
    • yt-dlp: downloads YouTube and Instagram videos for B-roll.
    • HyperFrames (connector): “After Effects style” animations.
    • Blender: 3D objects and animations when no B-roll exists.
    • ElevenLabs (connector): background music, sound effects, and a timestamped transcript.
  • Cut on waveforms as well as transcripts. Cutting from the transcript alone sometimes clipped him mid-word, so he tells Claude to check the waveform and cut after the sound ends. Nate Herk’s editing skill uses the same rule (see Related).
  • Expect the editing skill to be wrong at first. He says the script skill is “pretty dialed in from like the first go,” while the editing skill will need several rounds of feedback, each ending with “update the skill.”
  • Run a monthly review. Ask Claude to study your recent outliers through VidIQ and suggest changes to both skills, then feed them back. He calls it “almost creating this like reinforcement learning loop.”
  • Not Claude-only. He says the same workflow works in Codex with OpenAI’s models.
  • His limit: it suits short, talking-head, informational video. For long-form he still wants a human editor and to do edits himself.

What his own skills learned from his channel

The analysis of his best shorts took about 15 minutes and produced two skills, “short script” and “short editor”. It reported:

  • Topics that work: physical machines doing surprising things, such as flying cars, combat robots and body scanners.
  • Hook: “This is the coolest thing I saw today,” the name of his series.
  • Debate helps: videos where viewers argue whether the footage is real or AI do well. VidIQ’s visual analysis even described his Tesla and bodyguard footage as CGI, while his scripts present them as real demos.
  • Visual style: a 50/50 split with B-roll on top, magenta captions, and a B-roll change every 1.8 to 3.6 seconds.

Setup on a fresh account

  1. Create a project (“short form video editor”) and add instructions. His: “You are world class short form video editor. You take the source material and turn it into a script that is likely to perform well. You clean up A-roll video to cut out pauses and mistakes. You edit in B-roll from the source material and from what you find around the web to make the video highly visually appealing.” He adds that it can use VidIQ, Blender, HyperFrames, FFmpeg and yt-dlp.
  2. Customize, then Connectors: connect VidIQ and HyperFrames, authorising each in the browser. Later he adds ElevenLabs and picks the full version, which includes music and sound effects.
  3. Ask for the two skills. His prompt, shortened: use VidIQ to analyse my shorts, “look at the best performing shorts and figure out what makes them perform well. Look at both the script and the visuals and then create a skill that will generate similar scripts that are likely to go viral and another skill that can edit the videos to look like the existing videos.” He then describes the end-to-end loop and the edits he wants: cut pauses and mistakes, add B-roll, animations, subtitles, background music and sound effects. He ends with “When editing and doing initial cuts, use both the transcripts and the waveforms for editing.”
  4. Switch from manual to auto mode and click “always allow” so it keeps running while it works.
  5. Save both skills when it finishes.
  6. Connect a working folder (his is “claude editor”) with “don’t ask again for this folder on this device”, and add the same folder under the project’s context.
  7. Tell it where transcripts come from. “When I give you a video, use 11 Labs to get the timestamped script,” and accept the skill update.

Two blockers he hit on the first edit, and the fixes:

  • ElevenLabs refused to transcribe the video, and the skill would not let another tool do it. Fix: tell Claude to use an alternate transcription tool when ElevenLabs fails, and update the skill.
  • Downloads from NVIDIA’s site were blocked. Fix: Settings, Capabilities, turn on “create and edit files” and “use the internet while making files”, then under Allowed websites click Manage and add the blocked URLs. He also chose “allow all sites”. The change needed a new session; Claude wrote the prompt for him to paste into it.

The two test edits

  • Genie 4 (his existing account). He gave a link to the DeepMind blog post and a path to his own B-roll. VidIQ found other Genie 4 videos to learn from, and Claude wrote a script it scored 8 out of 10. The edit took 67 steps: load the skill, cut the A-roll, prepare B-roll and a music bed, write a plan, render, QA and deliver. It used ElevenLabs for music, loaded Claude in Chrome, pulled screenshots from candidate B-roll videos, timestamped every scene in his own B-roll, and used HyperFrames to make a typing clip he lacked footage for. One computer command failed and Claude worked around it. Details of the model are in Genie 4.
  • NVIDIA Motion Bricks (the fresh account). He pasted only the URL. Claude scored the idea 4 out of 5, expected 15,000 to 30,000 views based on his similar game and 3D shorts, and wrote a script without the AI phrasing he dislikes. He recorded it with retakes, dropped the file in with no prompt, and got a first cut.
    • Problems in the first cut: no background music, odd EQ or compression on his voice, one mistake left in, gaps too loose, and no HyperFrames animations.
    • The fix: one feedback message listing those problems, ending with “make sure these changes are updated in the skills so they’re applied to all future videos.” About 36 minutes later the revision had music, cleaner audio, tighter gaps and added graphics. Claude also wrote two Python scripts, a short-edit script and a graphics kit, for future runs.

Going further

  • Blender for missing B-roll. In another video Claude built a GPU animation in Blender and put HyperFrames text over it. He also points to Mon’nique Price, who he believes edits for NetworkChuck, getting a similar sequence from Claude.
  • The monthly review prompt: “review my last 10 YouTube shorts for outlier videos that performed well and give me a list of suggestions based on your findings for how I can improve my scripting and editing skills.” VidIQ pulled the channel’s analytics, transcripts, comments and retention curves without being asked. Suggestions included:
    • Say what is physically happening on screen in line two.
    • Put credentials and specs on title cards.
    • Keep caveats to one clause or cut them.
    • Make the first frame real footage of the thing in action.

Try It

  1. Start with the analysis prompt on your own channel, or name two or three channels you want to resemble if you have no history.
  2. Put the waveform rule in the editing skill on day one, before the first edit clips a word.
  3. Pre-approve sites in Settings, Capabilities, before the first edit so B-roll downloads are not blocked mid-run.
  4. End every round of feedback with “update the skill” so fixes carry to the next video.
  5. Run the outlier review about once a month, as he does, and paste its suggestions back into both skills.

Implementation

  • Tool/Service: Claude Pro with Opus 5.5; VidIQ, HyperFrames and ElevenLabs connectors; FFmpeg, yt-dlp and Blender run by Claude.
  • Setup: one Claude project with instructions, a connected working folder, two skills, auto mode on, and internet access allowed while making files.
  • Cost: Claude Pro at 1 for the first month through his sponsor link. ElevenLabs needs an account; its cost is not given.
  • Integration notes: editing is headless; no video editor app is opened. Long edits take a while (about 36 minutes for his revision), and he steps away while they run.

Open Questions

  • The skill files are not published, so the exact cut rules, caption style and B-roll timing code are not available.
  • Which transcription tool replaced ElevenLabs after the fix is not named.
  • Usage cost per edit is not given. The Genie 4 edit took 67 steps.
  • Which tab he used is not stated. The project, connector and folder screens he shows could be either the Chat or the Code tab.
  • His view counts (137,000 to 1.8 million on the shorts shown) are from his own screen; the transcript does not make clear which of them were AI-edited.