How to use the Rekordbox DJ Library CLI agent skill

What the skill lets the agent do

The skill gives an agent access to a command-line interface (CLI) for Rekordbox. The CLI works in two areas. The library side reads your Rekordbox track database (master.db) to count tracks, search by title or artist, show full metadata for a track and export the whole library to JSON. The playlist side lists playlists and creates, adds to or empties them.

The live-deck side sends virtual MIDI signals to Rekordbox to play or pause a deck, tempo sync, crossfade between decks, adjust EQ and trigger hot cues. It can also install a MIDI mapping file (Bunker.midi.csv) into Rekordbox's MidiMappings folder. The source describes this as a harness that combines the encrypted database and MIDI, because Pioneer does not provide a playback REST API.

Install the skill from the ZIP or the Claude apps

Download the skill ZIP from this page. The skill is a folder whose main file is SKILL.md. To use it with Claude Code, unzip it into your personal skills folder ~/.claude/skills/, or into a project's .claude/skills/ folder if you want it available only in that project.

To use it in the Claude apps instead, upload the skill under Settings, then Capabilities, then Skills.

• Personal (all projects): ~/.claude/skills/
• Single project: the .claude/skills/ folder inside that project
• Claude apps: Settings → Capabilities → Skills, then upload

Install the Python package and check prerequisites

The skill calls a Python package, so you need to install it before the agent can do anything useful. The source lists these requirements: Python 3.10 or newer, Rekordbox 6 or 7 installed with master.db present, and the cli-anything-rekordbox pip package, which pulls in pyrekordbox and mido.

For live-deck control you also need a virtual MIDI driver. The source names loopMIDI, LoopBe or teVirtualMIDI on Windows, the IAC Driver on macOS and ALSA snd-virmidi on Linux.

• Python 3.10+
• Rekordbox 6 or 7 with master.db present
• Virtual MIDI driver only if you want live-deck control

Check the setup and try the CLI yourself

Before asking the agent for anything, run the status command. The source describes it as showing the runtime, database and MIDI state. Every command also accepts --json, which is the format the agent reads. Running a query yourself first helps you confirm the install works and see what the output looks like.

Library commands are read-only in the source's description. Search matches a title or artist substring, so a short distinctive word usually works better than a full phrase.

• status: runtime, database and MIDI state
• count: total track count
• search QUERY: find tracks by title or artist substring
• info TRACK_ID: full track metadata
• dump --out FILE.json: export the full library as JSON

Trigger the skill with natural requests

You do not need to name commands. Describe the outcome you want and mention Rekordbox, so the agent knows which skill applies. The agent chooses the matching command. Requests that work well are specific about the track or playlist name and state whether you want a change made.

Ask for a read first when you are unsure. For example, asking how many tracks are in your library or which tracks match an artist is a lower-risk request than asking the agent to build or clear a playlist.

• How many tracks do I have in Rekordbox?
• Find every track by Daft Punk in my library and list the titles.
• Export my Rekordbox library to a JSON file called library.json.
• Create a playlist called Warmup and add the track Get Lucky to it.
• Empty the playlist Warmup. Make a backup first.

Safety: backups, Rekordbox state and network

Playlist writes (create, add, clear) back up master.db before changing it. They refuse to run while Rekordbox is open unless --force is supplied, and forced writes still require a backup. The --no-backup option is accepted only when Rekordbox is closed. Keep your own copy of master.db before any write, because the source says --force and --no-backup can bypass the checks.

The skill runs scripts (the source says yes) and does not use the network (the source says no). The source also notes that master.db is encrypted with a static AES-256 key shared by Rekordbox 6/7 installs, which pyrekordbox extracts automatically. Live-deck MIDI control can disrupt a performance, so do not let an agent run it unattended during a set.

• Make your own backup of master.db before any playlist write
• Close Rekordbox before writes unless you deliberately use --force
• Test on a copy of your library first if you can
• Do not use live-deck commands unattended during a performance