mcpField
Y
yt-edit

yt-edit

github.com/jakeschincariolCreative & media3.5k488 installsUpdated 6w ago
Repository

About yt-edit

yt-edit analyzes timestamped transcripts and produces a cut list for video editors. It flags long pauses, filler-only cues, and restarted sentences, while leaving media edits to the user.

Key features

  1. 01Finds long pauses
  2. 02Flags filler-only cues
  3. 03Detects restarted sentences
  4. 04Outputs suggested cuts

Use cases

  1. 01Reviewing a spoken take for pauses
  2. 02Finding filler words before editing
  3. 03Checking restarted lines in a transcript

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jakeschincariol/youtube-agent-skill --skill yt-edit

After installing, type/yt-editin Claude Code to confirm it loaded.

Bundled filesdeadair.py

Details

From the project README

yt-edit

An edit decision list from a timestamped transcript. It prints the cuts. You apply them.

python3 deadair.py transcript.srt              # srt, vtt or whisper json
python3 deadair.py transcript.srt --floor 0.35 --json

No transcript yet? Ask for one, or produce one first - whisper, faster-whisper, or the caption track YouTube generates on an unlisted upload all work. Do not guess at timings.

What it finds

  • DEAD - gaps longer than the floor, trimmed from the MIDDLE so both sides keep a breath. Cutting flush against speech is what makes a tightened take sound gasping.
  • FILLER - cues that are nothing but "um", "so yeah", "basically".
  • REPEAT - a sentence restarted. Compared against the last cue that was actually speech, not the literal previous cue, because most retakes have an "um" between the two attempts.

What it will not do

It does not touch media. It has no opinion about your B-roll. A 40% cut on the report is a 40% cut of SPEECH, and if the video has a long silent demo in it that number is wrong - check the report against the footage before you trust the runtime at the bottom.

The gate

Nothing here publishes. This skill writes and you publish. Every output ends in a block the user copies, and the last line of every run is the question: ship it, or change it?

Comments

Markdown supported