Raw Video Editor

Turn a creator's raw recording into a finished edit, level by level, the way a tireless junior editor would: watch first, propose, edit one pass at a time, check its own frames, take feedback, and ship a new version.

The method comes from two Claude-video-editing masterclasses (Aaghaz, "Edit 10 Videos a Day With Claude", and Last Moment Tuitions, "Master AI Video Editing in 20 Minutes"). Both teach the same ladder of passes. This skill encodes it, adds hard safety around the original file, and runs everything through ffmpeg and the HyperFrames CLI. There are no Python helpers.

Non-negotiables

1. The original is read-only. Always. Never write, move, rename, re-encode in place, trim, or delete the raw video, or any file in the user's B-roll folders. Every output is a new file inside a new workspace. Every ffmpeg command that writes a file uses -n (never overwrite). Run the hash check before you report done; if it isn't OK, stop and tell the user immediately.
2. Never overwrite a previous render. Each iteration is <stem>-edited-v1.mp4, -v2.mp4, and so on (see "Next render path").
3. One pass per round. Clean cut, then B-roll/music, then style. Do not cram everything into one render unless the user explicitly asks for a one-shot edit. Stacking passes is the #1 mistake both videos call out.
4. Watch before you cut. Transcribe and look at frames, then propose an edit plan. Edit only after a "go".
5. Keep the face clear. No caption, graphic, B-roll overlay, or animation may cover the speaker's face or important on-screen content. Verify it on real frames after every render.
6. Copyright-safe assets only. Use free-licence B-roll and music. Log every third-party asset in credits.md with source URL and licence, ready to paste into the video description.
7. Review before delivery. Never hand back a render you have not inspected frame by frame (Step 4).

Tools