Other

AudioEditor

AI audio editing pipeline: Whisper word-level transcription → Claude segment classification (KEEP/CUT_FILLER/CUT_FALSE_START/CUT_STUTTER/CUT_DEAD_AIR) → ffmpeg with 40ms qsin crossfades and room-tone fill → optional Cleanvoice cloud polish; plus GateScan/GateRepair for noise-gate ticking artifacts.

01
Workflow
08
Tools
00
References
14
Triggers

The Problem

Raw recordings are full of garbage: filler words, dead air, false starts, stutters. You can manually edit in a DAW, but that takes hours per episode and you still end up making judgment calls on every pause — is that silence rhetorical or accidental? Generic AI transcription tools will give you a transcript but won't touch the audio. And most automated cutters are blunt: they'll slice out a deliberate pause for effect the same way they cut a dead-air gap where you lost your train of thought.

How This Skill Approaches It

Run the full pipeline: Whisper transcribes at word-level timestamps, then Claude classifies each segment as KEEP, CUT_FILLER, CUT_FALSE_START, CUT_STUTTER, or CUT_DEAD_AIR — distinguishing a rhetorical pause from accidental silence before any cut is made. ffmpeg executes the edits with 40ms qsin crossfades at every cut point and fills gaps with extracted room tone so the edits don't click. Breaths get attenuated to 50% rather than removed, because fully cutting them sounds unnatural. An optional Cleanvoice API pass handles mouth sounds and loudness normalization. Three modes let you tune aggressiveness: --preview shows proposed edits before touching the file, --aggressive tightens thresholds for denser cleanup, --polish adds the Cleanvoice final pass.

  • Modes: --preview, --aggressive, --polish
  • Workflow: Clean
Not for video composition (use Remotion)

In Action

What you say to your DA, and what the AudioEditor skill actually does.

  • You say "clean up the audio on this podcast recording"
    Runs the Clean workflow: Transcribe.ts → Analyze.ts (Claude classifies every segment) → Edit.ts (ffmpeg cuts with 40ms crossfades and room-tone fill) → outputs cleaned MP3.
  • You say "show me what edits you'd make before you touch the file"
    Runs Clean with --preview: transcribes and classifies all segments, shows the proposed cut list with timestamps and reasons, makes no changes until you approve.

Inside the Skill

The thinking, frameworks, and architecture that distinguish this skill from a generic version of the same task.

What It Does

Cleans recorded audio automatically — strips filler words, false starts, stutters, and dead air, attenuates breaths, and crossfades every cut. It transcribes the file at the word level, has Claude classify each segment (KEEP, CUT_FILLER, CUT_FALSE_START, CUT_STUTTER, CUT_DEAD_AIR), then executes the cuts with ffmpeg. An optional Cleanvoice pass adds final polish. Modes: --preview, --aggressive, --polish.

The Problem

Cleaning a recording by hand means scrubbing a waveform for every "um," half-started sentence, and three-second silence, then crossfading each cut so it doesn't click. It's slow and tedious, and a blunt auto-tool over-cuts — it kills the rhetorical pause along with the accidental one, or leaves an audible seam where it spliced. This pipeline tells deliberate pauses apart from dead air, fills gaps with room tone, and crossfades each edit, so the output sounds clean rather than chopped.

How It Works

Whisper produces word-level timestamps, Claude classifies each segment (distinguishing rhetorical emphasis from accidental repetition), and ffmpeg executes the cuts with 40ms qsin crossfades, room-tone gap fill, and breath attenuation at 50% volume rather than removal. An optional Cleanvoice API pass handles mouth-sound removal, residual filler, and loudness normalization.

Pipeline

Audio Input
 |
[Transcribe] Whisper word-level timestamps (insanely-fast-whisper on MPS)
 |
[Analyze] Claude classifies each segment:
 | KEEP / CUT_FILLER / CUT_FALSE_START / CUT_EDIT_MARKER / CUT_STUTTER / CUT_DEAD_AIR
 | Distinguishes rhetorical emphasis from accidental repetition
 |
[Edit] ffmpeg executes cuts:
 | - 40ms qsin crossfades at every edit point
 | - Room tone extraction and gap filling
 | - Breath attenuation (50% volume, not removal)
 |
[Polish] (optional) Cleanvoice API final pass:
 - Mouth sound removal
 - Remaining filler detection
 - Loudness normalization

Output: cleaned MP3/WAV

Tools

