Avenox Roughcut logo

Avenox Roughcut

Community
avenoxai
avenox-roughcut

Avenox Studio — transcript-driven rough cut (silence + flub/retake removal). Use when cutting a raw talking-head or screen recording: remove dead air AND bad takes/restarts. Proven recipe with real gotchas baked in. Triggers: "rough cut", "cut the silences", "remove flubs/retakes", a raw screen recording to trim. Part of avenox-video step 2.

Overview

Publisheravenoxai
Repositoryavenoxskills
Skill nameavenox-roughcut
Stars
105
Forks
6
Bundled files
Instructions only
LicenseMIT
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 avenoxai on GitHub. Read the source before you install it.

Installation

Install the Avenox Roughcut 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/avenoxai/avenoxskills/tree/main/skills/avenox-roughcut
  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/avenoxai/avenoxskills.git /tmp/avenoxskills
mkdir -p .claude/skills
cp -r /tmp/avenoxskills/skills/avenox-roughcut .claude/skills/avenox-roughcut
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Avenox Roughcut 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 Avenox Roughcut 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 Avenox Roughcut 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 — transcript-driven (silence + flubs)

Two kinds of cut: silence (dead air, mechanical → auto-editor) and flubs/retakes (a restarted sentence, semantic → transcript + agent judgment). The director approves the flub list before anything is cut.

Pipeline

Job dir (LOCAL — never inside a synced/cloud folder): $STUDIO_JOBS/<job>/{raw,cut,transcript,frames}

Set STUDIO_JOBS to wherever you keep heavy media, e.g. export STUDIO_JOBS=~/video/projects. Keeping media out of a synced folder matters: cloud sync will thrash on multi-GB intermediates.

1. Transcribe (local mlx-whisper — Apple Silicon)

bash
cd "$STUDIO_JOBS/<job>"
python3 -c "
import os, certifi; os.environ['SSL_CERT_FILE']=certifi.where(); os.environ['REQUESTS_CA_BUNDLE']=certifi.where()
import mlx_whisper, json
r=mlx_whisper.transcribe('<RAW>', path_or_hf_repo='mlx-community/whisper-large-v3-turbo', language='<LANG>', word_timestamps=False)
segs=[{'i':i,'start':round(s['start'],2),'end':round(s['end'],2),'text':s['text'].strip()} for i,s in enumerate(r['segments'])]
json.dump({'text':r['text'].strip(),'segments':segs}, open('transcript/raw_timed.json','w'), ensure_ascii=False, indent=1)
"

~48s for 14 min of audio on an M-series Mac. Local is the default — it is faster and cheaper than any API round trip at this length. Note that most LLM-routing proxies have no whisper endpoint; if you must go remote, use a dedicated speech API.

2. Detect flubs (read transcript, propose to the director)

Scan raw_timed.json for:

  • repeated sentence-starts (the same opening said twice)
  • cut-off restarts (a half sentence, then the full take)
  • self-corrections ("we need X" → "instead of X, …")
  • hanging filler words right before a gap

Present as a table (mm:ss + text). The director approves before cutting. This step stays human-gated — an agent cutting semantic content unreviewed will eventually remove a real point.

3. Cut — flubs (ffmpeg) THEN silence (auto-editor)

Order matters: flub timecodes are in RAW coordinates, so cut flubs first; silence removal shifts the timeline underneath them.

Flubs via ffmpeg select (frame-precise; build KEEP as the complement of the cut ranges):

bash
KEEP="between(t,4.96,46.16)+between(t,48.98,69.42)+...+between(t,LAST,99999)"
ffmpeg -y -i "<RAW>" \
  -vf "select='$KEEP',setpts=N/FRAME_RATE/TB" \
  -af "aselect='$KEEP',asetpts=N/SR/TB" \
  -c:v h264_videotoolbox -b:v 18M -c:a aac -b:a 256k cut/flubcut.mp4

Silence via auto-editor:

bash
export SSL_CERT_FILE="$(python3 -c 'import certifi;print(certifi.where())')"; export REQUESTS_CA_BUNDLE="$SSL_CERT_FILE"
python3 -m auto_editor cut/flubcut.mp4 --edit "audio:threshold=8%" --margin 0.5s \
  -c:v h264_videotoolbox -b:v 16M --no-open -o cut/draft_v1.mp4

Gotchas (learned the hard way — do not rediscover)

  • auto-editor needs the certifi SSL fix or its binary download fails with CERTIFICATE_VERIFY_FAILED. Always export SSL_CERT_FILE first.
  • Do NOT use auto-editor --cut-out for flubs. In v29 a multi-range --cut-out a,b c,d … leaks the last range as a positional input file ("Could not open input file"). Use the ffmpeg select filter for content cuts — it is also frame-precise, where auto-editor's cuts are coarser.
  • Pause length is --margin, not --threshold. 0.15s ≈ very tight (~0.3s pauses); 0.5s ≈ ~1s max pauses, which reads as flowy rather than clipped. Tune margin for rhythm, leave threshold alone.
  • threshold=8% is calibrated to one specific voice/mic. Re-calibrate for your own setup: too low clips soft word-endings, too high leaves dead air.
  • The auto-editor binary is a WyattBlue release, auto-downloaded by the pip wrapper into its own cache.

Output & next

  • Render the draft with hardware encoding (h264_videotoolbox) for fast review; produce the master later via mltgen/.mlt, or a single-pass keep-list at libx264 CRF 18.
  • After cutting, re-transcribe the cut (or remap timecodes) so graphics land accurately → hand to the avenox-video graphics step.
  • Show the director the draft. They are the quality gate.

Frequently asked questions

What does the Avenox Roughcut AI skill do?

Avenox Studio — transcript-driven rough cut (silence + flub/retake removal). Use when cutting a raw talking-head or screen recording: remove dead air AND bad takes/restarts. Proven recipe with real gotchas baked in. Triggers: "rough cut", "cut the silences", "remove flubs/retakes", a raw screen recording to trim. Part of avenox-video step 2.

Why use Avenox Roughcut on TypingMind?

Because you install it once and use it with any model. Avenox Roughcut 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 Avenox Roughcut in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/avenoxai/avenoxskills/tree/main/skills/avenox-roughcut. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Avenox Roughcut?

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 Avenox Roughcut?

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

Is the Avenox Roughcut AI skill free?

Yes. It is published on GitHub by avenoxai under the MIT license. 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 👇