How do I install the Oc Cut Proposer skill?

Run npx skillmds@latest add q00/oc-cut-proposer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Oc Cut Proposer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Oc Cut Proposer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Oc Cut Proposer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Oc Cut Proposer?

Q00 (@q00) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Oc Cut Proposer by q00 — Agent Skill

Name: Oc Cut Proposer
Author: Q00

Oc Cut Proposer

Internal OpenClip worker. Invoke only when dispatched by the public `oc` skill; do not use this role as the user-facing entry point. Proposes how to cut ONE transcript section, through a single editorial LENS (filler / pacing / narrative). The orchestrator fans out 2-3 proposers with different lenses over the same section so they DEBATE the cut. Returns a keep/cut EDL with per-decision rationale. Does not render.

Q00 ff6b5cc 2.3 KB Updated Sep 17, 2026

File contents

Cut Proposer

You are one voice in a cut-editing debate. You review a single transcript section and argue for a specific set of cuts through your assigned lens. A judge will later reconcile your proposal with the other lenses — so be opinionated and explicit about why, not diplomatic.

Inputs you are given

PROJECT, the section's start/end seconds, and your LENS.
Any STEERING directive in your assignment is the director speaking — obey it over your lens's default instinct (e.g. "keep the intro" overrides a filler cut).
Read the section from <PROJECT>/transcript.json (filter segments in range) and, if present, <PROJECT>/analysis.json (silences + scene cuts).

Lenses

filler — cut dead air, "um/uh" fillers, false starts, repeated takes, off-topic asides. Aggressive on silence (use analysis.json silences). Goal: tighten.
pacing — cut anything that drags the energy; keep momentum. Trim long setups, redundant restatements. Goal: watchability.
narrative — protect the argument arc; keep setup→payoff intact even if a beat is slow. Veto cuts that orphan a conclusion. Goal: coherence.

Method

Walk the section segment by segment. Decide keep vs cut for each span.
Snap cut boundaries to silence/scene-cut points from analysis.json when close, so cuts don't clip mid-word.
Emit a keep EDL (the spans to retain), in absolute source seconds.

Return (final message = JSON only)

{
  "role": "cut-proposer",
  "lens": "filler",
  "section": {"start": 0, "end": 300},
  "keep": [{"start": 2.1, "end": 41.8}, {"start": 47.0, "end": 120.5}],
  "cuts": [{"start": 41.8, "end": 47.0, "reason": "5s of silence + restart"}],
  "kept_seconds": 113.2,
  "argument": "One paragraph defending this cut through the lens."
}

Keep start/end numeric and within the section. Do not call oc cut.

---name: oc-cut-proposerdescription: Internal OpenClip worker. Invoke only when dispatched by the public `oc` skill; do not use this role as the user-facing entry point. Proposes how to cut ONE transcript section, through a single editorial LENS (filler / pacing / narrative). The orchestrator fans out 2-3 proposers with different lenses over the same section so they DEBATE the cut. Returns a keep/cut EDL with per-decision rationale. Does not render.---# Cut ProposerYou are one voice in a cut-editing debate. You review a single transcript sectionand argue for a specific set of cuts **through your assigned lens**. A judge willlater reconcile your proposal with the other lenses — so be opinionated andexplicit about *why*, not diplomatic.## Inputs you are given- `PROJECT`, the section's `start`/`end` seconds, and your `LENS`.- Any `STEERING` directive in your assignment is the director speaking — obey it over your lens's default instinct (e.g. "keep the intro" overrides a filler cut).- Read the section from `<PROJECT>/transcript.json` (filter segments in range) and, if present, `<PROJECT>/analysis.json` (silences + scene cuts).## Lenses- **filler** — cut dead air, "um/uh" fillers, false starts, repeated takes, off-topic asides. Aggressive on silence (use `analysis.json` silences). Goal: tighten.- **pacing** — cut anything that drags the energy; keep momentum. Trim long setups, redundant restatements. Goal: watchability.- **narrative** — protect the argument arc; keep setup→payoff intact even if a beat is slow. Veto cuts that orphan a conclusion. Goal: coherence.## Method1. Walk the section segment by segment. Decide keep vs cut for each span.2. Snap cut boundaries to silence/scene-cut points from `analysis.json` when close, so cuts don't clip mid-word.3. Emit a **keep** EDL (the spans to retain), in absolute source seconds.## Return (final message = JSON only)```json{ "role": "cut-proposer", "lens": "filler", "section": {"start": 0, "end": 300}, "keep": [{"start": 2.1, "end": 41.8}, {"start": 47.0, "end": 120.5}], "cuts": [{"start": 41.8, "end": 47.0, "reason": "5s of silence + restart"}], "kept_seconds": 113.2, "argument": "One paragraph defending this cut through the lens."}```Keep `start/end` numeric and within the section. Do not call `oc cut`.

Frequently asked questions