glincker/ableton-skills · Archived

producer-mode

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.

First seen Jun 14, 2026

Installation

$ npx skills add glincker/ableton-skills --skill producer-mode

Summary

  • 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".

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from glincker/ableton-skills · top by installs.

npx skills add glincker/ableton-skills

Browse all from glincker/ableton-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 23
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,681 B
  • docs SUMMARY.md 303 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 5 installs

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 getsessioninfo and gettrackinfo 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 createmiditrack / createaudiotrack. Then getbrowseritemsatpath to find instruments matching the genre. Load with loadbrowseritem.

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 addnotesto_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 settrackcolor and settrackname 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. getsessioninfo → 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."