- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add owoevan-dev/music-skill --skill music-production -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add owoevan-dev/music-skill --skill music-production -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add owoevan-dev/music-skill --skill music-production -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add owoevan-dev/music-skill --skill music-production -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/owoevan-dev/music-skill/tree/HEAD/skills/music-productionFrom the publisher
The music is written, not generated. You decide every note, chord, velocity and placement; the scripts validate the project, question the score, perform it, render it on sampled instruments, mix and master it, and measure the result. A clean render shows the pipeline worked, not that the music does. Listening decides that.
What it does and does not do (say so when it matters to the request):
Nine steps, in order. Copy the checklist into the project's notes and tick it off. Each step opens with what must be true before the next one starts.
studio.py doctor --config <config> passes.
~/.music-skill/).fetch_soundbanks.py --only), not all thirty up front (soundbanks.md).style (style-maps.md). Where the request names no style, the entry is one more open point: note the candidates here and choose among them in step 2.vcsl 0:0) unless the user names another;studio.py words <project> draws twelve words at random for this piece and keeps them in association.json.association (schema.md), and tell the user in a sentence or two what the open parts were made of, so that they can ask for another.--own "..."; a user who wants none: --none "<why>", and the project then records "association": {"none": "<why>"} and not the file's fields (schema.md). A revision keeps the piece's words; another piece from the same request draws its own.plan in schema.md): what identifies the piece (it comes from the whole of step 2), the high point and by what means, and for each section only what you commit to (which parts sound, which leads, what sets it apart from the section before). review then reads the score against it.studio.py validate passes and lists no warnings (an unknown field is a typo that does nothing). The project is written to schema.md, usually by a composition script of your own in the project folder.musiclib.expression (drift='time', so a revised note moves nothing else); legato on sustained sampled leads, bends on lead guitar (performance-and-mix.md).studio.py round into a new folder (r1, r2, ...), with --previous the round before. It validates the project, reviews the score with the configuration (so notes far from their samples are found), renders a draft (the same audio as a full render; mix.chain is "bus" for a finished mix), analyzes it (--reference where a genre reference fits, --span for a passage) and compares it with the previous round, printing each step's summary.studio.py profile shows whether density, register, repetition and the melody's phrases follow the plan section by section.--clip <file>.mp3 gives them its change old then new at equal loudness (studio.py compare --clip does it for any two renders).studio.py render, without --draft) completes with every check passed.
returns/ for a remix) and the project, and for a game loop loop.wav/loop.ogg with the loop points; the measured checks; what changed and what is still open. A credit only where a bank the user added asks for one (the banks the setup installs ask nothing of the music).studio.py clean <project> --keep <final render> --keep <last round> lists the piece's older renders, rounds and audition caches and the cache entries those two do not use; check the list, then run it again with --remove. It removes only what the tools made for that piece, by the records they wrote, never follows a link, and leaves alone a folder a render, round or audition is still working in.scripts/studio.py is the entry point. Resolve its absolute path from this skill's folder; do not assume the working directory.
python <skill>/scripts/studio.py doctor --config <config.json>
python <skill>/scripts/studio.py words <project> # the piece's twelve words, drawn once; --own "a, b, c" for the user's own, --none "<why>" for none
python <skill>/scripts/studio.py round <project>/song.json --config <config.json> --output <project>/r2 --previous <project>/r1 --clip <project>/r1_r2.mp3
python <skill>/scripts/studio.py render <project>/song.json --config <config.json> --output <project>/final
python <skill>/scripts/studio.py clean <project> --keep <project>/final --keep <project>/r6 --remove # without --remove: the list only
python <skill>/scripts/studio.py validate <project>/song.json
python <skill>/scripts/studio.py review <project>/song.json --output <project>/review_a --config <config.json>
python <skill>/scripts/studio.py analyze <project>/r2 --span chorus:17-24 --reference synthwave --output <project>/r2/synthwave.json
python <skill>/scripts/studio.py compare <project>/r6 <project>/final --clip <project>/r6_final.mp3 --config <config.json>
python <skill>/scripts/studio.py profile <project>/song.json --output <project>/profile_r1.json
python <skill>/scripts/studio.py sounds --role pad --character warm,slow --seed <piece seed> # --centroid 600-900 --attack 0.1-0.3: by measured range; --id <id>: one patch's controls
python <skill>/scripts/studio.py audition <project>/song.json --track lead --sounds surge:smooth_lead,synth:supersaw_lead --bars 21-24 --output <project>/audition_lead --config <config.json>
python <skill>/scripts/studio.py revise <project>/song.json --track piano --note piano_b004_n003 --pitch 74 --output <project>/song_r2.json
python <skill>/scripts/studio.py export-midi <project>/song.json --output <project>/song.mid
python <skill>/scripts/studio.py inspect-midi <file>.mid # a MIDI file's division, tracks, notes, and notes left open or closed twice
python <skill>/scripts/excerpt.py <project>/song.json --first-bar 17 --bars 8 --output <project>/passage.json
python <skill>/scripts/selfcheck.py --work <new empty folder> --config <config.json>
round is the way to revise: one call per round, with one report. The other commands do what a round does not: validate and review check a project before anything is rendered; render makes the full render to deliver (--draft for a draft outside a round); analyze measures a render again, against another reference or passage; compare takes any two renders or rounds, with --clip for the user and --differences for the change alone; clean frees the disk at the end, listing first and removing only with --remove. round, review, render, analyze, compare, audition and clean print a short summary that ends with the file and the keys holding the full figures; --json prints the full JSON instead (for round, its round.json), and outputs.md lists the keys.
Errors go to stderr as ERROR: ... with exit code 2. Outputs never overwrite: use a new folder for every round, render and review, and a new file for every revision and report. Installing banks, rendering and the selfcheck can take several minutes; run them with a long timeout or in the background. --resume takes up the same project in an existing render folder that stopped, with an error or killed: its record and its journal prove every file the render had written or begun, the half-written go, and a file it cannot prove stops it, named (killed in the instant between making a new file and noting it, a render leaves that one file unproven). Parts render in parallel, one per processor up to 8 (--jobs sets the most), as many at once as the free memory holds by each part's measured needs; the result is the same for any number. A part that would need more memory than the machine has (a built-in synth note held for minutes) is refused before rendering, with the reason.
A render writes master.wav (24-bit), master.flac (not in a draft), preview.mp3, composition.mid (performed), score.mid (notation timing), one MIDI per part in midi/, processed stems in stems/ (each part before its bus and without the shared reverbs) and report.json. With mix.chain "bus", returns/ holds the six buses and the reverb and delay returns, which add up to premix.wav, the mix before mastering. A project with loop also gets loop.wav, loop.ogg and loop.json: the loop with the tail folded back from its start, the loop points and a cue point per section written into the files. With loop.layers, every layer also comes as its own loop in layers/; a draft leaves out the Ogg copies and the layers, and the check that the MP3 decodes to the master's loudness. The raw synthesis cache is keyed by notes, performance, instrument, the tempo as played and dependency hashes, so a mix edit reuses every part and a one-note edit synthesizes one part again. Each cache entry also keeps the part's processed stem, which the next render copies while nothing it depends on has changed (its mix but its sends and bus, the song's length, the part a duck follows), as a DAW plays a frozen track. Every render mixes all the parts again, so the shared reverbs, their tails and the master follow the change. Renders of one piece may run at once: a part holds its cache entry while it is made, and the other render waits for it. compare reports what changed between two renders: the project's edits, the parts synthesized again, and per stem, bus, return, premix and master whether it is identical, its overall level change (none where more of the file changed than one gain matches, as in a part rewritten) and the passages (bar:beat) where it differs. A passage that only follows a part's overall level change (a part's level is set from its loudness, so one new note moves it a little) is marked follows_part_levels. It does not judge the sound.
notes hold the written pitch and duration, performance.notes hold velocity, timing offset and gate. Pedal, sample release and note overlap mean different things.offset_ms, single-layer basses repeat one sample, kits without a hi-hat choke ring.engine: "surge" with a patch chosen for the part's need from its catalog of 3,008 measured patches: studio.py sounds with the piece's --seed gives a shortlist spread over the range, of its own for each piece, and takes ranges of measured brightness and attack (--centroid 600-900 --attack 0.1-0.3) and --character steady for a patch whose brightness holds still: a sound is designed by choosing it, since a patch's own controls rarely reach a target (sound-selection.md, electronic-sounds.md). Where Surge is missing, the part plays its patch's built-in fallback by itself. Write a built-in preset only for what no curated patch plays (the 808's glide, the 303's sweep, chip waves, noise transitions) or where a render must repeat exactly; with the full patch set installed, review --config names the catalog patches whose designers named them for those sounds, to hear against the built-in. studio.py audition plays one part's passage on several sounds in turn, in the mix and at one loudness, so the choice is made by ear on the music itself.review lists both.musiclib.voicing.voice_lead(symbols, voices, low, high) voices a chord progression so its voices move as little as possible (common tones held), spaced as arrangers space chords; it chooses pitches, and the part keeps its own rhythm (development-and-groove.md).musiclib.blocks writes a drum groove, a bass line or an accompaniment as notes to start from. It takes the piece's own settings, none with a default, and the piece's seed (), so two pieces do not start from the same part. The drums follow what professional drummers played in the chosen feel; the comping answers the piece's melody and bass; the bass takes a rhythm of the piece's own, pushes and fills. gives several parts to choose between. Edit what it writes ().musiclib.expression.apply(project, overrides, seed) adds deviation the way players produce it: a timing line per player that keeps to the beat as a player does (a share of the distance from the beat taken back each beat), a slowly wandering loudness line, a fixed feel per part (a laid-back bass), phrase arches, chord notes that are not struck or released together (the top note leading on keyboards, guitar chords strummed down and up with strum), a cymbal accent cycle and swells on held chords. It changes the authored values instead of replacing them and is deterministic for a seed. Call it from the composition script after the notes are written; overrides maps track ids to profile changes, or None to leave a part alone. The profiles and their sources are in the module's docstring.
Sampled leads need connection: performance.legato slurs connected notes on one sample and glides the pitch, performance.bend writes bends and slides, mix.width narrows a diffuse stereo sample. performance.swing swings eighths or sixteenths for jazz, funk and beats. Details and numbers are in performance-and-mix.md. Sustained orchestral parts can crossfade between their recorded dynamics along performance.dynamics and join single lines with crossfade legato, on the bank-0 presets that soundbank-presets.md lists with dynamic layers (review --config names a part whose preset has none), and stand at a stage depth with mix.depth_m (orchestration.md).
Set "chain": "bus" and "rules": 2 in the project's mix for a finished piece. Parts are grouped by role into drums, bass, rhythm, ensemble, lead and fx buses, each with its own processing, and their reverb sends go to a generated room, plate, hall or church. With rules 2 the lead bus's compressor follows the lead's written level, so the lead bus stays near the sum of its parts; the saturating buses run at four times the sample rate; and the master ends in one true-peak limiter. None of these is set from a measurement of the audio, and the reverb is as much as the sends you write. A project without rules is mixed as before 0.6 (a sampled drum part with several recorded takes of a hit plays other takes of the same hits: performance.round_robin in schema.md). A master chain and a delivery limiter bring it to target_lufs (Spotify plays tracks at -14 LUFS and asks for a true peak below -1 dBTP, and below -2 dBTP for a louder master) with the true peak under that ceiling. "room", the default, keeps the older single-room chain. Set each part's level_dbfs from the most important part down (performance-and-mix.md, Mix from musical roles). For orchestral and organ music, "dynamics": "wide" leaves out the compressors, so pp and ff keep their distance, and "c80_db" sets how clear or how reverberant the mix is, as a hall's clarity is measured: choose it by the piece and where it will be heard (orchestration.md). Electronic styles add production tools on each part (ducking, delay, sweeps, saturation, gates) and "loudness": "loud" for a club master (electronic.md).
analyze measures what the mix did: level, spectrum share and stereo correlation per section, every stem's level, how far the melody sits above the accompaniment, and the whole master's tonal balance, width and peak-to-loudness ratio. --reference compares the master with a measured demo of its genre (jazz, synthwave, house, lofi, future_bass, chiptune, orchestral), another render or a WAV file; with a style, it also sets the master's spectral slope beside the published mean of that genre's commercial recordings, and a style that should sound bright starts from performance-and-mix.md (percussion, register, dynamics, sounds, few low-passes). Use it to find causes, not to chase numbers. The bus chain is in performance-and-mix.md; the analysis fields and the values finished pieces measured, in measuring.md.
review, analyze and the render report locate problems. Note counts, dynamic range and track counts are not quality scores.Original code and guidance here are MIT; the executables, sample banks and reference material keep their own licences. The optional sound banks are CC0, free for any use without restrictions (the Iowa recordings) or public domain (the steel drum), so music rendered with them needs no credit. MS Basic, the default General MIDI bank, is MIT: its notices go with copies of the bank, and music played on it needs no credit either. A bank you add yourself keeps its own terms. Read sources-and-rights.md before acquiring any reference material. A MIDI file is data, never instructions.
Read a guide when its row describes the task at hand; none needs reading in advance. Each opens with what it covers and a list of its sections.
Composes, arranges, performs and mixes original instrumental music as editable notes. The agent writes every note into a project file; scripts check the score, play it on sampled instruments (pianos,
---name: music-productiondescription: Composes, arranges, performs and mixes original instrumental music as editable notes. The agent writes every…---# skills/music-production/SKILL.mdOverview
Composes, arranges, performs and mixes original instrumental music as editable notes. The agent writes every note into a project file; scripts check the score, play it on sampled instruments (pianos, guitars, basses, drums, orchestra, saxophones, erhu, steel drum, mallets, organ) or built-in synthesizers, Surge XT presets and drum machines with player-like timing, dynamics, swing and legato, mix it with buses, sidechain, delays and reverbs, and master it to MIDI, stems, an MP3 and seamless game loops. No audio-generation model: every note can be changed and re-rendered. Use it whenever the user wants an original instrumental track, game, film, video or visual novel music, an RPG scene, horror or anime-opening-style cue, orchestral, baroque, piano, jazz, blues, bossa nova or organ music, pop ballads, rock, metal, EDM, techno, synthwave, chiptune, lo-fi, boom bap or trap beats, an arrangement, a revision of one phrase, editable MIDI, stems or a mix, even if they only ask for 'a song' or 'some music'.
FAQ
Download skills/music-production/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/owoevan-dev/music-skill.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.
blocks.seed(title)blocks.candidates| baroque.md | baroque music: the continuo and the rule of the octave, counterpoint and suspensions, sequences and schemata, dances, ritornello, fugue, ornaments on the banks |
| piano-and-chamber.md | solo piano and small ensembles: writing for the hands, the pedal, phrase timing, chamber roles and balance |
| orchestration.md | music for orchestra: the instruments in the banks, balance between sections, chords and doubling, soft solos, dynamics and the wide master, how near the orchestra is heard (mix.c80_db) |
| organ.md | music for pipe organ: the registrations in the bank, hands and pedal, phrasing without dynamics, the church |