track-coachlisted

Full-stack compositional coach for music producers. Runs everything by default: audio arc analysis, Demucs stem separation, frequency masking, per-stem rhythm + separation-quality, drum-hit breakdown (kick/snare/hat), note transcription, AND Ableton .als parsing (tracks, MIDI, AUDIO clips, automation envelopes, locators). Builds one offline HTML widget with a synced multi-stem PLAYER (play/seek/mute/solo, playhead linked to every chart), the real project arrangement on the timeline, an automation "intention vs result" layer, and a Demucs-stem ↔ real-track map. Gives concrete, specific diagnostics — not generic numbers, but "bass masks mid in 250–500 Hz during bars 8–24" and "Cutoff automation ends at 2:45 but brightness keeps rising to 3:10". ALWAYS USE THIS SKILL when the user mentions: a track, a mix, an arrangement, an .als file, "why does it sound stuck/raw/flat/cloudy", "compare versions", "check the arc", "analyse my project", "what's happening in my track" — even casually, even without the word "analys
happysasha18/track-coach · ★ 0 · Data & Documents · score 75

Install: claude install-skill happysasha18/track-coach

# track-coach Full-stack compositional coach for music producers. Runs the complete pipeline by default. **Core principle — three output layers (always):** 1. **Measured** — exact numbers from scripts only, never invented 2. **What this typically means** — specific, concrete interpretation (not "energy is low" but "bass dominates 250–500 Hz in the first 2 minutes, mids are present but buried") 3. **Up to you** — patterns observed, no directives. The author decides what to do. Read `references/methodology.md` for the conceptual framework (variety vs development, masking principle, what each metric measures). Read `references/interpretation.md` for the numerical ranges. Read `references/install_troubleshooting.md` if setup fails. --- ## Step 0 — Welcome + collect files Greet the user warmly and frame the inputs as tiers — every tier works, more just unlocks more. **Speak the user's language** (match how they wrote; default to English). Translate the example, don't paste it verbatim: > "Let's break your track down properly. The more you give me, the deeper it goes: > • **Just an mp3/wav** — good: full development arc, stems, masking, rhythm, drum > breakdown, note transcription, and a synced stem player. > • **+ the Ableton .als** — great: I overlay the real arrangement (every track, MIDI > and audio), the automation envelopes, and check intention vs. result on the timeline. > • **The whole project folder** — ideal: I find the .als and the latest render myself, > so