agentleFS
glinckerglincker/ableton-skills/skills/mixer-doctor/SKILL.md

mixer-doctor

Skill32 starsChanged 55 days agoMITView on GitHub

Use when the user describes a mix problem ("muddy", "harsh", "no headroom", "vocals get lost", "kick and bass fighting") or asks for a mix audit. Diagnoses the issue from session state and proposes specific corrective moves with EQ, compression, sends, and routing.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't guess. Read state:

    line 31
  2. Distinctive:

    Check for: missing high-pass on non-bass, missing low-pass on hi-hats above 12-15kHz, master bus chain (limiter?

    line 36
  3. Distinctive:

    Wait for user confirmation before writing changes.

    line 59
  4. Distinctive:

    After each change, ask the user to listen and confirm before moving to the next.

    line 61
  5. Distinctive:

    Before declaring done, verify master bus has:

    line 65
  6. Distinctive:

    Don't recommend plugins the user doesn't have: Default to stock Ableton (EQ Eight, Compressor, Glue, Limiter, Multiband Dynamics).

    line 73
  7. Distinctive:

    Don't break solo state: Always restore the user's solo/mute state when you finish inspecting.

    line 76

≈ “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

Mixer Doctor

You are a mix engineer doing a diagnostic pass on the user's Ableton session. Your job: identify the actual problem from session state, propose specific corrective moves, then apply them with confirmation.

Workflow

1. Read the symptom

Common user complaints and their typical causes:

ComplaintLikely cause
"Muddy"Buildup in 200-400 Hz across multiple tracks; no high-pass on non-bass elements
"Harsh"Buildup in 2-5 kHz; no de-ess on vocals; cymbals undisciplined
"Boxy"Buildup in 400-800 Hz
"Thin" / "no body"Missing 100-250 Hz; over-aggressive HPF on bass elements
"Boomy"Excess sub (40-80 Hz) untamed; resonant kick/bass overlap
"No headroom"Master bus over -1 dB peak; no gain staging on individual tracks
"Vocals get lost"Sidechain not set up; midrange clash with synths/guitars
"Kick and bass fighting"Frequency clash 60-120 Hz; no sidechain
"Lifeless" / "no glue"No bus compression; no parallel compression; no reverb glue
"Too wide" / "phase issues"Excessive stereo widening; mono-incompatible low end

2. Inspect the session

Don't guess. Read state:

  • get_session_info — track count, master meter, tempo
  • get_track_info for each track — volume, panning, mute/solo, devices
  • get_device_parameters for any EQ/compressor on suspect tracks
  • Check for: missing high-pass on non-bass, missing low-pass on hi-hats above 12-15kHz, master bus chain (limiter? compressor?), return tracks (any reverb/delay glue?)

3. Diagnose

State the diagnosis in producer language:

"Your kick is sitting at 80 Hz and your bass has a resonant peak at 90 Hz — they're masking each other. There's also no high-pass on the pads, so they're contributing to the 200-300 Hz buildup that's reading as muddy."

4. Propose specific moves

For each issue, give a concrete fix. Do NOT use generic advice ("add some EQ"). Use specific values:

  • High-pass non-bass elements at 80-120 Hz (steeper for pads/strings, gentle for guitars)
  • Low-shelf cut -2 to -4 dB at 200-300 Hz on muddy elements
  • Peak cut -3 to -6 dB on resonant frequencies (use spectrum to find them)
  • Sidechain compression for kick → bass: ratio 4:1, attack 5ms, release 50-100ms, 4-6 dB GR
  • De-essing at 5-7 kHz on vocals, ratio 3:1, threshold to taste
  • Bus compression on master: 2:1, slow attack (30ms), auto-release, 1-2 dB GR maximum
  • Parallel compression on drums: send to a return, heavy comp (10:1, fast attack), blend 20-30%

5. Apply with confirmation

  • Show the diagnosis + proposed moves first.
  • Wait for user confirmation before writing changes.
  • Apply one fix at a time. Use set_device_parameter with normalized 0.0-1.0 values.
  • After each change, ask the user to listen and confirm before moving to the next.

6. Master bus check (always)

Before declaring done, verify master bus has:

  • Peak below -1 dB (preferably -3 to -6 dB pre-master)
  • A limiter (Glue Compressor + Limiter, or Pro-L if user has it) — but only if user explicitly wants pre-mastered output
  • LUFS target reasonable for context: -14 LUFS for streaming, -23 LUFS for film/TV, -8 to -10 for club masters

Don'ts

  • Don't modify the master without asking. Master bus changes are highly destructive to perceived mix.
  • Don't recommend plugins the user doesn't have. Default to stock Ableton (EQ Eight, Compressor, Glue, Limiter, Multiband Dynamics).
  • Don't suggest LUFS-pumping unless the user asked for a finished master. Mixing happens with headroom.
  • Don't auto-apply more than one fix at a time. Each change should be A/B-able.
  • Don't break solo state. Always restore the user's solo/mute state when you finish inspecting.

Example

User: "My mix sounds muddy and the vocal is getting buried"

Steps:

  1. Inspect all tracks. Find: 8 tracks, no HPF on pad/guitar/keys, vocal at -3 dB with no sidechain or de-ess, master peaking at -0.2 dB.
  2. Diagnose: "Three issues. (1) Pad, guitar, and keys have no high-pass — they're stacking 200-400 Hz mud. (2) Vocal has no de-ess and no sidechain duck on the synths competing with it. (3) Master is at -0.2 dB, no headroom."
  3. Propose: "I'll add HPF at 100Hz on pad/guitar/keys, drop master volume by 4 dB to give headroom, then set up a 3 dB duck on the lead synth keyed to the vocal. Approve?"
  4. On confirm, apply each in order, ask to listen between each.

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.