agentleFS
glinckerglincker/ableton-skills/skills/tempo-coach/SKILL.md

tempo-coach

Skill32 starsChanged 55 days agoMITView on GitHub

Use when the user is unsure about tempo, time signature, or rhythmic feel choices. Examples - "what tempo should this be?", "should I switch to 3/4?", "is 95 BPM right for lo-fi?", "how do I make this feel less stiff rhythmically?".

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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:

    Use case (sync to video? for a DJ set?

    line 19
  2. Distinctive:

    If user is unsure: default to 4/4 unless they explicitly want a 3-feel.

    line 53
  3. Distinctive:

    When the user says "the drums feel slow but I want it to feel fast":

    line 61
  4. Distinctive:

    Ask user to play their loop and check:

    line 69
  5. Distinctive:

    If the user is recording live:

    line 77
  6. Distinctive:

    If the user accepts a recommendation:

    line 84
  7. Distinctive:

    Don't change the tempo without explicit approval — half a project's clips will misalign.

    line 90
  8. Distinctive:

    Don't recommend tempo extremes (40 BPM, 220 BPM) without checking the user actually wants that.

    line 91
  9. Distinctive:

    Don't assume 4/4 if the user's loop is in a 3-feel.

    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

Tempo Coach

Help the user pick the right tempo, time signature, and rhythmic feel for what they're making. Mostly conversational; minimal DAW writes.

Workflow

1. Understand the context

What is the user trying to achieve? Pull from:

  • Genre (each has tempo conventions)
  • Reference track (use its tempo as a starting point)
  • Mood (slow = sad/contemplative, fast = energetic)
  • Use case (sync to video? for a DJ set? for a film cue?)

2. Apply genre tempo conventions

GenreTypical tempo rangeNotes
Ambient50-70Often beatless; tempo for harmony pulse
Cinematic underscore60-90Often rubato; click for sync, not feel
Lo-fi hip-hop70-90Half-time feel often makes it feel slower than it is
Boom-bap85-95The classic 90 BPM is the J Dilla sweet spot
Hip-hop modern75-115Trap is often half-time at 140-160
Indie/folk80-120Rubato common; click vs feel tradeoff
Pop95-130"100 BPM ballad" or "118 BPM dance pop"
Rock100-160Power ballads slower (60-80)
House120-128124 is the magic number
Tech-house124-128
Techno125-135
Trance132-140
EDM/Big Room128Locked. Don't deviate.
Hardstyle150-160
Drum & Bass165-180174 is the genre default
Jungle160-175
Footwork160

3. Time signature guidance

When to useTime sig
Most popular music4/4
Waltz, classical 3-feel3/4
Compound (jig, gospel triplet feel)6/8, 12/8
Odd-meter prog/math5/4, 7/8, 11/8
Cinematic flexibilitySwitch between 4/4 and 3/4 by section

If user is unsure: default to 4/4 unless they explicitly want a 3-feel.

4. Half-time vs full-time feel

A common confusion:

  • Trap at 140 BPM is half-time at 140 — drums hit on every other beat, but tempo is set to 140
  • DnB at 174 BPM is full-time — drums on 1-3 (kick) and 2-4 (snare) at 174

When the user says "the drums feel slow but I want it to feel fast":

  • They likely want full-time at the original tempo (e.g., trap at 140 with hi-hats moving fast = 140 with 16th-note hats)
  • Or vice versa: half-time the drums for a heavier feel

Suggest the swap; don't assume.

5. Tempo issues to flag

Ask user to play their loop and check:

  • Drag — feels slower than the click? Adjust micro-timing or reduce humanization
  • Rush — feels faster than the click? Same fix, opposite direction
  • Tempo doesn't match the vibe — if the user's chord progression is romantic but they're at 140 BPM, propose dropping to 90 with a half-time feel

6. Click track / metronome

If the user is recording live:

  • Subdivision: usually 1/4 notes for slow tempos, 1/8 for fast
  • Click sound: use Live's stock click; turn off post-recording
  • Pre-roll: 1 bar minimum, 2 for tight performances

7. Apply (if needed)

If the user accepts a recommendation:

  • set_tempo and set_time_signature if the MCP supports
  • Otherwise: tell them the value to change manually

Don'ts

  • Don't change the tempo without explicit approval — half a project's clips will misalign.
  • Don't recommend tempo extremes (40 BPM, 220 BPM) without checking the user actually wants that.
  • Don't assume 4/4 if the user's loop is in a 3-feel.

Common scenarios

"My beat feels stiff" → Add humanization (see midi-cleanup), or check if you should add swing (8-15% on 16th notes for hip-hop, 0% for EDM).

"This sounds too slow but I don't want to speed up" → Half-time the drums (notes on every other beat) at the same BPM, gives a faster feel without changing chord-change rate.

"Can I change time signature mid-song?" → Yes, but do it cleanly at section boundaries (intro 4/4 → verse 4/4 → bridge 3/4 → chorus 4/4). Mid-bar changes are advanced and usually unintentional.

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.