agentleFS
bitwize-music-studiobitwize-music-studio/claude-ai-music-skills/skills/release-kit/SKILL.md

release-kit

Skill668 starsChanged 10 months agoCC0-1.0View on GitHub

Builds everything the DistroKid and SoundCloud upload forms ask for, so uploading an album is pasting, not typing. It makes a page with every field and a copy button, the audio and cover paths, and the checks to clear first. Nothing touches either site. Use when the user is ready to upload an album, says "release kit", "upload sheet", "get it ready for DistroKid" or "what do I paste into SoundCloud".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Every run rebuilds both from the album files and config.

    line 26

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

Your Task

Input: $ARGUMENTS

Build the album's release kit and open it. The user then fills in the DistroKid and SoundCloud forms from it, and submits them, themselves.


Release Kit Skill

build_release_kit writes two files into the album's audio folder, beside mastered/:

  • release-kit.html: every value each upload form asks for, with a copy button, and the checks
  • release-kit.json: the same data

Every run rebuilds both from the album files and config.

Never automate either site. DistroKid's terms bar "any high volume, automated, or electronic means to access the Services (including, without limitation, robots, spiders or scripts)". Don't open, fill or submit either form. The user pastes, uploads and submits.

Step 1: Find the Album

find_album(<album-name>). If it isn't found, say so and stop.

Step 2: Build

build_release_kit(album_slug). It opens the page in an iTerm2 pane beside the session when panes work there, and in the default browser otherwise.

  • An error: show it and stop. That happens for an unknown album, or one with no audio folder yet (master it first).

Step 3: Report

Lead with what blocks the upload, then the advice:

Release kit for Paper Boats: open beside you (iTerm2 pane)
✗ 2 to fix first:
  - Set artist.legal_name in config: DistroKid needs the songwriter's real name
  - The cover is 3000×2000: it must be square
⚠ 1 to look at:
  - Track 4 (Tide) has explicit words but isn't marked explicit
Files: …/release-kit.html

With nothing ✗ or ⚠: "Ready: paste from the page into DistroKid and SoundCloud."

Step 4: Fixes

Offer the fix for each item, and rebuild after any change:

CheckFix
no mastered WAV, stray WAV/bitwize-music:mastering-engineer; move strays out of mastered/
cover missing or too small/bitwize-music:import-art
artist.legal_name, release.ai_disclosure/bitwize-music:configure, or edit ~/.bitwize-music/config.yaml. The AI answer is the user's own statement: ask, never pick
release datethe album README's release_date
titles, explicit flags, Streaming Lyricsthe track files (/bitwize-music:lyric-writer for lyrics)
an ISRC or UPC that isn't onethe track's isrc: or the album README's upc:: copy the code from the distributor, or delete the line and DistroKid assigns one

Remember

  1. Nothing touches DistroKid or SoundCloud. The user pastes, uploads and submits.
  2. The AI disclosure is the user's answer. The kit shows release.ai_disclosure exactly as configured.
  3. Rebuild after every fix. The page is generated, so edit the source, not the page.
  4. The legal name stays out of git. It lives in config, and the kit lives beside the audio.

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.