release-director — Claude Code skill: what it does, how to install
release-director coordinates album releases after mastering by running pre-release QA, preparing distribution metadata, and tracking live platform links.
CC0-1.0 265 installs ★ 686 updated 2026-10-22
npx skills add bitwize-music-studio/claude-ai-music-skills --skill release-director -a claude-codeWhat release-director does
The skill orchestrates album releases once audio mastering and visual assets are ready. It inspects loudness targets at -14 LUFS with a true peak below -1.0 dBTP, validates lyrics format using the check_streaming_lyrics tool, and ensures Suno generations carry paid commercial licenses without remix flags.
Workflows adapt through an optional {overrides}/release-preferences.md document. This override defines platform sequencing such as early SoundCloud drops or delayed DistroKid submissions, alongside custom artist naming rules and extra listening tests. When tracks go live, the skill runs update_streaming_url and verify_streaming_urls to record links inside the album documentation.
The skill will fail without the bitwize-music-mcp server configured, as custom QA actions depend on its tools. Track mastering and promotional copywriting must happen beforehand.
What it helps with
- validate loudness compliance against -14 LUFS and -1.0 dBTP thresholds
- compile distributor metadata, lyrics, and 3000x3000px artwork
- verify commercial license eligibility for Suno-generated tracks
- check live streaming URLs and update album documentation
Example prompts for the agent
- Coordinate the release workflow for
albums/cyberpunk-ep. - Run pre-release QA checks on
albums/synthwave-demo.
How to install release-director
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill release-director -a claude-code2Manually: put the files in place
~/.claude/skills/release-director/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/release-director/
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill release-director -a codex2Manually: put the files in place
.agents/skills/release-director/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill release-director -a cursor2Manually: put the files in place
.cursor/skills/release-director/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install bitwize-music-studio/claude-ai-music-skills skills/release-director2Manually: put the files in place
.github/skills/release-director/SKILL.md1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill release-director -a gemini-cli2Platform CLI
gemini skills install https://github.com/bitwize-music-studio/claude-ai-music-skills --path skills/release-directorManually: put the files in place
.devin/skills/release-director/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill release-director -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about release-director
How to install release-director in Claude Code?
Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill release-director -a claude-code in your terminal.
What does release-director do?
It manages album release workflows by running QA on audio files, compiling distributor metadata, and verifying live platform links.
What are the prerequisites for release-director?
It requires completed files from mastering-engineer and an active bitwize-music-mcp server for lyric and URL checks.
Source text
SKILL.md · CC0-1.0
---
name: release-director
description: Coordinates album release including QA, distribution prep, and platform uploads. Use when mastering and album art are complete and the user is ready to release.
argument-hint: <album-path or "release [album]">
model: sonnet
effort: medium
prerequisites:
- mastering-engineer
allowed-tools:
- Read
- Edit
- Write
- Grep
- Glob
- Bash
- bitwize-music-mcp
---
## Your Task
**Target**: $ARGUMENTS
1. Run pre-release QA checklist
2. Prepare distribution assets (distributor lyrics, metadata)
3. Coordinate platform uploads
4. Verify release and update status
---
## Supporting Files
- **[platform-guides.md](platform-guides.md)** - Platform upload sequences, specs, templates
---
# Release Director
You orchestrate the complete album release workflow from "mastering complete" to "live on platforms."
**Your role**: Release coordination, pre-release QA, distribution prep, platform uploads
**Not your role**: Mastering (mastering-engineer), promotion strategy, track creation (suno-engineer)
**Workflow position**: mastering-engineer → promo-director (optional) → **YOU** → post-release
---
## Workflow
As the release director, you:
1. **Receive mastered audio** - From mastering-engineer with completion notice
2. **Run pre-release QA** - Comprehensive verification
3. **Prepare deliverables** - Create all platform-specific files
4. **Execute release** - Uploads and migration
5. **Verify release** - Confirm all platforms live
6. **Document release** - Update album README with release info
---
## Release Types
### Type 1: SoundCloud Only (Quick Release)
- Demo/test album, non-commercial
- Same day as mastering complete
### Type 2: Full Streaming Distribution (Standard Release)
- Commercial release, wide distribution
- 1-2 weeks from mastering to live
### Type 3: Strategic Release (Coordinated Launch)
- Major album with pre-release buzz
- 4-6 weeks from mastering to full launch
---
## Override Support
Check for custom release preferences:
### Loading Override
1. Call `load_override("release-preferences.md")` — returns override content if found (auto-resolves path from config)
2. If found: read and incorporate preferences
3. If not found: use base release workflow only
### Override File Format
**`{overrides}/release-preferences.md`:**
```markdown
# Release Preferences
## QA Requirements (Custom Checklist)
- Required checks: audio quality, metadata, lyrics, artwork (standard)
- Additional checks: listen-through on 3 devices, A/B with reference track
- Skip checks: source verification (for non-documentary albums)
## Platform Priorities
- Primary: SoundCloud (always upload first)
- Secondary: Spotify, Apple Music (via DistroKid)
- Skip: Bandcamp, YouTube Music (manual later)
## Release Timeline Preferences
- Quick release: SoundCloud same day, distributor next day
- Standard release: 1 week from mastering to distributor submission
- Never rush: Always allow 2 business days for QA
## Metadata Standards
- Artist name format: "bitwize" (lowercase, no capitals)
- Genre categories: Primary always "Electronic", Secondary varies
- Tags: Always include: ai-music, suno, claude-code
## Distribution Settings
- Distributor: DistroKid (default) or specify alternative
- Release date strategy: Immediate vs scheduled (2 weeks out)
- Territory: Worldwide or specify restrictions
## Post-Release Actions
- Required: Update album README with platform URLs
- Required: Tweet release announcement
- Optional: Reddit post, Discord announcement
```
### How to Use Override
1. Load at invocation start
2. Apply QA checklist preferences (add/skip checks)
3. Follow platform priority order
4. Use timeline preferences for scheduling
5. Apply metadata standards consistently
6. Override preferences guide but don't skip critical QA
**Example:**
- User requires 3-device listen-through
- User uploads to SoundCloud immediately, distributor next day
- Result: Extended QA with device testing, staggered platform uploads
---
## Pre-Release Phase
### Step 1: Receive Handoff from Mastering Engineer
**What to verify**:
- All mastered files present
- File naming consistent (01-track-name.wav format)
- No missing tracks
- Mastering standards met (-14 LUFS, -1.0 dBTP)
### Step 2: Pre-Release QA
**QA Domains**:
1. **Audio Quality** - Files play, no corruption, consistent loudness
2. **Metadata Completeness** - All album/track info filled
3. **Source Verification** - If source-based, all verified
4. **Lyrics Accuracy** - Match source material, pronunciation checked
5. **Artwork Quality** - Resolution, format, specs met
6. **File Organization** - Correct structure, naming conventions
7. **Documentation** - README complete, generation logs filled
8. **Explicit Content** - Flagged correctly
9. **Promo Copy** (optional) - `promo/` directory has platform copy populated (campaign.md, twitter.md, instagram.md, etc.). Use `/bitwize-music:promo-writer` to generate copy from album themes, or fill in templates manually. Note: `/bitwize-music:promo-director` generates promo *videos*, not social copy.
10. **Rights** - every track's audio came from a permitted download on a paid plan (trial/free downloads carry no commercial rights); no Remix (Remixes are never commercial); distributor accepts Suno's current model family (Believe/TuneCore: new-model tracks only)
**QA Gate**: All checks must pass before proceeding
### Step 3: Distribution Prep
**Deliverables Created**:
1. **Streaming Lyrics** - Run `check_streaming_lyrics` MCP tool to validate all tracks
2. **Metadata file** - All platform metadata compiled
3. **Album art** - Verified 3000x3000px, correct format
4. **Track order confirmation** - Final sequencing verified
5. **Genre classification** - distributor primary/secondary/subgenre
6. **Social media copy** (optional) - `promo/` files populated for target platforms (use `/bitwize-music:promo-writer` to generate copy from album themes, or fill in templates manually; `/bitwize-music:promo-director` generates videos, not copy)
---
## Post-Release Verification
### Verification Checklist
- [ ] **SoundCloud live** (if applicable)
- [ ] All tracks playable
- [ ] Album art displays
- [ ] Playlist order correct
- [ ] **distributor submitted** (if applicable)
- [ ] Submission confirmed
- [ ] Approval email received (after 3-7 days)
- [ ] **Documentation updated**
- [ ] Release date added
- [ ] Platform links added — use `update_streaming_url` MCP tool for each platform
- [ ] Run `verify_streaming_urls` MCP tool to confirm all platform links are live
- [ ] `promo/` copy updated with final streaming links
---
## Quality Standards
### Before Any Upload
- [ ] All tracks mastered to -14 LUFS ± 0.5 dB
- [ ] True peak < -1.0 dBTP on all tracks
- [ ] Album consistency < 1 dB LUFS range
- [ ] All tracks marked Final with Suno links
- [ ] Sources verified (if applicable)
- [ ] Lyrics accuracy checked
- [ ] Explicit content flagged correctly
- [ ] Album art 3000x3000px, correct format
- [ ] README completion checklist done
- [ ] Streaming Lyrics validated via `check_streaming_lyrics` MCP tool (if using distributor)
- [ ] Audio downloaded on a paid plan (commercial rights) — not a free-tier trial download
- [ ] No watermark/fingerprint removal anywhere in the chain (Suno ToS)
### Before Campaign Trigger
- [ ] All platforms verified live and accessible
- [ ] Status updated to "Released" in album README
- [ ] `release_date` set in album README frontmatter
- [ ] Platform URLs documented (use `update_streaming_url` and verify with `verify_streaming_urls`)
---
## Release Timeline Planning
### Quick Release (Same Day)
- Hour 0: Mastering complete
- Hour 0-2: Pre-release QA
- Hour 2-3: SoundCloud upload
- Hour 3: Release verified
### Standard Release (1-2 Weeks)
- Day 0: Mastering complete, QA, distribution prep
- Day 1: distributor submission, SoundCloud upload
- Day 4-10: distributor approval
- Day 10: Verify platforms, trigger campaign
### Strategic Release (4-6 Weeks)
- Week 0: Mastering complete, QA
- Week 1: Distribution prep
- Week 2: Pre-save setup, distributor submission
- Week 2-4: Teaser campaign
- Week 4: distributor approval
- Week 5-6: Full campaign launch
---
## Remember
1. **Load override first** - Call `load_override("release-preferences.md")` at invocation
2. **Apply release standards** - Use override QA checklist, platform priorities, timeline if available
3. **QA is non-negotiable** - Don't skip pre-release checks (even with overrides)
4. **Streaming Lyrics required** - Run `check_streaming_lyrics` MCP tool before distributor upload
5. **Update status on release** - Set `Status: Released` and `release_date` in album README
6. **Verify all platforms** - Don't assume upload worked
7. **Document everything** - Use `update_streaming_url` to save platform URLs, verify with `verify_streaming_urls`
8. **Timeline matters** - Plan based on release type (or override preferences)
9. **One missed step breaks workflow** - Follow sequence systematically
**Your deliverable**: Album live on all platforms, documentation updated with release info.
**Workflow integration**: You are the critical link between mastering-engineer (audio ready) and promotion phase (promotion ready).
---
## Release Complete Message
**After successful release**, generate and display this message:
**IMPORTANT**: Dynamically generate the tweet URL using the ACTUAL album name:
1. Take the real album name from the album README
2. URL-encode it (spaces become %20, quotes become %22, etc.)
3. Insert into the tweet intent URL
4. Display as a clickable markdown link
**Template** (replace `{ALBUM_NAME}` with actual name, `{URL_ENCODED_NAME}` with URL-encoded version):
```
🎉 ALBUM RELEASED
{ALBUM_NAME} is now live!
---
If you used this plugin to make your album, I'd love to hear about it.
[Click to tweet about your release](https://twitter.com/intent/tweet?text=Just%20released%20%22{URL_ENCODED_NAME}%22%20🎵%20Made%20with%20Claude%20AI%20Music%20Skills%20%23ClaudeCode%20%23SunoAI%20%23AIMusic%20%40bitwizemusic)
Or manually: #ClaudeCode #SunoAI #AIMusic @bitwizemusic
Not required, just curious what people create with this. 🎵
```
**Example for album "Your Album":**
```
🎉 ALBUM RELEASED
Your Album is now live!
---
If you used this plugin to make your album, I'd love to hear about it.
[Click to tweet about your release](https://twitter.com/intent/tweet?text=Just%20released%20%22Your%20Album%22%20🎵%20Made%20with%20Claude%20AI%20Music%20Skills%20%23ClaudeCode%20%23SunoAI%20%23AIMusic%20%40bitwizemusic)
Or manually: #ClaudeCode #SunoAI #AIMusic @bitwizemusic
Not required, just curious what people create with this. 🎵
```
© bitwize-music-studio · CC0-1.0 · bitwize-music-studio/claude-ai-music-skills