Tool Command Purpose
Transcribe bun ${CLAUDE_SKILL_DIR}/Tools/Transcribe.ts <file> Word-level transcription via Whisper
Analyze bun ${CLAUDE_SKILL_DIR}/Tools/Analyze.ts <transcript.json> LLM-powered edit classification
Edit bun ${CLAUDE_SKILL_DIR}/Tools/Edit.ts <file> <edits.json> Execute cuts with crossfades + room tone
Polish bun ${CLAUDE_SKILL_DIR}/Tools/Polish.ts <file> Cleanvoice API cloud polish
Pipeline bun ${CLAUDE_SKILL_DIR}/Tools/Pipeline.ts <file> [--polish] Full end-to-end pipeline
GateScan bun ${CLAUDE_SKILL_DIR}/Tools/GateScan.ts <file> [--json] Detect noise-gate ticking (silence-boundary steps); exit 1 on defects
GateRepair bun ${CLAUDE_SKILL_DIR}/Tools/GateRepair.ts <in> <out.mp4> --finalize [--abr 192k] Repair gate ticking; --finalize iterates until the ENCODED file scans clean
LoudnessLock bun ${CLAUDE_SKILL_DIR}/Tools/LoudnessLock.ts <in> [--out <out.mp4>] Measure or lock delivery loudness to −14 LUFS / −1dBTP (YouTube standard); self re-measures, exit 0 only in tolerance

Gate-Artifact Gate (blocking — incident 2026-07-13)

Capture-chain noise gates (recorder filters, macOS Voice Isolation) truncate audio to digital zero with no fade. Every gate close/open edge is a step discontinuity; leveling (+gain/compression) amplifies each edge into an audible tick — 774 edges in one 13-minute recording shipped in two public launch videos and drew listener complaints.

The gate, non-negotiable for any audio that will be leveled or published:

  1. Before ANY leveling/gain/compression: GateScan the raw source. Gate activity present → run GateRepair FIRST (edges smoothed at low level), THEN level. Boosting first turns inaudible edges into loud ticks.
  2. Before ANY upload/publish: GateScan the FINAL ENCODED file must exit 0. AAC encoding re-introduces steps near silence — scan the encode, not the intermediate WAV (GateRepair --finalize owns this loop).

API Keys Required

Service Env Var Where to Get
Anthropic (for analyze step) ANTHROPIC_API_KEY Already set via Claude Code
Cleanvoice (for polish step, optional) CLEANVOICE_API_KEY cleanvoice.ai Dashboard Settings API Key

Examples

Example 1: Clean a podcast recording

User: "clean up the audio on this podcast file"
-> Invokes Clean workflow
-> Runs full pipeline: transcribe -> analyze -> edit
-> Outputs cleaned MP3 with filler words, stutters, and dead air removed

Example 2: Preview edits before applying

User: "show me what edits you'd make to this recording"
-> Invokes Clean workflow with --preview flag
-> Transcribes and analyzes, shows proposed edits without modifying audio
-> User reviews edit list, then runs again to apply

Example 3: Aggressive clean with cloud polish

User: "aggressively clean this audio and polish it"
-> Invokes Clean workflow with --aggressive --polish flags
-> Tighter thresholds for filler detection
-> Cleanvoice API pass for mouth sounds and normalization

Gotchas

  • Transcription accuracy varies with audio quality. Background noise, multiple speakers, and accents reduce accuracy.
  • Cut detection is heuristic-based. Always preview edits before committing — automated cuts can remove intentional pauses.
  • Cloud polish uploads audio to external service. Confirm the user is okay with cloud processing for sensitive content.
  • dB-domain cliff detectors false-positive on fade feet. A legitimate cosine fade into digital zero has infinite dB slope at its foot, so any >NdB/2ms detector flags it forever. Verify repairs with sample-domain STEP detection (GateScan), never dB slopes. (2026-07-13)
  • One-sided iterative fades don't converge on stray boundary impulses. A single sample sitting on a gate boundary survives repeated one-sided fades; fade-down-then-up "mutes" preserve a blip's edges and its leading step. The V-notch (cosine to zero at the boundary, both sides) and hard-zeroing inside gated silence are the converging fixes. (2026-07-13)
  • Meter-clean ≠ ear-clean. Scanners find ticks; repairs can create audible holes the tick-scanner calls clean (the 2026-07-12 duck incident). Match the probe to the defect class a human hears, keep repairs minimal-touch, and give the principal before/after listen clips at swap time.

Workflows & Routing · 1

Each workflow is one job the skill runs. The trigger phrases route your request to the right one — this is the skill's routing table.

  1. 01
    Clean Workflows/Clean.md

    clean audio, edit audio, remove filler words, clean podcast, remove ums, cut dead air, polish audio

Tools · 8

Deterministic executables the workflows call — the code that does the real work, not prompt scaffolding.

  • Analyze.ts
  • Edit.ts
  • GateRepair.ts
  • GateScan.ts
  • LoudnessLock.ts
  • Pipeline.ts
  • Polish.ts
  • Transcribe.ts

How to Invoke

Say any of these to your DA and LifeOS activates the AudioEditor skill automatically:

  • "clean audio"
  • "edit audio"
  • "remove filler words"
  • "clean podcast"
  • "remove ums"
  • "cut dead air"
  • "polish audio"
  • "trim recording"
  • "cut stutters"
  • "ticking audio"
  • "clicking audio"
  • "audio clicks"
  • "gate artifacts"
  • "popping audio"

Or invoke explicitly:

Skill("AudioEditor")

Want LifeOS to do this for you?

Install LifeOS on your machine — your DA gets the AudioEditor skill plus 46 others, all hooked into one Life OS.