arrangement-coach
Use when the user has a Session-view loop and wants to promote it to a full Arrangement, build sections…
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 compatibility, frequency balance, LUFS. Examples - "is this ready to master?", "audit my mix before export", "check my
Claude Code
$ npx -y skills add glincker/ableton-skills --skill mastering-prep --agent claude-code
Codex
$ npx skills add glincker/ableton-skills --skill mastering-prep -a codex -y
Cursor
$ npx skills add glincker/ableton-skills --skill mastering-prep -a cursor -y
Gemini CLI
$ npx skills add glincker/ableton-skills --skill mastering-prep -a gemini-cli -y
GitHub Copilot
$ npx skills add glincker/ableton-skills --skill mastering-prep -a github-copilot -y
OpenCode
$ npx skills add glincker/ableton-skills --skill mastering-prep -a opencode -y
Windsurf
$ npx skills add glincker/ableton-skills --skill mastering-prep -a windsurf -y
name: mastering-prep description: 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 compatibility, frequency balance, LUFS. Examples - "is this ready to master?", "audit my mix before export", "check my levels".
Pre-master audit. Confirm the mix is in a clean state for either external mastering or self-mastering. Does NOT apply final mastering — that's a separate workflow with explicit user intent.
For each item, mark ✅ pass or ❌ fail with the specific reading:
| Check | Target | What to look for | | --- | --- | --- | | **Peak level** | -3 to -6 dB | Master should have headroom — never above -1 dB | | **No master limiter active for export-to-mastering** | Off | Mastering engineer wants raw mix; remove limiter from master | | **No master compressor over 2 dB GR** | <2 dB | Heavy mastering compression on a pre-master is destructive | | **LUFS integrated** | -16 to -20 LUFS for pre-master | Too loud = no headroom for mastering | | **Mono compatibility** | All elements audible in mono | Toggle Utility's mono switch — verify nothing disappears | | **Phase coherence** | Above 0.0 (positive) | Use Spectrum or Stereo & Phase — dips below 0 = destructive cancellation | | **Frequency balance** | No spikes >6 dB above neighbors | Bass vs mids vs highs evenly spread | | **Sub-bass below 40 Hz** | Cut or controlled | Anything below 30 Hz wastes headroom and clouds masters | | **Above 18 kHz** | Cut if no musical content | Tames hiss/artifacts; saves headroom | | **DC offset** | None | Use Utility's DC filter on the master | | **Track-level clipping** | None | Inspect each track's meter — yellow is fine, red is not | | **Inactive devices** | Bypass or remove | Unused devices on tracks waste CPU and confuse archiving |
Print the audit table with results. Lead with failures, then warnings, then passes.
> *"Audit results:* > *❌ Master peaking at -0.8 dB — needs at least 3 dB more headroom* > *❌ Vocals on track 3 mono-incompatible — disappears 30% in mono fold* > *⚠️ LUFS integrated -10.2 — too loud for pre-master, drop master fader 4 dB* > *✅ Phase coherence 0.7 — good* > *✅ No DC offset* > *✅ Sub-bass clean below 30 Hz*"*
For each failure, propose a specific fix. Apply only on user confirmation:
If user is exporting now, also confirm:
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…
Use when the user wants to generate, voice, or modify chord progressions. Examples - "give me a sad chord progression in C…
Use when the user wants drum patterns by genre - kick, snare, hi-hat, percussion. Examples - "give me a trap beat", "house drum…
Use when the user asks to humanize a MIDI part, fix voice leading, quantize notes, clean up timing, fix stuck/duplicate notes, or…
Use when the user describes a mix problem ("muddy", "harsh", "no headroom", "vocals get lost", "kick and bass fighting") or asks…
Use when the user asks to set up tracks, pick instruments, scaffold an arrangement, build a project template, or describe a track…
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…