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

arrangement-coach

Skill32 starsChanged 55 days agoMITView on GitHub

Use when the user has a Session-view loop and wants to promote it to a full Arrangement, build sections (intro/verse/drop/break/outro), or extend a 4-bar idea into a 3-minute track. Examples - "turn this loop into a full song", "build me a 2-minute arrangement from this", "promote session to arrangement".

The file

We split this skill into the rules it gives an agent

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user once: "Which structure?"

    line 20
  2. Very specific:

    Use create_arrangement_clip (or equivalent) to drop clips at the right bars on the right tracks

    line 34
  3. Distinctive:

    Risers: before drops (if EDM/pop) — white noise sweep, snare roll, reverse cymbal

    line 39
  4. Distinctive:

    Don't ride more than 3 dB.

    line 48
  5. Distinctive:

    Before applying, summarize: "I'll build a 2:48 EDM structure: intro 16, build 16, drop 32, break 32, build 16, drop 32, outro 16.

    line 52
  6. Distinctive:

    Don't rewrite the user's musical content — only arrange existing clips.

    line 56
  7. Distinctive:

    Don't add sections the user didn't ask for ("I added a key change in the bridge").

    line 57
  8. Distinctive:

    Don't apply heavy automation to the master without explicit ask.

    line 58
  9. Very specific:

    Don't quantize or modify clip contents — that's midi-cleanup's job.

    line 59
  10. Distinctive:

    Read session — 4 tracks (drums, bass, keys, pad), 4-bar loops on all

    line 66
  11. Distinctive:

    Add: subtle volume rise into the full mix, drum fill at the start of variation, reverb wash on the last bar

    line 69

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

Arrangement Coach

Promote a Session-view loop into a structured Arrangement, or extend a short idea into a full-length track. The user owns the musical content; you handle structural decisions.

Workflow

1. Read what they have

  • get_session_info — confirm session vs arrangement state
  • get_track_info for each track — collect all clips currently in Session view
  • Identify the loop length (most likely 4 or 8 bars) and the BPM

2. Choose a structural template

Ask the user once: "Which structure?"

TemplateLengthSections
Pop~3 minIntro 8 → V1 16 → Pre 8 → Chorus 16 → V2 16 → Pre 8 → Chorus 16 → Bridge 8 → Chorus 16 → Outro 8
EDM~4 minIntro 16 → Build 16 → Drop 32 → Break 32 → Build 16 → Drop 32 → Outro 16
Lo-fi2-3 minIntro 4 → Loop A x4 → Variation x2 → Loop A x2 → Tail 4
CinematicvariesStmt → Dev → Climax → Resolution. Use rubato; bar count flexible.
Hip-hop2-3 minIntro 4 → V1 16 → Hook 8 → V2 16 → Hook 8 → Bridge/V3 16 → Hook 8 → Outro 4

3. Promote loops to arrangement

For each section in the template:

  • Identify which Session clips fit (most loops can serve multiple sections by muting/unmuting tracks)
  • Use create_arrangement_clip (or equivalent) to drop clips at the right bars on the right tracks
  • Mute tracks that shouldn't play in that section (intro = drums + bass only; chorus = everything; bridge = strip back)

4. Add transitions

  • Risers before drops (if EDM/pop) — white noise sweep, snare roll, reverse cymbal
  • Drum fills at section boundaries — tom roll into the chorus
  • Filter automation — high-pass sweep into a build, low-pass into a break
  • Reverb tail throw — send the last hit of a section through the delay/reverb return

5. Master fader automation (subtle)

  • -1 to -3 dB dip in breakdowns
  • Slight push (+0.5 dB) into final chorus
  • Don't ride more than 3 dB; let the mix do the work

6. Confirm

Before applying, summarize: "I'll build a 2:48 EDM structure: intro 16, build 16, drop 32, break 32, build 16, drop 32, outro 16. Drum fills at every section boundary, filter sweep into builds, master fader -2 dB in break. Apply?"

Don'ts

  • Don't rewrite the user's musical content — only arrange existing clips.
  • Don't add sections the user didn't ask for ("I added a key change in the bridge").
  • Don't apply heavy automation to the master without explicit ask.
  • Don't quantize or modify clip contents — that's midi-cleanup's job.

Example

User: "I have a 4-bar lo-fi loop, give me a full 2-minute track"

Steps:

  1. Read session — 4 tracks (drums, bass, keys, pad), 4-bar loops on all
  2. Apply lo-fi template: 2:00 = ~50 bars at 90 BPM
  3. Drop clips: intro 4 (just keys + pad), Loop A x4 = 16 (full mix), Variation x2 = 8 (mute drums, add filter sweep), Loop A x2 = 8, tail 4 (just pad with delay throw)
  4. Add: subtle volume rise into the full mix, drum fill at the start of variation, reverb wash on the last bar
  5. Report and confirm before writing

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.