agentleFS
glinckerglincker/ableton-skills/skills/reference-match/SKILL.md

reference-match

Skill32 starsChanged 55 days agoMITView on GitHub

Use when the user references another track they want to emulate the vibe/sound of. Examples - "make this sound like Ólafur Arnalds", "I want a Tame Impala vibe", "match the mix of Kendrick's Money Trees". Translates artist/track references into actionable production decisions.

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:

    Ask if not given: "Which track or artist?

    line 14
  2. Distinctive:

    Use the right synth patches (vintage analog vs modern digital)

    line 47
  3. Distinctive:

    Don't apply everything blindly.

    line 57
  4. Distinctive:

    After the user listens, refine based on what's still wrong.

    line 63
  5. Distinctive:

    Don't claim to "exactly clone" anyone's sound.

    line 67
  6. Distinctive:

    Don't download or process copyrighted audio.

    line 68
  7. Distinctive:

    Don't recommend specific sample packs unless they're public (Splice, Output) and the user has them.

    line 69
  8. Distinctive:

    Don't apply more than 3 reference moves before letting the user listen.

    line 70

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

Reference Match

Translate a reference track or artist into concrete production choices. We do not download or analyze copyrighted audio. We use known sonic signatures and the user's own ears.

Workflow

1. Identify the reference

Ask if not given: "Which track or artist? And which aspect — the arrangement, the mix, the sound design, or the overall vibe?"

2. Pull the sonic signature from common knowledge

Map the reference to its known characteristics. Examples:

ReferenceSignature
Ólafur ArnaldsFelt piano, string ensemble (often Spitfire), tape saturation, slow tempo (60-80), minor key, sparse arrangement, long reverb tails, microphone proximity sound
Tame Impala (Currents-era)LinnDrum patterns, OP-1 synths, heavy chorus on guitar, vocoded vocals, sidechained bass, 60-90 BPM, vintage drum saturation
BonoboLive percussion + electronic drums, jazz harmony, vinyl crackle textures, mid-tempo (90-110), wide stereo, heavy use of sample chops
BurialVinyl/cassette texture, rain/atmosphere, pitched-up vocal samples, sub bass, garage-2step rhythm, lo-fi hihats, minor 7 chords
Kendrick (DAMN era)808 sub, trap hi-hats, jazz samples, vocal layering, heavy compression, mid-side EQ for vocal width
Billie Eilish (early)Whisper vocal up close, sparse 808, finger snaps, sub-heavy mix, heavy automation, breath sounds intentionally left in
SkrillexHeavy modulation on bass (vocal-formant LFOs), drops with stutter edits, 14k+ shimmer on leads, super-wide stereo, side-chained pump
Hans ZimmerMassive low brass (often layered with synth), Trinity choir (low + bright), pulsing ostinatos, slow chord swells, 1-second+ reverb tails
Lo-fi hip hop (Lofigirl-style)Wurlitzer/Rhodes, jazz chords, vinyl crackle, tape saturation, 70-90 BPM, 50% wet drums, swung 16ths

3. Translate to action

For each aspect the user cares about, propose moves:

Arrangement

  • Match section structure (Bonobo = long intros; Skrillex = constant motion)
  • Match density (Billie = sparse, Skrillex = dense)

Mix

  • LUFS target (lo-fi/Bonobo: -10 to -8 LUFS, modern pop: -8 to -6, cinematic: -16 to -14)
  • Stereo width (cinematic: narrow; EDM: very wide)
  • Frequency balance (trap: heavy 50-80Hz; folk/acoustic: balanced midrange)

Sound design

  • Pick instruments matching the era/style
  • Use the right synth patches (vintage analog vs modern digital)
  • Match drum kit character (vinyl sample vs modern punchy)

Effects

  • Reverb type (Hall for cinematic; Plate for vocals; Spring for surf-rock; Room for tight modern pop)
  • Tape/vinyl saturation (essential for Bonobo, lo-fi, Tame Impala)
  • Chorus (Tame Impala, dream pop, '80s)

4. Ask the user to listen and direct

Don't apply everything blindly. Pick the 3 most distinctive elements of the reference and propose them first:

"Top 3 Ólafur signatures I'd start with: (1) felt piano via Spitfire Originals or stock Grand Piano with the lid closed setting + tape sat; (2) slow swelling string pad with 2-second attack + reverb send 40%; (3) tempo 70 BPM, minor key, 4/4 but with rubato feel via velocity-driven micro-timing. Apply these first, listen, then iterate?"

5. Iterate

After the user listens, refine based on what's still wrong. References are inherently approximate — embrace the iteration loop.

Don'ts

  • Don't claim to "exactly clone" anyone's sound. We approximate the recipe.
  • Don't download or process copyrighted audio.
  • Don't recommend specific sample packs unless they're public (Splice, Output) and the user has them.
  • Don't apply more than 3 reference moves before letting the user listen.

When the reference is unfamiliar to you

If you don't know the reference: ask the user to describe what they like about it. ("Is it the drums? The vocal effect? The arrangement?") Then apply the technique that matches their description — you don't need to know the artist to translate "warm, lo-fi, jazzy chords" into action.

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.