agentleFS
glinckerglincker/ableton-skills/skills/chord-pro/SKILL.md

chord-pro

Skill32 starsChanged 55 days agoMITView on GitHub

Use when the user wants to generate, voice, or modify chord progressions. Examples - "give me a sad chord progression in C minor", "voice these chords for piano", "what's a good progression for cinematic music?", "extend this progression with more color tones".

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 16 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If two are missing, ask in one sentence:

    line 17
  2. Distinctive:

    No closed-position triads in the same octave as the bass

    line 40
  3. Distinctive:

    Use idiomatic guitar voicings, not piano-translated chords

    line 50
  4. Distinctive:

    Avoid the muddy zone (root in same octave as bass synth)

    line 58
  5. Distinctive:

    If user wants "more color":

    line 62
  6. Distinctive:

    Add 9ths to major chords (Cmaj9 instead of C)

    line 63
  7. Distinctive:

    Add 11ths to suspended chords

    line 64
  8. Distinctive:

    Use 7ths consistently in jazz/neo-soul

    line 65
  9. Distinctive:

    Add altered tones (b9, #11) on V chords for tension

    line 66
  10. Distinctive:

    When moving from one chord to the next, move each voice by the smallest interval possible:

    line 70
  11. Distinctive:

    Avoid parallel fifths and octaves between outer voices

    line 73
  12. Distinctive:

    Keep common tones static when possible

    line 74
  13. Very specific:

    Write the chords to the target track using add_notes_to_clip.

    line 78
  14. Distinctive:

    Don't write closed-position triads stacked in MIDI without thought to voice leading.

    line 82
  15. Distinctive:

    Don't ignore instrument range — Vln1 cannot play below G3.

    line 83
  16. Distinctive:

    Don't put all voices in the same octave (results in muddy mid-range).

    line 84
  17. Distinctive:

    Don't use 7-note voicings unless the user has a 7+ voice synth or rich pad — they sound like a fist on a piano.

    line 85

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

Chord Pro

Generate or refine chord progressions with proper voicing. Music-theory grounded — no random Reddit-tier chord stacks.

Workflow

1. Ask if needed

Required: key + mode, mood/genre, target instrument. Optional: length (default 4 chords), tempo (for rhythmic feel).

If two are missing, ask in one sentence:

"What key and what mood?"

2. Choose progression by genre/mood

Mood/GenreReliable progressions (in C / Cm)
Sad / cinematicCm – Ab – Eb – Bb (i-VI-III-VII), or Cm – Gm/Bb – Ab – Eb
Hopeful / popC – G – Am – F (I-V-vi-IV), or C – Am – F – G
TensionCm – F – Cm – G7 (i-iv-i-V), or Cm – Bb – Ab – G
Neo-soul / R&BCmaj7 – Em7 – Am7 – Dm7 (I7-iii7-vi7-ii7), or use modal interchange
Lo-fi / chillCmaj7 – Fmaj7 – Bb7 – Eb7 (mixolydian feel), or use ii-V-I in jazz extensions
Cinematic buildCm – Ab – Fm – G (Aeolian + V)
EDM upliftingAm – F – C – G (vi-IV-I-V — the "Axis")
Modal/dorianCm – F – Gm – Cm (i-IV-v-i in dorian)

3. Voice properly

For each chord, place voices according to instrument:

Piano (most common)

  • LH: Root + 5th (or root + octave) below middle C
  • RH: 3rd + 7th (or 3rd + 5th + 9th for color) above middle C
  • No closed-position triads in the same octave as the bass

String ensemble

  • Cello: root (one octave below middle C)
  • Viola: 5th (or 3rd in inversion)
  • Vln 2: 3rd or 7th (depending on chord quality)
  • Vln 1: highest color tone (9, 11, 13)
  • Respect ranges: Vln1 G3-G6, Vln2 G3-D6, Vla C3-A5, Cello C2-C5

Guitar

  • Use idiomatic guitar voicings, not piano-translated chords
  • Open chords for folk/indie
  • Drop-2 voicings for jazz
  • Power chords (root + 5th) for rock

Pad / synth

  • Spread across 2 octaves
  • Can use closed voicing in upper register for warmth
  • Avoid the muddy zone (root in same octave as bass synth)

4. Add color (optional)

If user wants "more color":

  • Add 9ths to major chords (Cmaj9 instead of C)
  • Add 11ths to suspended chords
  • Use 7ths consistently in jazz/neo-soul
  • Add altered tones (b9, #11) on V chords for tension

5. Voice leading between chords

When moving from one chord to the next, move each voice by the smallest interval possible:

  • C → F: keep C (root of C, fifth of F), move E down to F, move G up to A
  • Avoid parallel fifths and octaves between outer voices
  • Keep common tones static when possible

6. Apply

Write the chords to the target track using add_notes_to_clip. Each chord gets one full bar by default (override if user specified rhythm).

Don'ts

  • Don't write closed-position triads stacked in MIDI without thought to voice leading.
  • Don't ignore instrument range — Vln1 cannot play below G3.
  • Don't put all voices in the same octave (results in muddy mid-range).
  • Don't use 7-note voicings unless the user has a 7+ voice synth or rich pad — they sound like a fist on a piano.

Example

User: "Sad progression in F minor for piano"

Output:

  • Progression: Fm – Db – Ab – Eb (i-VI-III-VII)
  • Bar 1: LH F2-C3, RH Ab3-C4-Eb4 (Fm)
  • Bar 2: LH Db2-Ab2, RH F3-Ab3-Db4 (Db, common tone Ab held)
  • Bar 3: LH Ab2-Eb3, RH C4-Eb4-G4 (Ab, ascending top voice)
  • Bar 4: LH Eb2-Bb2, RH G3-Bb3-Eb4 (Eb, dominant pull back to Fm)

Apply with add_notes_to_clip. Length = 1 bar each, velocity 90 default.

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.