agentleFS
OxyFlaxOxyFlax/AI/skills/audio-normalize/SKILL.md

audio-normalize

Skill0 starsChanged 5 months agoMITView on GitHub

Normalize and balance voice levels in a multi-speaker audio recording (m4a, mp3, wav). Use when: voices are unbalanced because some speakers are far from the microphone, preparing audio for transcription, equalizing volume across participants, pre-processing a voice memo before Apple Intelligence transcription or whisper. Runs entirely on-device (MacBook M1/Apple Silicon or iPhone). Supports French and English. Optionally runs local on-device transcription with whisper.cpp.

  • Installs packages

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Very specific:

    Ask the user for the path to the audio file if not provided.

    line 36
  2. Distinctive:

    If ffmpeg is missing, stop and ask the user to install it first.

    line 49
  3. Very specific:

    Use --transcribe flag above, or set up once:

    line 80
  4. Very specific:

    If you need to know *who said what*, feed the normalized output into the meeting-transcribe skill:

    line 93
  5. Very specific:

    Default compressor settings in normalize.sh work well for most recordings.

    line 107
  6. Distinctive:

    If results are over-compressed (voices sound pumping/unnatural), reduce ratio:

    line 108

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audio Normalize — Voice Balancing for Multi-Speaker Recordings

Balances voices in a conversation recording where some speakers are far from the microphone. All processing runs on-device — no audio ever leaves the Mac. Works with French and English recordings.

When to Use

  • Some voices in the recording are too quiet (far mic distance)
  • Preparing an .m4a before Apple Intelligence transcription (re-inject on iPhone/Mac) or before running the meeting-transcribe skill
  • Want a local on-device transcript without any cloud service
  • Pre-processing a Voice Memo before sharing with teammates

What It Does

Three-stage ffmpeg chain:

StageFilterPurpose
1highpass=f=80Remove sub-80 Hz room rumble and handling noise
2acompressorCompress dynamic range: lifts quiet/far voices, attenuates loud peaks
3Two-pass loudnorm (EBU R128)Bring final output to broadcast-standard −16 LUFS

Output: <original>_normalized.m4a — safe to use with any transcription tool.

Procedure

Step 0 — Confirm Input

Ask the user for the path to the audio file if not provided. Confirm output location (default: same folder, _normalized suffix).

Step 1 — Check Environment

# ffmpeg — required for all processing
which ffmpeg || echo "Install: brew install ffmpeg"

# whisper-cli — only needed for local transcription
which whisper-cli || echo "Install: brew install whisper-cpp"

If ffmpeg is missing, stop and ask the user to install it first.

Step 2 — Run Normalization

chmod +x ./scripts/normalize.sh

# Basic — normalize only (then re-inject on iPhone or use Apple Intelligence)
./scripts/normalize.sh path/to/recording.m4a

# With local on-device transcription (whisper.cpp, no internet)
./scripts/normalize.sh path/to/recording.m4a --transcribe

# Specify language explicitly (faster, slightly more accurate)
./scripts/normalize.sh path/to/recording.m4a --transcribe --lang fr
./scripts/normalize.sh path/to/recording.m4a --transcribe --lang en

The script prints loudness before/after so you can see the effect.

Step 3 — Transcription Options

Present the user with the two paths:

Option A — Apple Intelligence (recommended for iPhone integration)

  1. AirDrop _normalized.m4a to iPhone
  2. Open in Voice Memos → tap the recording → share to Notes or use transcript button
  3. Or on Mac: open in QuickTime Player → Edit menu → Transcribe

Option B — Local whisper.cpp (best pure-local quality, no Apple account)

Use --transcribe flag above, or set up once:

brew install whisper-cpp
# Download best model for M1 Pro (quantized, ~1 GB, fast on Metal GPU)
mkdir -p ~/.cache/whisper
curl -L "https://huggingface.co/ggerganov/whisper.cpp/resolve/main/ggml-large-v3-q5_0.bin" \
     -o ~/.cache/whisper/ggml-large-v3-q5_0.bin
# Model lands in ~/.cache/whisper/ — script finds it automatically

whisper.cpp uses Apple Metal GPU on M1 — transcribes ~10 min audio in ~30 s. Supports --lang auto for mixed French/English sessions.

Option C — meeting-transcribe skill (adds speaker diarization)

If you need to know who said what, feed the normalized output into the meeting-transcribe skill:

/meeting-transcribe path/to/recording_normalized.m4a

Step 4 — Verify Output

  • Output file should be ~same size as input (AAC 128k)
  • Listen to a quiet passage: far voices should be clearly audible
  • Loudness printed at end should be near −16 LUFS

Tuning (Advanced)

Default compressor settings in normalize.sh work well for most recordings. If results are over-compressed (voices sound pumping/unnatural), reduce ratio:

# In normalize.sh, find:
acompressor=threshold=-32dB:ratio=5:attack=5:release=80:makeup=5dB
# Reduce ratio to 3 or 4 for a gentler touch:
acompressor=threshold=-32dB:ratio=3:attack=5:release=80:makeup=3dB

Files

FilePurpose
scripts/normalize.shMain processing script

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.