跳到主要内容
知仓学习社ZHICANG

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 o…

不碰外部(只输出文字)无严重或高危命中mohitagw15856/pm-claude-skills

它会碰到什么

扫了多少1 个文本文件,7 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

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 prenup — that's why we're doing it now, while it's

easy"), and the order that keeps the meeting friendly

  • The decision & spending rules: what needs everyone, what the

bookings-person just decides, the band-fund basics

  • Lawyer-trigger flags: the events that upgrade this from document to

legal matter (label interest, publishing deal, real recording budget,

a member with a manager)

Required Inputs

Ask for (if not already provided):

  • The band: members, roles (who writes? who books? who fronts money?),

how long together, what's released already

  • The current reality of songs: who's been writing, how arrangements

happen, anything already registered anywhere

  • Money so far: gig fees, who's owed for gear/van/recording fronted
  • Any storm clouds already visible (the member half-out, the founder

possessive of the name) — the agreement is written toward the real

band, not the ideal one

Framework

  1. Songs first — writing and recording are different rights. The

options, plainly: pure writer-split (whoever wrote it owns it) ·

band-split-everything (all songs equal, all members) · the common

hybrid (writers keep the song; the band's recording of it is

everyone's). Each has a future: pure-writer gets awkward when the

bassist's riff made the song; band-split gets awkward when one person

writes everything. Decide per-band, write it down, and note that

registrations/collection societies formalize it later — flag, not

asserted procedure.

  1. Money: distinguish the streams. Gig money (usually equal, minus

the band fund) · recording income (follows the songs decision) ·

merch (band fund or equal) · the band fund itself: what goes in

(a % of everything), what it pays (van, recording, the fronted gear

debts — logged and repaid first), who can spend to what limit.

  1. The name. The fight nobody expects: options — the band owns it

(majority of current members keep it if someone leaves) · the founder

owns it (stated now, honestly) · nobody continues it without

unanimous consent. Whichever, write the leaving-case explicitly.

  1. Exits, quit vs fired vs the band ends. The departed member's

rights to: past recordings (usually keeps their share — they played

on it), future income from old songs (follows the songs decision),

the name (per #3), gear and the fund (bought-out how?). The 30-second

version everyone can live with beats the perfect version nobody

discusses.

  1. Decisions and offers. What needs everyone (signing anything,

spending over £X, adding/removing members) vs what the doer decides

(the bookings person confirms gigs inside agreed terms). And the

offer rule: no member negotiates for the band alone; offers come to

the group with 48 hours to read.

  1. The lawyer line, stated warmly. This document is the band's real

agreement and worth signing as-is — AND the moment a label, publisher,

real budget, or manager appears, it goes to a music lawyer to be made

formal. Both halves true; the second is a flag this skill always

raises and never fakes.

Output Format

## The [band name] agreement — v1, [date]
[Six sections, each a plain-language decision · signature-ish lines]

## The options you chose from (kept for the record)
[Per hard question: the menu + why this band picked what it picked]

## The meeting script
[The prenup-joke opener · question order · handling the possessive
founder / half-out member kindly]

## When this goes to a lawyer
[The trigger list — label/publishing/budget/manager — verify-local flag
on registrations and societies]

Quality Checks

  • [ ] Writing and recording rights are decided separately and explicitly
  • [ ] The name section answers the leaving-case by name
  • [ ] Fronted money (gear, van, recording) is logged with a repayment

rule

  • [ ] Every section is a decision — zero "the band will discuss"

placeholders

  • [ ] The not-legal-advice line and the lawyer triggers are present;

society/registration mechanics are flagged, not asserted

Anti-Patterns

  • [ ] Do not default everything to equal-split without showing what

equal costs the writers (or writer-split costs the arrangers) —

informed beats harmonious-for-now

  • [ ] Do not write the founder's name-ownership in by assumption —

it's the menu's most contested item; make it explicit either way

  • [ ] Do not let the agreement pretend the half-out member is all-in;

write toward reality

  • [ ] Do not draft legalese — plain language the drummer reads beats

clauses nobody does

  • [ ] Do not skip it because "we're friends" — the document is friendship

insurance, and the meeting script says exactly that

Related

[[release-day-countdown]] for when the songs this protects go out;

[[press-kit-epk]] for the band's outward face; [[roommate-agreement]] —

same move, different shared dream; [[first-client-contract]] energy for

solo artists dealing with venues.

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。

同名技能的其他版本

有 3 个不同仓库或目录里都有叫 band-agreement 的技能。它们内容并不相同,别混用: