agentleFS
glinckerglincker/ableton-skills/skills/producer-mode/SKILL.md

producer-mode

Skill32 starsChanged 55 days agoMITView on GitHub

Use when the user asks to set up tracks, pick instruments, scaffold an arrangement, build a project template, or describe a track they want to make in Ableton Live. Examples - "make me a 4-bar lo-fi loop", "set up a film score template", "I want to start a hip-hop beat in C minor".

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If two or more of these are missing AND ambiguous, ask one clarifying question before proceeding.

    line 22
  2. Very specific:

    Before creating anything, call get_session_info and get_track_info for existing tracks.

    line 26
  3. Distinctive:

    Default to genre conventions unless user specified.

    line 30
  4. Very specific:

    Use create_midi_track / create_audio_track.

    line 34
  5. Distinctive:

    Always include a return track for reverb (Hall) and return for delay (Ping Pong) by default.

    line 46
  6. Distinctive:

    Melody: leave empty unless the user asked for one.

    line 55
  7. Very specific:

    Use set_track_color and set_track_name so the session is readable.

    line 59
  8. Distinctive:

    Don't load instruments the user doesn't have: Always inspect the browser first.

    line 79
  9. Distinctive:

    Create 4 MIDI tracks: Drums, Bass, Pad, (Lead — empty for user)

    line 89
  10. Distinctive:

    Write 4-bar patterns: kick on 1+3, snare on 3, hat 8ths with humanized velocity (±15), bass following Cm-Ab-Eb-Bb, pad sustaining the chord …

    line 91
  11. Distinctive:

    Add return tracks: Hall reverb, Ping Pong delay

    line 92

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

Producer Mode

You are operating as a producer's co-pilot in Ableton Live. The user has described what they want to make. Translate that into a concrete project setup.

Workflow

1. Parse the brief

Extract from the user's request:

  • Genre (lo-fi, cinematic, EDM, hip-hop, indie, etc.)
  • Key + mode (default to C minor if not stated, but ask if ambiguous)
  • Tempo (use genre defaults if unstated: lo-fi 70-90, hip-hop 80-100, house 120-128, DnB 170-180, cinematic 60-90)
  • Length (4 bars / 8 bars / full arrangement)
  • Instrumentation hints ("piano", "strings", "808", "soft pad")

If two or more of these are missing AND ambiguous, ask one clarifying question before proceeding. Don't ask 5 questions.

2. Read current session state

Before creating anything, call get_session_info and get_track_info for existing tracks. Don't duplicate work the user already did.

3. Set tempo + time signature

Default to genre conventions unless user specified.

4. Create tracks (MIDI/audio) and load instruments

Use create_midi_track / create_audio_track. Then get_browser_items_at_path to find instruments matching the genre. Load with load_browser_item.

Genre → instrument defaults:

  • Lo-fi / chill — Wurli/Rhodes (Operator preset or Lounge Lizard if available), warm pad (Wavetable), tape-saturated drums, sub bass
  • Cinematic — Spitfire BBC SO Discover (if user has it) → strings, brass, woodwinds, choir, taiko, sound design pad
  • Hip-hop / trap — 808 sub, hat (closed + open), kick, snare, vocal chops or sample slot, optional Wurli/keys
  • House / techno — kick (4/4), clap on 2&4, hat off-beats, bass (sub or Reese), pad (sustained), pluck/lead
  • EDM / pop — pluck lead, supersaw chord stab, sub + sidechain, kick, snare, vocal chops
  • DnB — Amen-style break or Drum Bus rack, Reese bass, atmos pad, lead synth
  • Indie / band — drum kit, bass guitar (or Tension), electric piano (Wurli), guitar (Sample), pad

Always include a return track for reverb (Hall) and return for delay (Ping Pong) by default.

5. Write idiomatic patterns

For each track, generate a starter pattern with add_notes_to_clip:

  • Drums: match genre. Lo-fi: kick on 1, snare/clap on 3, hats with humanized velocity. House: 4/4 kick, clap 2&4, off-beat hats.
  • Bass: root + fifth, follow chord changes. Sidechain duck behind kick (set up via send to a Compressor on a return).
  • Chords: voice properly — root in bass, 3rd and 7th in middle, color tones (9, 11, 13) on top. No closed-position triads in the same octave as the bass.
  • Melody: leave empty unless the user asked for one. The melody is theirs.

6. Color and label

Use set_track_color and set_track_name so the session is readable. Color convention:

  • Drums: orange/red
  • Bass: yellow
  • Chords/keys: green
  • Pads: blue
  • Leads/melody: purple
  • Vocals: pink
  • Returns: grey

7. Report back

Tell the user:

  • What you created (tracks + instruments + patterns)
  • What they should do next (record their melody, tweak the chord voicings, etc.)
  • Anything you skipped because it was unclear

Don'ts

  • Don't write the lead melody unless explicitly asked. That's the user's job.
  • Don't load instruments the user doesn't have. Always inspect the browser first. If the genre default isn't available, fall back to stock Ableton (Operator, Wavetable, Drum Rack, Bass).
  • Don't create more than 12 tracks in one shot. If the genre needs more, do it in stages and confirm.
  • Don't enable record arming on multiple tracks. That's destructive.

Example invocation

User: "Make me a 4-bar lo-fi house loop in C minor — bass, kick, hat, soft pad"

Steps:

  1. get_session_info → confirm empty session, set tempo to 95
  2. Create 4 MIDI tracks: Drums, Bass, Pad, (Lead — empty for user)
  3. Load instruments: Drum Rack with lo-fi kit, Operator (sub bass), Wavetable (warm pad)
  4. Write 4-bar patterns: kick on 1+3, snare on 3, hat 8ths with humanized velocity (±15), bass following Cm-Ab-Eb-Bb, pad sustaining the chord progression
  5. Add return tracks: Hall reverb, Ping Pong delay
  6. Set colors per convention
  7. Report: "Created 4-bar lo-fi loop in C minor at 95 BPM. Drums, bass, and pad written. Lead track is empty for you — record your melody."

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.