agentleFS
glinckerglincker/ableton-skills/skills/groove-builder/SKILL.md

groove-builder

Skill32 starsChanged 55 days agoMITView on GitHub

Use when the user wants drum patterns by genre - kick, snare, hi-hat, percussion. Examples - "give me a trap beat", "house drum pattern", "DnB drums at 174", "lo-fi drums with swing", "boom-bap pattern".

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no kit loaded → ask user, or load stock Ableton Drum Kit.

    line 33
  2. Distinctive:

    Add ghost notes on snare at velocity 30-50

    line 85
  3. Distinctive:

    After writing, apply genre-appropriate humanization:

    line 89
  4. Distinctive:

    If user wants a 2-bar pattern with fill:

    line 99
  5. Distinctive:

    Don't write 100% on-grid for any genre except minimal techno or hard EDM.

    line 109
  6. Distinctive:

    Don't overdo ghost notes (>4 per bar starts to clutter).

    line 110
  7. Distinctive:

    Don't apply genre defaults if the user gave a specific tempo — respect their tempo.

    line 111
  8. Distinctive:

    Don't write more than 8 bars in one shot — give the user a section to evaluate.

    line 112

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

Groove Builder

Generate idiomatic drum patterns by genre with proper humanization. Writes to MIDI clips on the user's drum track.

Workflow

1. Identify genre + tempo

Required: genre. Optional: tempo (use genre defaults).

GenreDefault tempoTime sig
Lo-fi hip-hop70-904/4
Boom-bap85-954/4
Trap130-150 (half-time feel)4/4
House120-1284/4
Tech house124-1284/4
Techno125-1354/4
DnB / Jungle165-1804/4
UK garage130-1384/4 (shuffled)
Drill (UK)140-145 (half-time)4/4
Reggaeton95-1004/4 (dembow)

2. Verify drum rack

get_track_info on the drum track. Confirm a drum rack is loaded with at least kick (C1), snare (D1), hat (F#1), and optionally clap (D#1), open hat (A#1), perc (G1+).

If no kit loaded → ask user, or load stock Ableton Drum Kit.

3. Write the pattern

For a 1-bar (16-step) pattern, here are tested templates:

Lo-fi hip-hop

Kick:  X . . . . . X . . . . . . . . .
Snare: . . . . X . . . . . . . X . . .   (snare on 5 & 13 for half-time feel)
Hat:   X . X . X . X . X . X . X . X .   (8th notes)
  • Kick: vel 100-110
  • Snare: vel 90-100, slight late timing (+5ms)
  • Hat: vel 65-85, ±15 humanize, swing 8-12%

Boom-bap

Kick:  X . . X . . X . . . X . . . . .
Snare: . . . . X . . . . . . . X . . .
Hat:   X X X X X X X X X X X X X X X X   (16ths)
  • Hat: vel 50-80, more aggressive humanize ±20

Trap

Kick:  X . . . . . . X . . . . . . . .   (sparse, half-time feel)
Snare: . . . . X . . . . . . . X . . .
Hat:   X X . X X X . X X . X X X . X X   (rolling, with stutters)
808:   long held bass notes underneath
  • Hi-hat rolls: alternate 16ths with 32nd-note bursts
  • Open hat occasionally on the off-beat

House

Kick:  X . . . X . . . X . . . X . . .   (4-on-the-floor)
Clap:  . . . . X . . . . . . . X . . .
Hat:   . . X . . . X . . . X . . . X .   (off-beat 8ths)
OpHat: . X . . . X . . . X . . . X . .   (between beats)
  • Kick: vel 110, locked on grid
  • Clap: vel 95
  • Hat: tight, minimal humanize

DnB

Kick:  X . . . . . . . . . X . . . . .
Snare: . . . . X . . . . . . . X . . .
Hat:   X X X X X X X X X X X X X X X X   (16ths, fast)
  • Snare on 2 & 4 (half-time feel at the bar level)
  • Add ghost notes on snare at velocity 30-50

4. Humanize

After writing, apply genre-appropriate humanization:

  • Lo-fi: heavy (±20 velocity, ±15ms timing, 12% swing)
  • Boom-bap: medium (±15 velocity, ±10ms, 6-8% swing)
  • House/Techno: minimal (±5 velocity, ±2ms, 0% swing)
  • Trap: moderate on hats, tight on kick/snare
  • DnB: tight on kick/snare, loose on hats

5. Add fill (optional)

If user wants a 2-bar pattern with fill:

  • Bar 1: main pattern
  • Bar 2: same, but last 1-2 beats replaced with a fill (snare roll, tom run, hat stutter)

6. Confirm + write

Summarize: "Lo-fi pattern, 90 BPM. Kick on 1+3, snare on 5+13, 8th hats with 12% swing. ±15 velocity, ±15ms timing. Apply?"

Don'ts

  • Don't write 100% on-grid for any genre except minimal techno or hard EDM.
  • Don't overdo ghost notes (>4 per bar starts to clutter).
  • Don't apply genre defaults if the user gave a specific tempo — respect their tempo.
  • Don't write more than 8 bars in one shot — give the user a section to evaluate.

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.