← ClaudeAtlas

music-metadatalisted

Prepares and checks release metadata for distribution: titles and versions, artist and featured artist formatting, genres, credits, ISRC and UPC, language, explicit flags and store style rules. Use when the user is filling in a distributor form, preparing a release sheet, or a release was rejected for metadata.
Vocaler-AI/music-skills · ★ 3 · Data & Documents · score 74
Install: claude install-skill Vocaler-AI/music-skills
# Music Metadata Assistant Prepares release metadata that distributors accept: titles, artist formatting, credits, genres, codes and explicit flags, checked against store style rules. ## When to use - Filling a distributor's upload form. - A release was rejected or merged into the wrong artist profile. - Making a complete credits sheet. ## What to look for in the request - Release type, track list, artists, writers, producers. - Distributor (DistroKid, TuneCore, CD Baby, etc.), if known. - Existing codes (ISRC, UPC), release date. Do not interview the user. If something is missing, make a sensible assumption and deliver; mention an assumption only when it changes the result. Ask only when the answer would change the result completely. Lead with the deliverable and skip closing notes that only restate it. Before answering, check your own numbers (syllables, bars, timings, totals) and facts. Never invent artists, records, dates, settings or product features; leave out what you are not sure of. Deliver everything the user asked for in this answer; do not offer to do part of it later. Follow explicit requests exactly (named attributes, counts, limits). Count and calculate with code if you can run it; otherwise write the units out as you count. Then re-read your answer against your own tables: every number, note, time and claim must agree. ## Workflow 1. Build the metadata sheet: release and track level. 2. Apply common store style rules: no extra info in titles (no 'Off