agentleFS
CanArslanDevCanArslanDev/ableton-live-mcp/skills/ableton-live/SKILL.md

ableton-live

Skill11 starsChanged 36 days agoMITView on GitHub

How to work in Ableton Live through the ableton MCP tools, covering looking before changing, addressing tracks/devices/clips, batching edits, undo, snapshots and listening to the result. Use whenever a request involves Ableton Live, a Live set, its tracks, clips, devices, scenes or mixer.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. OthmanAdi/loophole★ 22same name
    2. LevyBytes/AI-SKILL-ableton-live★ 4same name
    3. SpeakingColors/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the user states a decision or a preference, keep it: memory(action="remember", text="Kick at -6 dB", key="kick") for this set (saved …

    line 19
  2. Very specific:

    Before a series of mix or sound changes: snapshot(action="save", name="before …").

    line 33
  3. Distinctive:

    Delete only what the user named.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Working in Ableton Live

The ableton MCP server controls the Live set that is open right now, through the AbletonMCP Remote Script running inside Live. Every change is real and audible at once, and each tool call is one step in Live's undo history.

Look first

  • get_session_overview() returns tempo, meter, Key & Scale, every track (type, devices, mixer, Session and Arrangement clips) and the scenes. Call it before changing anything and again after structural edits; do not guess indices. Its memory holds what was decided about this set and what the user likes: follow it ("as we agreed" means look there).
  • When the user states a decision or a preference, keep it: memory(action="remember", text="Kick at -6 dB", key="kick") for this set (saved inside it), scope="user" for every set. A key replaces that key's old note.
  • Tracks: index, exact name, master or return A. Devices: index or name. Session clips: clip_index (the scene row). Arrangement clips: arrangement_clip_index.
  • Anything without a dedicated tool: read the Live Object Model with lom_get_object(path="live_set tracks 0 devices 0") and change it with lom_set_property(...) or lom_call_method(...). Several edits in one run_batch(commands=[...]) take one round trip.

Change carefully

  • Before a series of mix or sound changes: snapshot(action="save", name="before …"). snapshot(action="diff", name=...) shows what changed since, and snapshot(action="restore", name=...) puts it back. Two snapshots give the user an A/B.
  • Generators write into a clip slot (clip_index) or the Arrangement (arrangement_time). Pass replace=true only when the old notes should go.
  • Delete only what the user named. When they asked for it, call the tool: clients that can show a confirmation ask the user themselves, and a declined delete comes back as an error to report. Ask first only before deleting something they did not name (a cleanup you are proposing).
  • preview=true on generators, transform_clip_notes and apply_midi_tool shows the notes without writing them: use it when the user wants to see options first.
  • agent_changes() lists what you changed this session; agent_changes(undo=1) takes back your last change exactly. If the user has edited the set since, restore that change's snapshot_before instead (parameter changes) or let them undo in Live.
  • select_in_live(...) shows the user what you are talking about (selects the track, clip or device in Live's window).

Listen to the result

  • measure_levels() meters every track while the set plays (gain staging).
  • render_and_analyze() records a section in real time and reports loudness, true peak, dynamics, tonal balance and stereo image.
  • mix_doctor() records every track at once and finds masking and level problems (see the mix-and-master skill).
  • These play the set in real time, so tell the user before starting a long section, and keep sections short (8–16 bars) while iterating.

"This part", "the selection"

With the AbletonMCP Companion extension (Live 12.4.5+ Suite), the user can right-click an Arrangement selection, clips or a track and choose "Share … with AbletonMCP"; get_live_selection() then returns the bars and tracks they mean. Without it, ask for bar numbers or locator names.

Sets on disk

read_live_set(path=...) reads an .als without opening it: settings, tracks, devices, plug-ins, clips and missing samples; compare_to= a file from the project's Backup folder shows what changed. find_live_sets(query="Serum") finds sets by file, track or plug-in name. These never touch the open set.

Watching what the user does

watch_live(preset="transport") (or selection, structure, or any path/property) starts buffering Live's changes; read them with get_live_events(since=..., wait_seconds=...) and stop with unwatch_live().

When a tool fails

Connection refused, timeouts or "older than this server" errors: run doctor() and follow its fixes; the ableton-setup skill has the details.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.