跳到正文
cccskills
免费在 GitHub 公开

release-director

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.

中文简介正在准备中。当前显示原文说明。

集成工具X (Twitter)

实测评分 未实测

查看安装方法

包含的文件(2)

  • SKILL.md10.5 KB
  • platform-guides.md4.6 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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


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:

# 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. 🎵

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

about

免费

Provides information about the bitwize-music plugin, its version, and its creator. Use when the user asks about the plugin, its purpose, version, or capabilities.

中文简介正在准备中。当前显示原文说明。

bitwize-music-studio/claude-ai-music-skills5852026年10月22日 更新

Creates visual concepts for album artwork and generates AI art prompts. Use during planning for concept discussion, or after all tracks are Final for actual artwork generation.

中文简介正在准备中。当前显示原文说明。

bitwize-music-studio/claude-ai-music-skills5852026年10月22日 更新

Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases. Use when planning a new album or reworking an existing album concept.

中文简介正在准备中。当前显示原文说明。

bitwize-music-studio/claude-ai-music-skills5852026年10月22日 更新

Shows a structured progress dashboard for an album with percentage complete per phase, blocking items, and status breakdown. Use for a quick visual overview of album progress.

中文简介正在准备中。当前显示原文说明。

bitwize-music-studio/claude-ai-music-skills5852026年10月22日 更新

Tracks and manages album ideas including brainstorming, planning, and status updates. Use when the user wants to add, review, or organize their album idea backlog.

中文简介正在准备中。当前显示原文说明。

bitwize-music-studio/claude-ai-music-skills5852026年10月22日 更新

clipboard

免费

Copies track content (lyrics, style prompts, streaming lyrics) to the system clipboard. Use when the user needs to paste lyrics or style prompts into Suno or other external tools.

中文简介正在准备中。当前显示原文说明。

bitwize-music-studio/claude-ai-music-skills5852026年10月22日 更新

查看 bitwize-music-studio 的全部技能

报告此技能的问题