long-form-editor
Skill4 starsChanged 33 days agoMITView on GitHub
Edit raw talking-head takes into a finished YouTube long form - transcribe, build a word-snapped cut list, grade and punch in on the A-roll, add word-synced motion graphics, generate original music and sound effects, mix and render one final file. Use when someone hands over raw takes and asks for an edit.
- Installs packages
In this repository4 other files it gives its agents.
- interview-shot-sheetSkill
- shorts-cutterSkill
- video-quality-checkSkill
- youtube-metadataSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Run everything from editor/.
- Very specific: line 22
Find the story: Read every transcript. Write segs.py: (section, take, first-word start, START of last word[, hard out[, hard in]]).
- Very specific: line 30
Graphics: write g/_content.js (see example_content.js), assemble part2.js = _infra.js + _content.js + _tail.js, then node check.mjs.
- Distinctive: line 40
Never put a number on screen that wasn't said or verified.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Long-form editor
Everything is code, so every change is repeatable: a note like "music's too loud" becomes one number in one script.
Folder layout
<video>/raw/ IMG_xxxx.MOV takes (+ screen recordings)
<video>/editor/ these scripts (copy from scripts/)
<video>/final/ output + upload textRun everything from editor/. Needs ffmpeg, Python (numpy scipy soundfile pillow faster-whisper), Node + playwright (npm i playwright && npx playwright install chromium).
Steps
- Check the footage first with the
video-quality-checkskill (HDR? full range? dim?). FixTM/GRinbuild.pyto match. - Transcribe. Extract 16 kHz mono to
tr/IMG_x.wavand 48 kHz stereo toa48/IMG_x.wav, thenpy tr.py IMG_x ...(Whisper with word timestamps). - Find the story. Read every transcript. Write
segs.py:(section, take, first-word start, START of last word[, hard out[, hard in]]). Chapter slots are('CARDn', None, seconds).- Hook first: the result, then the promise. Cut stammers and repeated phrases; prefer the clean re-say.
- Re-transcribe a 5–10 s clip whenever a timing looks wrong. Whisper merges repeats and invents words in silence.
py edl.py→plan.json. Cuts snap to the quietest 10 ms near word edges, and pauses over 0.6 s shrink to 0.3 s.py words.py→ word times on the output timeline (g/words.js).py build.py→ graded, range-converted, punch-in A-roll (aroll.mkv). Set the face position per take inFACEso zooms stay centred.py voice.py→voice.wav(crossfaded joins, EQ, de-ess, gentle compression, ~-14.5 LUFS).- QA the cut: re-transcribe
voice.wavand read it start to finish. Fixsegs.pyand repeat 4–8 until it reads clean. - Graphics: write
g/_content.js(seeexample_content.js), assemblepart2.js = _infra.js + _content.js + _tail.js, thennode check.mjs.block(section, 'start phrase', 'end phrase', html, {side}). Children withdata-at="phrase"reveal on that word.- One graphic at a time, opposite side from the face, never over it. Render sample frames and look at them before the full render.
py music.py→ original score + sound effects timed to the sections and graphics (no licensed music needed). Thenpy mix.py→ music ~20 dB under the voice, oversampled true-peak limiter.- Render graphics: in
g/, runnode render.mjs <from> <to>in 3–4 parallel chunks. py final.py→ one composite pass, CRF 14 slow, AAC 320k.
Taste rules
- One focal point on screen. No subtitles top and bottom at the same time.
- Graphics say less than the voice: 2–4 words big, one small line under.
- Never put a number on screen that wasn't said or verified.
- Chapter cards between steps; a short end card.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

