What problem does it solve?
Operating Ableton Live programmatically is error-prone: API commands report success without applying changes, parameter ranges vary per device, and some controls like the Max for Live LFO Map button cannot be scripted at all. This Skill encodes the verification discipline, device knowledge, and API workarounds needed to reliably build tracks, clips, patches, and generative music in a live set.
Core Features & Use Cases
- Verified Device Control: Reads device parameters before setting them, respects per-device ranges, and reads back every change to confirm it actually landed.
- Generative Music Construction: Uses coprime loop lengths, note probability, velocity deviation, and unsynced LFOs to build evolving, non-repeating material.
- API Limitation Handling: Knows which controls cannot be scripted (LFO Map targets, sidechain sources, track grouping) and instructs the user exactly which control to click, or substitutes a scriptable approach like return tracks for shared effects.
- Use Case: Ask the agent to build a generative ambient patch with a Drift synth, probability-weighted MIDI notes, and a slow modulated filter, and it will resolve track and device indices, set parameters within their real ranges, verify each change, and hand you the one Map click the API cannot perform.
Quick Start
Ask the agent to build a track in Ableton Live, for example: create a drum rack with a sidechained bass and a generative melody clip using note probability.