agentleFS
OthmanAdiOthmanAdi/loophole/skills/ableton-live/SKILL.md

ableton-live

Skill22 starsChanged 6 months agoMITView on GitHub

Connect and operate the Loophole Bridge (Ableton Live MCP server). Use when the user wants to check Live/bridge prerequisites, wire an MCP client to Loophole, or run a Live editing recipe (humanize, build arrangement, batch rename, chord from prompt). Triggers: "is my Ableton bridge working", "set up loophole", "connect Claude to Ableton", "/doctor", "/setup".

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. CanArslanDev/ableton-live-mcp★ 11same 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.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    All object references are opaque and session-scoped.

    line 67

≈ “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

ableton-live (alias: loophole)

A thin developer-experience layer for the Loophole Bridge, the MCP server that controls Ableton Live 12 over the official Extensions SDK. This skill closes the loop between "the bridge is installed" and "the agent uses it well." It does three things and nothing more.

It never talks to Live directly. It does not embed tool logic, re-implement the bridge, or import any bridge or SDK code. The bridge is the only thing that touches the Live Object Model. Every Live operation in this skill is a call to one of the bridge's MCP tools.

What this skill does

  1. /doctor runs five prerequisite checks (Live running, extension installed, Node version, bridge port reachable, token present) and prints a PASS or a specific FIX line for each, then one verdict. See doctor.md. It never auto-runs /setup.
  2. /setup reads the port and bearer token from bridge.json, then emits one merge-safe MCP client block for Claude Code, Claude Desktop, or Cursor. It never writes or replaces a config file. See setup.md.
  3. Recipes are reusable snippets for common Live edits, each a named sequence of real bridge tool calls. See recipes/: humanize-midi, build-arrangement, batch-rename, chord-from-prompt.

How the pieces connect

flowchart LR
  U["User intent"] --> SK["ableton-live skill"]
  SK --> DOC["/doctor: 5 checks"]
  SK --> SET["/setup: emit merge-safe config block"]
  SK --> REC["recipes: tool sequences"]
  DOC -. "reads" .-> BJ["bridge.json"]
  SET -. "reads" .-> BJ
  REC --> BR["Loophole Bridge (MCP tools)"]
  BR --> LIVE["Ableton Live 12 Suite"]
  classDef accent fill:#E9A23B,stroke:#9A6A1A,color:#160F02,font-weight:bold;
  class BR accent

The skill reads bridge.json (for /doctor and /setup) and issues MCP tool calls (for recipes). It does not reach past the bridge.

The bridge tools the recipes use

The recipes reference only these registered MCP tools. No recipe invents a tool.

ToolRead or writeWhat it does
live_get_song_overviewreadtempo, scale, grid, counts, and current opaque track references
live_find_trackreadresolve a track name or substring to current opaque track references
live_list_clipsreadlist a track's session slots and clips with current opaque references
live_get_notesreadread all MIDI notes from one clip
live_set_tempowriteset the Set tempo in BPM
live_set_track_propswriteset a track's name, mute, solo, or arm in one serialized mutation
live_set_noteswritereplace all MIDI notes in one clip in one serialized mutation
live_create_trackwritecreate one empty MIDI or audio track
live_create_midi_clipwritecreate an empty MIDI clip in a session clip slot
live_set_paramwriteset one device parameter using its returned opaque session reference
live_insert_devicewriteinsert a built-in Live device on a track
live_render_trackwriterender a track's pre-FX audio over a beat range to a WAV

Mutation boundaries (read before running any recipe)

Each write tool is a separate mutation. Simple setters are designed to initiate their write inside one transaction, but real Live undo behavior remains an E2E gate. Never call a multi-tool recipe atomic. Creating a clip and then filling it uses two mutations because the SDK must return the clip before notes can be assigned. State the mutation count before writing and tell the user to inspect Live's undo history.

Beta limits the recipes inherit

These come from the bridge and extensions, not from the skill, and the recipes state them where they apply:

  • MIDI notes only. No automation, MIDI CC, clip gain, or routing API in this beta.
  • live_create_midi_clip targets Session clip slots, not the Arrangement timeline. The Session-to-Song extension preflights, then runs ordered clear, create, and populate mutation phases. Its receipt reports 0 intended undo entries for a no-op, 2 for cue-only, or 3 when it clears, creates, and populates. Partial errors expose the exact undoStepsToRestore.

All object references are opaque and session-scoped. Use the value returned by the current list or read call unchanged. Never construct a value such as lhref_trk_<opaque-token>, and re-list after structural changes.

  • live_insert_device is built-in Live devices only (no third-party or VST).
  • live_render_track is pre-FX and practical for audio tracks.
  • Scale and tempo are read from the Set; the recipes do not guess a key. Assume 4/4 unless a scene signature is read.
  • User-invoked only.

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.