arrangement-coach
Use when the user has a Session-view loop and wants to promote it to a full Arrangement, build sections (intro/verse/drop/break/outro), or extend a 4-bar idea…
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.
$ npx -y skills add glincker/ableton-skills --skill mixer-doctor --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/mixer-doctorContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
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.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.
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 |
Don't guess. Read state:
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."*
For each issue, give a concrete fix. Do NOT use generic advice ("add some EQ"). Use specific values:
Before declaring done, verify master bus has:
> 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.
Claude Skills for Ableton Live producers. Workflows for Claude Code, Cursor, Codex, and Gemini CLI. Pairs with any Ableton MCP server. MIT.
Use when the user has a Session-view loop and wants to promote it to a full Arrangement, build sections (intro/verse/drop/break/outro), or extend a 4-bar idea…
Use when the user wants to generate, voice, or modify chord progressions. Examples - "give me a sad chord progression in C minor", "voice these chords for…
Use when the user wants drum patterns by genre - kick, snare, hi-hat, percussion. Examples - "give me a trap beat", "house drum pattern", "DnB drums at 174",…
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. Audits headroom, peak levels, mono…
Use when the user asks to humanize a MIDI part, fix voice leading, quantize notes, clean up timing, fix stuck/duplicate notes, or generally polish a MIDI clip…
Use when the user asks to set up tracks, pick instruments, scaffold an arrangement, build a project template, or describe a track they want to make in Ableton…