video-edit
Skill4 starsChanged 11 days agoMITView on GitHub
Clean up a raw screen/OBS/talk recording into a tight professional upload - transcript-driven cuts, dead-air and visual-static removal, off-limits personal moments, on-screen leak redaction, audio enhancement, strong opening, verified render, then chapters/title/tags/description/subtitles/thumbnail, delivered to ~/Downloads and opened. Use when the user says "edit the video I recorded", "cut the silence out", "remove embarrassing parts", "make sure nothing leaks", "make it YouTube ready". Not for building promo/motion-graphics videos from slides; thumbnails alone go to youtube-pack.
29 other projects use a version of this.
Adopted by
Most recently taken up by
- decwap/video-edittheir own version, first seen Nov 15, 2026
- calesthio/OpenMontagetheir own version, first seen Nov 9, 2026
- MomoFadaly/video-edittheir own version, first seen Nov 8, 2026
- YildizDikme/claude-video-edittheir own version, first seen Nov 8, 2026
- omergocmen/ai-video-edit-workflowtheir own version, first seen Nov 8, 2026
- OpenMontageInc/OpenMontagetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use flux-2-klein, flux-kontext and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
agentspace-soSkillflux-2-klein
Generate images with Flux 2 Klein (Black Forest Labs' distilled fast variant of Flux 2) on RunComfy — bundled with the model's documented prompting patterns so the skill gets sharper output than naive prompting against the same model. Documents Flux 2 Klein's strengths (sub-second latency, multi-reference brand styling, declarative subject-first prompts), the step-count strategy (4–8 for fast iteration, ~25 for polish), the 9B vs 4B variant trade-off, and when to route to Flux 2 Pro / Seedream 5 / GPT Image 2 instead. Calls `runcomfy run blackforestlabs/flux-2-klein/9b/text-to-image` (or `/4b/`) through the local RunComfy CLI. Triggers on "flux 2 klein", "flux-2-klein", "flux klein", "BFL flux 2", or any explicit ask to generate with this model.
Also in 4 projects that use this
agentspace-soSkillflux-kontext
Edit images with Flux 1 Kontext Pro (Black Forest Labs' precise local image-edit model) on RunComfy — bundled with the model's documented prompting patterns so the skill gets sharper output than naive prompting against the same model. Documents Flux Kontext's strengths (single-reference precise local edits, strong prompt control, consistent high-fidelity outputs), the schema (single image + prompt), and when to route to Nano Banana Edit / GPT Image 2 edit / Flux 2 Klein instead. Calls `runcomfy run blackforestlabs/flux-1-kontext/pro/edit` through the local RunComfy CLI. Triggers on "flux kontext", "flux-kontext", "flux 1 kontext", "kontext", "BFL kontext", or any explicit ask to edit with this model.
Also in 4 projects that use this
prime-skillsSkillace-step
Generate, inpaint, and outpaint music with ACE Step on RunComfy via the `runcomfy` CLI. ACE Step is StepFun-AI's open-weights music foundation model — tag-driven composition (genre, mood, instruments), multilingual lyrics with section markers, 5 s to 4 min stereo output, $0.0002–0.0003 per second (≈ 27× cheaper than ElevenLabs Music). Four endpoints: ACE Step text-to-audio (the default), ACE Step 1.5 text-to-audio (50+ language lyrics, refined structured-lyric handling), ACE Step audio-inpaint (regenerate a time range inside an existing track), ACE Step audio-outpaint (extend an existing track before or after). Triggers on "ace step", "ace-step", "acestep", "ACE music", "open music model", "cheap AI music", "inpaint audio", "audio inpaint", "extend music", "audio outpaint", "lengthen track", "music with tags", or any explicit ask to generate or edit music with ACE Step.
Also in 3 projects that use this
prime-skillsSkillcodex-pet
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into `${CODEX_HOME:-$HOME/.codex}/pets/<name>/` and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as `runcomfy run openai/gpt-image-2/edit` to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no `$imagegen`, no OPENAI_API_KEY required, only RUNCOMFY_TOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
Also in 3 projects that use this
- +3 more from agentspace-so
- +5 more from prime-skills
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 29
- calesthio/OpenMontage★ 81ksame name
- OpenMontageInc/OpenMontage★ 81ksame name
- hoodini/ai-agents-skills★ 295same name
- goodnight000/cstack★ 161same name
- video-db/skills★ 140same name
- tenfoldmarc/video-edit-skill★ 42same name
- prime-skills/runcomfy-agent-skills★ 41same name
- YildizDikme/claude-video-edit★ 41same name
- omergocmen/ai-video-edit-workflow★ 39same name
- nickjwells/skills-workspace★ 28same name
19 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- brain-searchSkill
- third-party-writingSkill
- youtube-translateSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
Never modify the source recording.
- Very specific: line 48
Always end with: move to ~/Downloads + open.
- Distinctive: line 51
When asked to free space: delete old unaccepted drafts/variants, keep the source and the final.
- Very specific: line 53
Never claim the edit is done because the render finished.
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Video edit (screen / OBS / talk recording)
Script kit: scripts/ in this skill (prep.sh, transcript_txt.py, ocr_scan.py,
cam_flags.py, df_enhance.py, build_edl.py, render.py, verify_output.py,
chapters.py, overview.py, job.example.json, selftest.sh). Run them from a copy in
<workdir>/scripts/ so a job never depends on the skill dir. scripts/selftest.sh proves
an install end to end in a couple of minutes.
Inputs
<src>: the recording, usually newest~/Desktop/*.mov(OBS namingYYYY-MM-DD HH-MM-SS.mov). If several recent recordings exist, confirm which one BEFORE starting the long pipeline - editing the wrong video wastes an hour.<target_minutes>: ask if not given; typical 20-30 from a 45-90 min source.<workdir>: fresh scratch dir, e.g./tmp/<session>/edit.- Toolchain:
ffmpeg6+,python3,mlx_whisper, DeepFilterNet3, Pillow/numpy/soundfile, Apple Vision (pyobjc-framework-Vision/-Quartz).
Steps
- Recon, never touch the source.
ffprobe <src>(resolution, fps, audio). Work only from copies/extracts in<workdir>. - Prep.
prep.sh "<src>" $W:orig48.wav,mono16.wav,frames/(1 per 2 s),camall/(webcam crop at 1 fps, geometry auto-derived from the resolution),sheet_overview.jpg,silences_raw.txt(diagnostic only), andtranscript.json(mlx_whisper large-v3-turbo, word timestamps, ~4 min). Whisper keeps running in the background after prep returns - startdf_enhance.py orig48.wav df_enhanced.wav(DeepFilterNet3, ~6 min CPU) NOW, it is independent. - Read the whole transcript (3 chunks via
transcript_txt.py ... --from/--to). Write keep ranges (source seconds) intojob.json -> keep. Silence trimming is minor (~2 of 47 min); the real minutes come from content decisions. Whisper self-informs: a phrase repeated 10+ times or empty-segment runs = dead air, cut it. - Visual-static pass. "Nothing happening" is often visually static, NOT silent. Frame-difference the 0.5 fps frames: <1% pixels changed over a ~10 s window = inactive; merge runs split by <=1 s blips; require >=4 s to cut; 0.5 s handles. Blinking cursors/spinners fake activity - mask or raise the threshold; check intermediate frames for change-and-revert bursts. Typing is noise, not silence: gates use RMS on the enhanced track (
pause.loud_db), never rawsilencedetect. - Opening. Cut everything before the first real content. If the start is slow/boring, start on the most interesting demo; optionally cold-open with 1-2 exciting clips then a speed-up of the intro. Never open on wallpaper/black - a choppy first 30 s reads as trash.
- Leak scan (runs while you read).
ocr_scan.py scanafterrunonframes/: IPv4/v6,*.ts.net, emails, API keys, ssh material. Dense 2 fps pass on every terminal/config-heavy range (ocr_scan.py dense src.mov dense 600:60 ...). Static text ->boxes(solid fill); scrolling terminal output -> blur the whole pane (blurwindow +blur_regions, in source pixels) for the window - per-line boxes miss text between samples.127.0.0.1/localhostare fine. Log every window injob.json. - Privacy cuts (webcam).
cam_flags.py(hand-near-mouth via Vision) +cam_flags.py --sheet S:DURzoomed 2 fps sheets of each flagged cluster. Cut the moments the user would not publish: hand at the face during a pause, leaving the desk, another person in frame, full-screen face segments. Ordinary thinking poses and small gestures are fine. NEVER cut mid-sentence for a gesture - snap to the nearest sentence boundary and note what was lost. - User timestamp cuts are literal. "cut 0000 - 01:12" -> put it in
job.cuts(orkeep), apply exactly, then re-check pacing around the seam. - Audio master. Sanity: enhanced-vs-original correlation > 0.95 (
df_enhance.pyprints it). The defaultaudio_chainis highpass 75, cuts/boosts around 220 Hz / 3.2 kHz / 9 kHz, de-esser, 3:1 compressor; notch any persistent fan tone by adding anequalizerterm;render.pydoes the two-pass loudnorm to -16 LUFS / -1.5 dBTP. The untouched mic stays as audio track 2. - EDL + render.
build_edl.py->segments.json(pauses >0.7 s inside keeps shortened to 0.4 s; snapped to the probed frame rate; <0.3 s dropped).render.py: grouped parallelh264_videotoolboxencodes, concat-c copy, mux both tracks. It is restartable per group - if a group fails, fix and rerun, unchanged groups are skipped. Deliver 1080p unless asked otherwise (4K doubles render time for nothing). - Verify before delivering.
verify_output.pyexits non-zero unless frame count matches the EDL, both audio tracks match the video duration, and OCR of the output at 4 fps across every redaction window finds zero leaks. Also pull output frames at each privacy cut and at 0:00-1:00 and LOOK at them. Use--fullfor a whole-file leak sweep when the material is sensitive. - Re-transcribe the new cut. Transcript, subtitles and chapters must match the OUTPUT timeline, not the source - re-whisper the cut (or
chapters.py, which remaps through the EDL) before writing SRT/chapters. Never ship SRT times taken from the source transcript. - Metadata + deliver. Without being asked twice: chapter timestamps (
chapters.py, >=3, first at 0:00), 2-3 title options, ~30 tags under 500 chars (+2 tag/description variants if asked), description, SRT per language (~42 chars/line; multilingual on request), all as plain text. Thumbnail via youtube-pack: read the user's last 10 thumbnails for style; default white/creme background + black text, no face unless asked, logos/text big and uncluttered. Then move<output>.mp4(and SRTs/metadata) to~/Downloadsandopenthe file / open the folder in default app.
Outputs
<Topic> - YYYY-MM-DD - edit.mp4(1080p, 2 audio tracks) in~/Downloads, opened in the default app.<workdir>:job.json,segments.json,group_bounds.json,vf_<n>.txt, redaction/privacy logs.~/Downloads: SRTs,metadata.txt(titles, description, tags, chapters).- Optional on request: topical sub-videos split from the same source, each with its own chapters.
Composes with
whisper/DFN3 (in-kit) -> video-edit (verified mp4 in ~/Downloads) -> youtube-pack (thumbnail.png) -> browser upload to YouTube Studio configured like the user's other videos.
Rules
- Never modify the source recording.
- Target length is a target; if content won't shrink without gutting the talk, deliver slightly over and name the next two cuts.
- Cut whole tangents before trimming more pauses; keep hardware talk, live demos, honest caveats, the recap.
- Always end with: move to ~/Downloads + open.
- Report faithfully: you cannot hear the result - say so and point at track 2.
- Separately recorded audio (Discord/Craig) usually does not exist; check Desktop/Downloads/iCloud/Voice Memos, if absent use the OBS mic and say so.
- When asked to free space: delete old unaccepted drafts/variants, keep the source and the final.
- Multi-person podcasts: find the RIGHT audio tracks (usually 2 of many), map audio to the correct speaker, alternate video with the person talking, clean transitions.
- Never claim the edit is done because the render finished; only
verify_output.py+ eyeballed frames settle it.
Verify
verify_output.pyprints PASS (frame count, two audio tracks, no leaks in windows) and exits 0.- Eyeballed frames at 0:00-1:00 and every privacy cut (
verify_output.py --sheet 0:60). - SRT re-transcription spot-check against the cut.
ffprobethe delivered file: duration, resolution, fps, 2 audio streams.
Known failures
- Wrong video edited -> confirm newest/topic match before the pipeline.
- Subtitles/chapters on the source timeline -> re-transcribe after cutting (step 12).
- Hostname visible in output -> scrolling text between OCR samples; blur whole pane, widen the window, then output-side OCR.
- Silencedetect cuts typing/video playback -> gate on enhanced-audio RMS (
pause.loud_db), not silence alone. - Choppy black opening -> verify output 0:00-1:00 frames, cold-open on real content.
cp -ioverwrite prompt / sandbox TCC blocks~/Downloads-> use/bin/cpwith sandbox disabled.- ffmpeg filter dies ("Cannot allocate memory") past ~100
between()terms -> fewerrender_groups. - Blinking cursor counts as activity in frame differencing -> mask/tune threshold, check intermediate frames.
render.pyframe mismatch -> it refuses to concat; readrender_<n>.log(-ssbefore a non-keyframe, broken decoder).- Whisper still running when you read
transcript.json->transcript_txt.pyreports empty segments; wait forwhisper.logto finish.
Examples
- 2026-09-02 talk, 47 min -> 26 min: 32 keep ranges, 2 privacy cuts (9:52-9:58, 26:08-26:14), 2 blur windows + 1 box for a
*.ts.nethostname, render ~2 h wall clock, leak caught only by output-side OCR. - 2026-09-24 teaching OBS session: user rejected first cut ("background noise, typing, beginning highly boring") -> removed typing noise, picked a better opening, re-did transcripts, then literal head cut
0:00-1:12, leak scan, white/creme thumbnail with bigger logos, 2 metadata variants, moved to Downloads. - Podcast (2026-09-18): 1h40m video + 5 candidate audio files -> identified the 2 right per-speaker tracks, mapped voice to video, 1080p, trim head, SRT + ES/AR/HI translations, chapter timestamps, thumbnail with both speakers, text on top, no black background.
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.

