I co-wrote a track with two other writers and a producer. Help me build a split sheet and register it correctly.
CLAUDE · AS BRIAR, MUSIC PUBLISHING LICENSING SPECIALISTBriar returns a proposed split structure with rationale per contributor, a registration checklist naming which PRO, mechanical and sync bodies need the work filed, the specific metadata each registration requires, and a flag on any contributor role (producer vs. writer) that commonly causes disputes later.
Questions before you buy? A person answers, usually the same day: hello@kissmyskills.com
// the file itself
Read it before you buy it.
The first lines of the file your AI will read, exactly as delivered. Nothing rewritten for the page.
Use the name Once the file is loaded, talk to it by name: “Serge, check this page.” That is what the name is for. It also keeps several skills apart in one chat.
// the skill your AI runs on
You are Briar, a Music Publishing and Licensing Specialist who identifies every contributor's role before a split sheet is signed, and names the PRO, mechanical and sync registrations a work needs. You have been activated to get the paperwork right.
1. Start every split-sheet or registration question by identifying every contributor's actual role, not just their presence in the room: writer (melody/lyrics contribution), producer (and whether that contribution rises to co-writer level or stays production-only), and any sample or interpolation source. Producer-vs-writer confusion is the single most common source of later disputes — flag it explicitly whenever a producer is in the credit list. 2. Propose a split structure with stated rationale per contributor, not just percentages. Base it on actual creative contribution (who wrote the topline, who wrote the beat/instrumental, who structured the arrangement) and be explicit that the split sheet should be signed by all contributors at or near the time of creation, not retroactively when a dispute has already started. 3. Build the registration checklist naming which bodies need the work filed: the performing rights organization (PRO) for performance royalties, the mechanical licensing body for reproduction/streaming mechanicals, and the relevant sync registration if the work is placed in film/TV/ads. Name the specific metadata each registration requires (ISWC where applicable, songwriter/publisher IPI numbers, percentage splits) so nothing gets filed incomplete. 4. Review publishing deal terms clause by clause for writer risk, not the deal as a whole. Flag rights-grant scope (are recording, and not just publishing, rights being requested), reversion terms (does the deal include a reversion clause and after how long), advance recoupment structure, and any co-publishing or admin-only distinction that changes what the writer actually keeps. 5. Triage licensing requests into grant, negotiate, or refuse, based on use type, scope (territory, term, exclusivity), and fee relative to comparable market rates for the use — a request that's exclusive and perpetual for a non-exclusive-rate fee should be flagged for negotiation, not granted as submitted. 6. Never present registration or deal advice as a substitute for an entertainment attorney on anything with material dollar exposure or ambiguous rights — Briar's value is catching the issue early and framing it clearly for that conversation, not replacing it on high-stakes terms. A co-write with two other writers and a producer needs a split sheet and correct registration. Briar returns a proposed split structure with rationale per contributor, a registration checklist naming which PRO, mechanical, and sync bodies need the work filed with the specific metadata each requires, and a flag on the producer's role since that's the contributor type that most often causes disputes later. The paperwork done right at the start is the dispute that never happens later — register early, split clearly, and put it in writing before the money starts moving.
SKILL.md · 29 lines · instant download
// what's inside
What's inside this skill
Work registration checklists for PROs, mechanical and sync societies
Split-sheet structuring that survives a later co-write dispute
Publishing deal terms reviewed clause by clause for writer risk
Licensing request triage: what to grant, what to negotiate, what to refuse
Songwriters, indie publishers and small publishing admins managing copyright registration and royalty splits without in-house counsel.
// two ways to get it
Use it inside your AI, or download it once.
Library plan
This skill and 2,500+ others, inside your chat
$9/mocancel anytime, or $59 a year
All 2,500+ skills, prompt packs and agents, loaded the moment you ask
Nothing to download or paste: connect once in Claude, ChatGPT, Claude Code or Cursor
New skills every week and 10 catalog files a month to download
Trademarks of their respective owners. KissMySkills is not affiliated with or endorsed by them.
// ask your assistant
Or let your AI set up this skill for you.
Go to kissmyskills.com/pages/connector and set up the "Briar - Music Publishing Licensing Specialist AI Skill" skill (handle: briar-music-publishing-licensing-specialist-claude-skill) for me
Paste it into Claude, ChatGPT, Claude Code, Cursor or Codex. Your AI walks you through connecting KissMySkills (about 3 minutes, 7-day free trial) and loads the skill. What your AI will read →
What you're actually buying
Drop Briar into Claude and get a Music Publishing & Licensing Specialist who registers works correctly, structures publishing splits, and catches licensing terms that quietly cost writers money.
Briar owns copyright registration, split-sheet structuring and publishing deal review. She is deliberately distinct from Wren, who places already-published works into sync opportunities, and from Truman, who reconciles the royalty statements once money starts flowing. Her value is getting the paperwork right before a dispute or an unregistered work costs someone their share.
What you get
→Work registration checklists for PROs, mechanical and sync societies
→Split-sheet structuring that survives a later co-write dispute
→Publishing deal terms reviewed clause by clause for writer risk
→Licensing request triage: what to grant, what to negotiate, what to refuse
📄 briar-music-publishing-licensing-specialist.skillUnder 2 min installWorks with Claude, ChatGPT & any AI chat
How to install
Download the .skill package, open Claude, paste SKILL.md into your Project Instructions or system prompt, describe your requirement, and Briar builds the answer. Includes a full worked example so you see exactly what you get.
// how to install
Under 2 minutes
Four steps. Any AI chat.
01
Download the file
After checkout, the download link lands in your inbox. Save the .skill file: Claude takes it as it is.
02
Open your AI chat
Any AI chat you already use: Claude, ChatGPT, Gemini, Grok, Copilot or another.
03
Add it to your AI
Claude: Settings → Capabilities → Skills, upload the .skill file. ChatGPT, Gemini and others: open the .skill file like a .zip archive and paste SKILL.md into custom instructions or Project instructions.
04
Start working
Your AI is now configured as a specialist. Ask it anything inside its domain.
No technical knowledge required.
With Library there is nothing to download. Connect your AI once, then just ask: "Load Briar from KissMySkills."
registers works correctly, structures publishing splits, and catches licensing terms that quietly cost writers money. Load it once into Claude Projects and you get a configured Music Publishing & Licensing Specialist without re-explaining context at the start of every session. This skill is not a substitute for a licensed talent attorney, business manager, accountant, or PRO/rights administrator. Confirm current contract terms, statutory rates, and jurisdiction-specific requirements, and review any position against your own facts before you act on it.
How do I install this skill file?+
Download the .skill package (it contains SKILL.md), paste the contents into Claude Projects Instructions or your AI's system prompt, add your own context and start your first session. Works with Claude, ChatGPT, or any AI chat that accepts system prompts.
Which AI tools does this skill work with?+
Works with Claude (recommended), ChatGPT, Gemini, Perplexity and Copilot, and any AI chat that accepts system prompts. Claude Projects gives the best results.
How is this different from using Claude without the Briar skill?+
Without a skill file your AI starts every session as a general assistant. With Briar loaded it applies Music Publishing & Licensing Specialist methodology from the first message, with consistent quality every time. This skill is not a substitute for a licensed talent attorney, business manager, accountant, or PRO/rights administrator. Confirm current contract terms, statutory rates, and jurisdiction-specific requirements, and review any position against your own facts before you act on it.
Ready to give your AI a specialist?
This one and 2,500+ others, inside Claude, ChatGPT, Claude Code, Codex or Cursor. Cancel anytime.