band-agreement
Write the band agreement before the money or the breakup arrives — who owns the songs, how money splits (writing vs performing distinguished), who owns the name, what happens when someone quits, and the decision rules for offers — decided while everyone still shares a van. Use when a band asks 'how should we split money', 'who owns our songs', 'our drummer quit, what happens', or is about to record/release/sign anything. Produces a plain-language band agreement and the meeting script to agree it. Not legal advice — it's the conversation that makes the lawyer cheap later.
npx skills add mohitagw15856/pm-claude-skills --skill band-agreement --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Band Agreement Skill Bands don't break up over creative differences — they break up over the unspoken spreadsheet: the song one person wrote but everyone arranged, the name the founder feels they own, the gig money split evenly while one member books everything, the member who quit in March and wants royalties forever. Every one of those fights is cheap to decide *before* there's money and impossible after. This skill runs the deciding: the questions in the right order, the standard options for each (with what each choice means down the road), and a plain-language agreement the band actually signs — plus the honest line that when real money or a real contract shows up, an hour with a music lawyer turns this document from "our deal" into "our deal, watertight." ## What This Skill Produces - The **band agreement**, one-to-two pages in plain language: songs, splits, the name, spending, decisions, exits — every section a decision, not a description - The **options menu** per hard question (songwriting splits, name ownership, departed-member rights) with the honest tradeoffs of each standard choice - A **band-meeting script**: raising this without it feeling like a prenup ("it IS a pr
- What This Skill Produces
- Required Inputs
- Framework
- Output Format
- Quality Checks
- Anti-Patterns
- Related
What does the band-agreement skill do?
Write the band agreement before the money or the breakup arrives — who owns the songs, how money splits (writing vs performing distinguished), who owns the name, what happens when someone quits, and the decision rules for offers — decided while everyone still shares a van. Use when a band asks 'how should we split money', 'who owns our songs', 'our drummer quit, what happens', or is about to record/release/sign anything. Produces a plain-language band agreement and the meeting script to agree it. Not legal advice — it's the conversation that makes the lawyer cheap later.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill band-agreement --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.