ableton-songwriting-copilot
Use when helping a songwriter or music producer operate ChordChemist with Ableton Live and Max for Live: preparing the local web app, OpenAI Realtime voice, SQLite songs, Ableton/M4L bridge, writing o
SKILL.mdskills/ableton-songwriting-copilot/SKILL.md
GitHubAbleton Songwriting Copilot
Core Model
Treat ChordChemist as the songwriting companion, Ableton Live as the sound/playback environment, and Max for Live as the narrow local bridge. Keep OpenAI keys and Realtime sessions in the browser/server app; keep Ableton mutations behind explicit bridge commands and user intent.
Available Scripts
scripts/check-stack.sh— Checks local app, API key presence, SQLite, bridge, Max Library assets, M4L device presence, and Ableton process status.
Prerequisites:
- Bash, curl, git, Python 3, and standard macOS shell tools.
- No Bun/Bunx dependency for this skill.
- Use
scripts/check-stack.sh --helpbefore changing flags. - Use
scripts/check-stack.sh --jsonwhen the result needs to be parsed by an agent or piped into another command.
Workflow
- Classify the task:
- Setup/readiness: app URL,
.env, OpenAI key, SQLite, bridge server, M4L poller, Ableton slot. - Realtime voice: browser WebRTC, macOS microphone permission,
/api/realtime/session, transcript/consent behavior. - Ableton export/playback: highlighted slot, M4L device, instrument after the bridge, write/fire/stop clips.
- Songwriting: chords, melody, arrangement, vocal adaptation, audition decisions.
- Implementation: code, docs, M4L assets, tests, packaging.
- Setup/readiness: app URL,
- For setup/debug/Ableton work, read
references/chordchemist-m4l-runbook.md. - Run
scripts/check-stack.shbefore claiming local readiness, unless the user only wants conceptual advice. - For deterministic harmony/melody answers, use
$chordchemist-composerwhen available. Do not invent ChordChemist CLI results. - For browser UI work, use the Browser/in-app browser on the local URL. For Ableton or Max UI work, use Computer Use and begin with
get_app_state. - Before mutating Ableton, confirm the user asked to send/write/play/stop in Live, or that the current task clearly implies it.
- Verify with concrete evidence: local status JSON, bridge
/health, M4L poller count, successful command result, visible Live meters/audio, or test output.
Production Guardrails
- Do not print API keys. Report only present/missing.
- Do not move Realtime microphone capture into Max for Live.
- Do not auto-play, overwrite clips, or perform destructive melody actions without user intent or consent gates.
- When
Permission deniedappears on Realtime, check macOS microphone permission for Codex/Chrome before blaming OpenAI. - When Live is silent, check instrument placement and
midiin -> midioutpass-through before changing music. - When bridge commands time out, check for stale Max editor pollers and restart
npm run live-bridgebefore rewriting code.
Script
Use the local stack checker from any directory:
scripts/check-stack.sh
Useful flags:
scripts/check-stack.sh --help
scripts/check-stack.sh --json
scripts/check-stack.sh --repo /path/to/chord-chemist
scripts/check-stack.sh --app-url http://localhost:8080 --bridge-url http://127.0.0.1:53873
Exit codes:
0: success.1: general runtime error.2: invalid arguments.
Completion Criteria
- For readiness: identify the app URL, OpenAI key status, SQLite DB path, bridge status, poller count, and Ableton/M4L next action.
- For Realtime: confirm API key and browser/server status, then resolve mic permission or report the remaining OS/browser step.
- For Ableton playback: confirm clip write result and either visible meters/audio or the specific missing piece.
- For implementation changes: run the repo’s relevant checks and update M4L/realtime docs when behavior changes.