agentleFS
mrpaidsocialmrpaidsocial/mrpaidsocial-video-editor-agent/.claude/skills/edl-tighten/SKILL.md

edl-tighten

Skill168 starsChanged 5 days agoNo licenceView on GitHub

Surgically remove awkward pauses, dead air, and long silences from a FINISHED voiceover-driven cut while keeping video, VO audio, word-synced captions, SFX hits, and the composition timeline in sync. Use when asked to "tighten the cut", "remove the pause at 0:41", "cut the dead air", "the gap between sentences is too long", "shave the silences", "it drags here", or when a revision round adds new cuts to an already-tightened edit. Finds gaps two ways (silencedetect + RMS envelope), chooses frame-quantized cut windows that never clip speech onsets, masks splices at cuts or attention magnets, executes ONE trim/concat filtergraph per stream from the original source, remaps the transcript through the EDL with scripts/remap-transcript.py (never re-whisper), and verifies with a re-scan plus frame extraction. Needs ffmpeg/ffprobe + python3 only. Not for building the edit itself (branded-ad-edit / talking-head-recut) or QA of a render you didn't cut (video-qa).

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.