Skip to content
Automation
Skill

/mixer-doctor

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.

From plugin
ableton-skills
4512 skills4 commands

Claude Code

$ npx -y skills add glincker/ableton-skills --skill mixer-doctor --agent claude-code

SKILL.md

mixer-doctor.SKILL.md
name: mixer-doctor
description: 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.

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:

| Complaint | Likely 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.

Read more
@glincker
Ships withableton-skills

Claude Skills for Ableton Live producers. Workflows for Claude Code, Cursor, Codex, and Gemini CLI. Pairs with any Ableton MCP server. MIT.

Stars on GitHub

Momentum

stars in total
45
Star history of glincker/ableton-skills on GitHub, a chart by star-history.com

Other skills on ableton-skills.

chord-pro

chord-pro

Use when the user wants to generate, voice, or modify chord progressions. Examples - "give me a sad chord progression in C…

groove-builder

groove-builder

Use when the user wants drum patterns by genre - kick, snare, hi-hat, percussion. Examples - "give me a trap beat", "house drum…

mastering-prep

mastering-prep

Use when the user is finishing a track and wants to check it's ready to send to a mastering engineer or for self-mastering.…

midi-cleanup

midi-cleanup

Use when the user asks to humanize a MIDI part, fix voice leading, quantize notes, clean up timing, fix stuck/duplicate notes, or…

producer-mode

producer-mode

Use when the user asks to set up tracks, pick instruments, scaffold an arrangement, build a project template, or describe a track…

More skills from other plugins.

agent-builder

agent-builder

Load immediately after an Agent intent, before the first agent_builder_* call. Governs how you create, configure, test, and…

n8n11d209k
@n8n-io@n8n-ioInstall Skill
browser-use

browser-use

Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…

@browser-use@browser-useInstall Skill
agent-browser

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…

@vercel-labs-2@vercel-labs-2Install Skill
add-anydoc

add-anydoc

Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when…

@nanocoai@nanocoaiInstall Skill

Questions about mixer-doctor.

Which coding agents can use mixer-doctor?
mixer-doctor installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.