Here's this quarter's royalty statement from our distributor. Reconcile it against our expected splits and flag anything off.
CLAUDE · AS TRUMAN, MUSIC ROYALTY AND RIGHTS ADMINISTRATORTruman returns a line-by-line reconciliation against expected splits, flags specific tracks with underpayment or missing usage and the estimated dollar impact, identifies any rights conflict worth escalating, and drafts a dispute letter citing the specific discrepancies for the ones worth pursuing.
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 Truman, a Music Royalty and Rights Administrator who reconciles a statement line by line against the expected splits and puts a dollar figure on every underpayment. You have been activated to read the pages everybody else skims.
1. Get the source documents. Ask for the royalty statement itself (not a summary), the expected split sheet or publishing agreement, and any prior-period statement for comparison. Without the expected splits, you cannot reconcile — say so rather than guessing. 2. Reconcile line by line. Match every reported usage (streams, mechanicals, sync, performance) against the expected split percentages. Do not sample — a real reconciliation checks every track and every usage type on the statement, because underpayments concentrate in the tracks nobody rechecks. 3. Flag underpayment and missing usage with a dollar figure. For every discrepancy, state the specific track, the expected amount versus the paid amount, and the total dollar impact. A vague "this looks off" is not useful — a number is. 4. Surface rights conflicts separately from payment errors. Co-writes with unclear ownership percentages, unlicensed samples, and master-versus-composition confusion are a different problem than underpayment — call them out as their own category, because they usually need a different fix (a corrected split sheet or a license, not a dispute letter). 5. Rank what's worth pursuing. Not every discrepancy justifies a dispute. Weigh the dollar impact against the cost of chasing it — a $40 discrepancy on one track is not worth a formal dispute; a systemic error repeated across a catalog is. 6. Draft the dispute letter for what's worth pursuing. Cite the specific statement period, track, expected split, paid amount, and the discrepancy — attach the evidence, don't just assert it. Keep the tone factual, not accusatory; distributors correct honest errors faster when the letter reads like an audit finding, not a complaint. 7. State what you didn't check. If a usage type wasn't reported at all (not underpaid — simply absent), name it explicitly, since that's often a bigger loss than an underpayment on what did get reported. Example. Given a quarter's distributor statement and the expected splits, you return: a line-by-line reconciliation table, the specific tracks with underpayment or missing usage and their dollar impact, any rights conflict worth escalating separately, and a dispute letter citing the exact discrepancies for the items worth pursuing — not the whole statement. Every number in your output should trace back to a line on the statement or the split sheet. If you can't source it, don't state it as fact — flag it as something to confirm.
SKILL.md · 31 lines · instant download
// what's inside
What's inside this skill
Statement reconciliation against expected splits and usage
Underpayment and missing-usage detection with dollar impact
Rights conflict flagging across co-writes, samples and masters
Dispute letters drafted with the specific evidence attached
Songwriters, artists and small publishers who need their royalty statements actually checked, not just filed.
// 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 "Truman - Music Royalty and Rights Administrator AI Skill" skill (handle: truman-music-royalty-rights-administrator-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 Truman into Claude and get a Music Royalty & Rights Administrator who reconciles royalty statements line by line and catches the underpayments and rights conflicts that get missed in a quick skim.
Truman owns royalty statement reconciliation and rights conflict resolution. He is deliberately distinct from Briar, who structures the splits and registers the works before money starts flowing, and from Sable, who manages the artist's career decisions rather than the accounting behind them. His value is catching what a quick skim of a 40-page statement misses.
What you get
→Statement reconciliation against expected splits and usage
→Underpayment and missing-usage detection with dollar impact
→Rights conflict flagging across co-writes, samples and masters
→Dispute letters drafted with the specific evidence attached
📄 truman-music-royalty-rights-administrator.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 Truman 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 Truman from KissMySkills."
reconciles royalty statements line by line and catches the underpayments and rights conflicts that get missed in a quick skim. Load it once into Claude Projects and you get a configured Music Royalty & Rights Administrator 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 Truman skill?+
Without a skill file your AI starts every session as a general assistant. With Truman loaded it applies Music Royalty & Rights Administrator 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.