trove-take-cut
Cut a raw multi-take recording down to one keeper per line. Use when the same lines were read several times and the retakes, stumbles, and dead air should go. Not for footage that is already a single take, and not for a single trim.
- License 许可
- MIT
- 所属仓库
- bravew/trove
- 最近更新
- 2026-11-12
- Stars
- ★ 10
- Forks
- 1
01 前言 Front Matter
- name
- trove-take-cut
- license
- MIT
- metadata
- { "inspired-by": "BuildLoop video skills", "trove-category": "designs-media", "trove-category-label": "Designs & media" }
- description
- Cut a raw multi-take recording down to one keeper per line. Use when the same lines were read several times and the retakes, stumbles, and dead air should go. Not for footage that is already a single take, and not for a single trim.
- when_to_use
- cut out the bad takes; keep the last take of each line; remove the retakes from this recording; tighten the pauses in this read
- user-invocable
- true
02 资源文件 4
- 参考文档references/takes.schema.json1.5 KB
- 参考文档references/words.schema.json832 B
- 脚本scripts/cut_points.py3.8 KB
- 脚本scripts/verify_cut.py2.7 KB
03 SKILL.md 正文
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run build:skills -->
Take cut
A raw recording where each line was read several times becomes one keeper per
line, joined without clicks or clipped consonants. This decides which takes
survive and where the cuts fall. Captions, music, and grading belong to
trove-video-edit afterwards, and a single trim of an already-cut file belongs
to trove-ffmpeg.
Why the cuts are not on the transcript
Word timestamps drift by up to a few tenths of a second, so a cut placed on one lands in the breath before a word or clips the consonant off it. Use the transcript for the words and for finding where each take roughly sits. Take the cut points from the waveform.
Three more rules come from the same failure:
- A breath sits just before the first word and is quieter than speech. An absolute threshold between the two skips the breath. A threshold relative to the line's loudest sample does not, because a shouted line pushes it high enough to clip the quiet word that opens it.
- Scan inward from outside the window. Scanning outward from the middle stops at a pause inside the line and cuts it in half.
- A phrase that appears twice in the result means two windows covered the same words. Durations and a glance will not show it.
Workflow
Work in a scratch directory next to the source. The source file is never modified.
-
Probe and transcribe. Read
references/runtime-spec.mdintrove-ffmpegbefore the first command, and use itsprobe.pyfor duration, frame rate, and any subtitle track. Extract a mono 16 kHz WAV, then transcribe it to word level and writewords.jsonmatching words.schema.json. The engine is the user's choice.faster-whisperwith word timestamps works. A script supplied by the user works. Do not install one they did not ask for. Recognizers drop "uh" and "um" by default, and a dropped filler hides the stumble that decides the keeper. Ask the engine to keep them. Withfaster-whisper, an initial prompt that itself contains fillers does that. Transcribe each candidate reading on its own as well, since a filler the full pass dropped often shows up when its take is transcribed alone. -
Group the readings. Each script line was read several times. Group the segments that are the same line, in order. When the user supplied the script, align to it. Otherwise take the wording of the cleanest reading as the line.
-
Pick the keeper. Default to the last reading that contains no stumble, false start, or flubbed word. Prefer a reading that is followed by a real pause in the source, because a line chopped out of a longer run keeps the rising intonation of the words that came after it. Prefer one continuous reading of several sentences over stitching them from separate takes. Record the choice in
takes.jsonmatching takes.schema.json, with a rough window around each keeper, and show it to the user before rendering. They override per line. When every reading of a line has a stumble, keep the cleanest, name the stumble in itsreason, and say so. Cutting a filler out of a kept line istrove-ffmpeg'ssilence.py --filler, run only when the user asks. -
Find the edges and render. Run
scripts/cut_points.pywith the WAV andtakes.json. It prints one{start, end}per line, scanned inward from the waveform. The default threshold suits a normally levelled voice. On a quiet recording, a soft word ending, such as the "s" in "runs", sits below it and gets clipped. When the source is gated to digital silence between words, lower--thresholdtoward that floor and confirm the last word of each line in the fresh transcript. Pass those totrove-ffmpeg'scut.py --segmentswith--accurateand a short declick, thenjoin.pyif the segments are separate files. Never write a raw ffmpeg command, and never cut on the word timestamps. -
Verify. Transcribe the result to a fresh
words.jsonand runscripts/verify_cut.py. A cut is not done until it printsCONTENT: clean. Clean means no line plays twice and the first word is on time. It does not check for fillers. On a failure, re-pick the offending line as one continuous take, re-cut, and run it again. Run it on every output, including every variation.
Pace
Gaps that still feel long are a smaller pad, not a new cut. A pause inside a kept line is the speaker's delivery. Leave it unless the user asks. Softening a join with a crossfade belongs to the edit that follows, not here.
04 同仓库更多 Skills
using-trove
Skill discipline anchor for the Trove marketplace. Loaded once per session; routes the agent to the right trove-* skill before code, planning, review, or git actions.
trove-write-skill
Skill authoring workflow. Use when creating or updating a Codex or Trove skill, including rubrics, tasks, metadata, and validation.
trove-worktree
Git worktree workflow for spikes, risky experiments, and broad refactors that should not disturb the user's current branch.
trove-why
Reconstruct design rationale and decision history from evidence — source control, issue tracker (Linear), docs (Notion), chat (Slack), error tracking (Sentry) — with calibrated confidence. Use for "why does X work this way", "why did we pick Y", regressions, and postmortems. Use trove-explain for how it works now.
trove-verify
Completion verification workflow. Use before claiming done, fixed, complete, ready, or shipped.
trove-unslop
Cut AI tells from writing — PR descriptions, release notes, specs, commit bodies, and replies. Use before finalizing prose, or when the user asks to clean up, de-slop, or make text sound human.