speech-aware-cutting
Skill7 starsChanged 20 days agoMITView on GitHub
Choose the moments of talking footage worth keeping and cut them so no one is clipped mid-sentence - the transcript sets every in and out, the watch picks what is worth it - then read the cut as the viewer will hear it with scripts/review_cuts.py, which flags chopped words, filler and seams that open on "but" or "she", with the time to move each edge to. Use when cutting a short, a reel or highlights from an interview, podcast, vlog, talk or any footage where people speak, and when a finished cut sounds choppy.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- PicsArt/media-studioedited, first seen Nov 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- PicsArt/media-studio★ 1100% same
Wrote their own version · 0
None found.
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 repository69 other files it gives its agents.
- ai-presenterSkill
- animate-designSkill
- app-ui-animationSkill
- asset-auditSkill
- assetsSkill
- background-musicSkill
- caption-decorationsSkill
- character-riggingSkill
- custom-transitionsSkill
- design-layer-importSkill
- drama-series-writingSkill
- edit-footageSkill
- edit-on-your-computerSkill
- edit-pipelineSkill
- face-hidingSkill
- figma-storyboard-animationSkill
- film-animaticSkill
- film-cast-designSkill
- film-cuttingSkill
- film-finishingSkill
- film-shot-generationSkill
- film-story-writingSkill
- footage-analysisSkill
- footage-reframingSkill
- generate-mediaSkill
- get-startedSkill
- large-scene-assemblySkill
- linked-element-motionSkill
- make-cartoonSkill
- make-characterSkill
- make-comicsSkill
- make-screen-videosSkill
- make-short-dramaSkill
- motion-design-craftSkill
- motion-intentSkill
- motion-pattern-librarySkill
- motion-reviewSkill
- motion-scene-continuitySkill
- motion-tracking-from-videoSkill
- movie-producerSkill
- open-picsart-appSkill
- photo-slideshowSkill
- picsart-add-mediaSkill
- picsart-video-rulesSkill
- quality-reviewSkill
- quick-merge-and-exportSkill
- realistic-color-gradeSkill
- recastSkill
- recreate-videoSkill
- reel-structureSkill
- reference-fragment-matchingSkill
- resting-frame-rulesSkill
- retention-hooksSkill
- scene-3d-authoringSkill
- scene-animation-referenceSkill
- scene-building-basicsSkill
- scene-template-remixSkill
- screen-recording-analysisSkill
- screen-recording-layoutsSkill
- screen-recording-zoomSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Read every source as the footage-analysis skill says for talking footage: a transcript kept as the tool returned it (transcript-<source …
- Very specific: line 40
Write the plan as the reel's clip list, the one the footage-reframing skill's scripts/reel_cut.py reads, with each spoken source's …
- Very specific: line 45
Run python3 scripts/review_cuts.py reel.json on that same file.
- Very specific: line 69
Read the script yourself too, as prose, for what is clunky.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Speech cuts
A short cut from talking footage lives on its words. The framing can be perfect and the short is still unwatchable when it opens on half a sentence or spends its first two seconds on "yeah, no, totally". So the cut is planned from what is said, and checked as what is heard, before anything is built.
Read the footage
Read every source as the footage-analysis skill says for talking footage: a transcript kept as the
tool returned it (transcript-<source id>.json where you run commands), which sets every boundary, and a watch, which picks the moments. A photo has no speech
at all: it is a beat, not a backbone.
Plan the cut
- One pool of moments. Take the watch's candidate moments from every source into one list, each with the source it came from: its times count on that source's clock, as the footage-reframing skill says.
- Snap each to whole thoughts. A clip's
inis a sentence's first word, or a word after a real pause; itsoutis a sentence's last word, or a word before one. The transcript'scutPointsmark the clean ends. - Order and trim to the target. Order the moments by their loops, as the retention-hooks skill says. Aim for the target length within about 15%. When the length and a clean sentence conflict, the sentence wins and the length moves. Never cut a word out of a sentence to save time: the ear hears the splice at once, where the eye would forgive a picture cut.
- Place photos at sentence edges, never inside one, each held long enough to read.
- Keep what the user saw work. A recut or a fix starts from the last version the user saw,
never from zero. Every moment they liked stays, with the picture it had; a fix for a constraint
(a clipped word, a pause, the length) moves an edge, never swaps the moment for another. A
moment dropped, moved or given a new picture gets one line in the message to the user. Where
the use case keeps the edit-pipeline record, its keepers ledger and
scripts/meaning_diff.pydo this, as the edit-pipeline skill says.
Write the plan as the reel's clip list, the one the footage-reframing skill's scripts/reel_cut.py reads,
with each spoken source's transcript beside its other fields (its file path, where you run commands).
Review it as heard
Run python3 scripts/review_cuts.py reel.json on that same file. It joins each clip's words in
play order into the heard script, and checks three things per clip:
| Check | Fails when | Its repair |
| Integrity | an edge cuts through a word, or the clip opens or stops mid-sentence | move that edge to the time given |
| Substance | most of the clip is filler; the opening clip is held to a stricter share | drop it, or take the sentence beside it |
| Fluency | a clip opens on a connective ("but", "so") with nothing before it, or the reel opens on a pronoun no one has been named for | move the in point back to what it refers to, or lead with another clip |
| Context | a clip opens on an answer ("Yes", "Exactly") whose question the cut drops | move the in point back to the question |
Each clip also lists the speakers its words carry. Use them when the footage-reframing skill asks who a
clip should hold on.
The review also returns context: each name the reel says for the first time, each "she" or "that"
right after a seam, each "as I said", and each seam that jumps far in its source, with the second of
the reel it is heard at and, when the cut drops it, what the source said first. These are not faults.
They are the places a listener who knows only the reel may get lost.
Then have the script read cold. You know the whole footage, so you cannot hear what is missing.
Have it read on paper as the quality-review skill's cold watch says, its calls quoted first as it
says: a SPEND (quote it in one line, then get the yes with your host's own question tool, such as AskUserQuestion, "Yes, go ahead" / "Yes, up to N credits for this task" / "No", never as a typed question; only where the host has no such tool, those options numbered in one message; unless a spend limit the user stated covers it: N credits or an explicit no-limit ("as much as needed"), never inferred from words like "go ahead". Within it, ask nothing: quote it in one line ("About 8 credits; 12 of 20 left after this"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) before the first read unless every call is quoted at 0 credits. Each row a clip's time in the
reel and its heard words, so readers who know nothing read it up to each moment and say what they
understood. Check their account at each context time: did they know who or what it was? Where
they did not, keep the setup or lead with another clip.
Read the script yourself too, as prose,
for what is clunky; whether a clean clip is worth its seconds is your call.
Apply the repairs to the plan and run it again until it is clean. A repair changes numbers in a plan, so it costs nothing. The review never blocks the cut: if every candidate is thin, build from the strongest and say so in one line.
A clip it marks silent (a photo, a shot with no transcript) is a beat of silence in the heard
script. A segment the transcript returned without word times is checked only at its sentence
edges, and the review says so.
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.

