agentleFS
konradrekonradre/video-production-skills/skills/mastering-audio/SKILL.md

mastering-audio

Skill7 starsChanged 21 days agoMITView on GitHub

Master audio files (especially Suno/Udio AI music) for streaming release with LUFS normalization, true peak limiting, and optional enhancements. Triggers — "master this", "master the track", "LUFS normalize", "optimize for streaming". Not for a spot's or film's delivery loudness — use video-finish-qc.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 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.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run analysis to understand the audio characteristics:

    line 30
  2. Very specific:

    Use --preset suno (optimized for AI music characteristics)

    line 48
  3. Very specific:

    Use --preset streaming for -14 LUFS, conservative processing

    line 52
  4. Very specific:

    Use --preset loud for -9 LUFS with saturation/punch

    line 55
  5. Very specific:

    Use --preset dynamic for -16 LUFS, minimal processing

    line 58
  6. Very specific:

    Default output: If no output specified, creates <input>_mastered.wav in same directory.

    line 85
  7. Distinctive:

    Run analysis on processed file to confirm:

    line 89

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Mastering Skill

Master audio files for streaming release using DSP analysis and processing.

Tool Location

~/.claude/skills/mastering-audio/scripts/master.mjs

Workflow

Phase 1: Analyzing Audio

Run analysis to understand the audio characteristics:

node ~/.claude/skills/mastering-audio/scripts/master.mjs "<INPUT_FILE>" --analyze --json

Metrics to evaluate:

  • LUFS (loudness) - streaming target is -14 LUFS
  • True Peak - should be below -1 dBTP
  • Stereo width and correlation
  • DC offset presence
  • Detected issues (clipping, low headroom, etc.)

Phase 2: Selecting Approach

Based on analysis, determine processing approach:

If Suno/Udio AI music:

  • Use --preset suno (optimized for AI music characteristics)
  • Addresses: harsh 2-4kHz, clipping, overloud output

If targeting streaming platforms:

  • Use --preset streaming for -14 LUFS, conservative processing

If maximum loudness needed:

  • Use --preset loud for -9 LUFS with saturation/punch

If preserving dynamics:

  • Use --preset dynamic for -16 LUFS, minimal processing

Custom approach (advanced):

--target-lufs N     Target LUFS (default: -14)
--ceiling N         True peak ceiling dB (default: -1)
--deharsh           Reduce harsh frequencies
--add-air           High-frequency sparkle
--warmth            Tape saturation
--punch             Transient enhancement
--stereo-width N    Width percentage (100 = unchanged)
--bit-depth N       16 or 24 (default: 24)
--sample-rate N     Output rate (default: 48000)

Phase 3: Processing Audio

Execute mastering with chosen settings:

# Using preset
node ~/.claude/skills/mastering-audio/scripts/master.mjs "<INPUT_FILE>" "<OUTPUT_FILE>" --preset suno

# Custom settings
node ~/.claude/skills/mastering-audio/scripts/master.mjs "<INPUT_FILE>" "<OUTPUT_FILE>" --target-lufs -14 --ceiling -1 --deharsh --add-air

Default output: If no output specified, creates <input>_mastered.wav in same directory.

Phase 4: Verifying Results

Run analysis on processed file to confirm:

node ~/.claude/skills/mastering-audio/scripts/master.mjs "<OUTPUT_FILE>" --analyze

Success criteria:

  • LUFS within ±0.5 of target
  • True peak at or below ceiling
  • No clipping warnings
  • Stereo correlation positive (not phase-inverted)

Presets Reference

PresetLUFSCeilingDe-harshAirWarmthPunchWidth
streaming-14-1YesNoNoNo100%
loud-9-0.3YesYesYesYes105%
dynamic-16-1NoNoNoNo100%
suno-14-1YesYesNoYes102%

Processing Chain

  1. DC offset removal
  2. Hybrid dynamic processor (de-harsh)
  3. High-frequency exciter (air)
  4. Tape warmth saturation
  5. Multiband transient enhancement (punch)
  6. Stereo width adjustment
  7. Bass mono (< 200 Hz)
  8. Final filters (30 Hz HPF, 18 kHz LPF)
  9. LUFS normalization
  10. Lookahead true peak limiter

Dependencies

  • Node.js 18+
  • ffmpeg (for audio decoding)
  • npm dependencies (run npm install in skill directory once)

Example Session

User: master this suno track for spotify release
Assistant:
1. Analyzing: node master.mjs song.mp3 --analyze --json
   → LUFS: -9.2, True Peak: +0.3 dBTP (clipping detected)

2. Selecting: Using suno preset (AI music, targeting -14 LUFS)

3. Processing: node master.mjs song.mp3 song_mastered.wav --preset suno
   → Applied: de-harsh, air, punch, bass mono, LUFS normalization, limiting

4. Verifying: node master.mjs song_mastered.wav --analyze
   → LUFS: -14.0, True Peak: -1.0 dBTP (no issues)
   → Ready for streaming release
  • Deeper context — the upstream projects behind the rules here: video-production/references/CONTEXT-MAP.md § Where the deeper context lives.

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.