Rough Cut logo

Rough Cut

Community
appariciojunior
rough-cut

Editorial rules for choosing what to keep in talking-head footage (retakes, false starts, spoken notes to the editor, fillers) and the keep-list / moments formats that a planner script turns into frame-exact cuts. Use when deciding a cut, revising one from feedback, or writing keep.json.

Overview

Publisherappariciojunior
Repositoryvideo-editor-skills
Skill namerough-cut
Stars
360
Forks
50
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by appariciojunior on GitHub. Read the source before you install it.

Installation

Install the Rough Cut AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/appariciojunior/video-editor-skills/tree/main/skills/rough-cut
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/appariciojunior/video-editor-skills.git /tmp/video-editor-skills
mkdir -p .claude/skills
cp -r /tmp/video-editor-skills/skills/rough-cut .claude/skills/rough-cut
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Rough Cut in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Rough Cut on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Rough Cut is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Rough cut: what stays

You decide what stays, by word index. A planner script decides where each cut lands (pads, waveform checks, pause shortening, frame snapping). Never do its job by hand.

The brief creators give: remove retakes and silences, keep it feeling like a natural vlog. Not a jump cut every second.

Read first

The manifest, then every clip's word list in order. Each token: {i, text, start, end, type} with type word or audio_event ("(laughs)", "[lighter click]"). Read it as a story before deciding anything.

Rules

  1. Retakes: keep the best complete take, usually the last. Never keep a take that trails off. Cut the restart cue with it ("let me do that again", a swear at themselves).
  2. False starts: cut an abandoned sentence plus its restart cue.
  3. Spoken notes to the editor ("editor, roll the video here", "this slide is a video"): cut them and write each as a note moment → becomes a pink marker on the join where it was.
  4. Fillers stay. It's a vlog. Only cut a filler that is clearly dead air on its own. Stumbles inside a word stay (cutting them makes a visible jump).
  5. Keep their voice: asides, jokes, a laugh, a deliberate pause before a point.
  6. Pauses are not your job. Give whole thoughts as one range; the planner shortens long pauses.
  7. Keep recorded order unless asked.
  8. Unsure? Keep it and flag it. A wrong cut is invisible to the creator; a flagged keep is a 5-second decision. Typical flags: near-identical lines in a row (deliberate repetition or retake?), self-corrections, a joke about "starting this three times".

keep.json

json
{
  "segments": [
    {"clip": "C0001", "from": 12, "to": 57, "why": "opening, second take"},
    {"clip": "C0002", "broll": true, "in": 0.0, "out": 4.0, "why": "camera goes into the bag"}
  ],
  "flags": [{"clip": "C0001", "at": 141, "note": "kept a stumble, check it"}],
  "summary": "3-6 lines in plain words"
}

from/to are inclusive word indices. B-roll segments are by seconds (see broll). Optional per range: lead_in / tail seconds of room (see vlog-pacing).

moments.json

json
{"moments": [
  {"type": "note", "clip": "C0001", "from": 1964, "to": 1994, "label": "VIDEO: product demo", "note": "Roll the demo here. They said: '…'"},
  {"type": "punch", "clip": "C0001", "from": 812, "to": 818, "label": "the line that lands"}
]}
  • note: covers the cut words; the marker goes on the join.
  • punch: a real punchline (conclusion, payoff, strong opinion), about one every 2–3 minutes. The picture pushes in to 115% for that line only, then goes back.

After planning

Read the review file once: struck-through text must be only what you meant to cut. Report: raw vs cut length, pieces, every retake removed (timestamp + gloss), every note, every flag.

Revisions

Creators speak in timeline times ("cut 02:14 to 02:20"). Map to word indices with the review file, edit the keep-list, re-plan, rebuild as a new version, and report only what changed.

Frequently asked questions

What does the Rough Cut AI skill do?

Editorial rules for choosing what to keep in talking-head footage (retakes, false starts, spoken notes to the editor, fillers) and the keep-list / moments formats that a planner script turns into frame-exact cuts. Use when deciding a cut, revising one from feedback, or writing keep.json.

Why use Rough Cut on TypingMind?

Because you install it once and use it with any model. Rough Cut is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Rough Cut in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/appariciojunior/video-editor-skills/tree/main/skills/rough-cut. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Rough Cut?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Rough Cut?

As many as you like. As long as a model supports skills, you can use Rough Cut with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Rough Cut AI skill free?

It is published on GitHub by appariciojunior. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