Asd Ste100
danyuchn/asd-ste100-skill
A skill your agent uses when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and…
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…
Install Band Agreement
$ npx skills add mohitagw15856/pm-claude-skills --skill band-agreement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills band-agreement --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/band-agreement .claude/skills/band-agreement && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "band-agreement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/band-agreement into .claude/skills/band-agreement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "band-agreement", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/band-agreementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill band-agreement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills band-agreement --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/band-agreement .agents/skills/band-agreement && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "band-agreement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/band-agreement into .agents/skills/band-agreement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "band-agreement", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill band-agreement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills band-agreement --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/band-agreement .cursor/skills/band-agreement && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "band-agreement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/band-agreement into .cursor/skills/band-agreement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "band-agreement", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/band-agreement--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill band-agreement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills band-agreement --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/band-agreement .gemini/skills/band-agreement && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "band-agreement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/band-agreement into .gemini/skills/band-agreement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "band-agreement", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills band-agreementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill band-agreement -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/band-agreement .github/skills/band-agreement && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "band-agreement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/band-agreement into .github/skills/band-agreement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "band-agreement", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill band-agreement -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills band-agreement --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/band-agreement .opencode/skills/band-agreement && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "band-agreement" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/band-agreement into .opencode/skills/band-agreement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "band-agreement", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
band-agreement- GitHub stars
- 1.4k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 843 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Works in 6 steps: Songs first — writing and recording are… → Money: distinguish the streams. Gig… → The name. The fight nobody expects:… → …
- A band asks how should we split money
- SKILL.md covers What This Skill Produces, Required Inputs, Framework and Output Format, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Band Agreement is an agent skill from mohitagw15856/pm-claude-skills. 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…
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Plain language and style rules. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- A band asks how should we split money
- Who owns our songs
- Our drummer quit
- Is about to record/release/sign anything
Example prompts
- “how should we split money”
- “who owns our songs”
- “our drummer quit, what happens”
- “/band-agreement”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Songs first — writing and recording are different rights. The
- Money: distinguish the streams. Gig money (usually equal, minus
- The name. The fight nobody expects: options — the band owns it
- Exits, quit vs fired vs the band ends. The departed member's
- Decisions and offers. What needs everyone (signing anything,
- The lawyer line, stated warmly. This document is the band's real
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Band Agreement loads about 1.7k tokens when it runs. Until then it costs about 148 tokens; SKILL.md has 843 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 843 words, ~1,740 tokens.
Download SKILL.mdSave it as
.claude/skills/band-agreement/SKILL.md (or your agent's skills folder).- name
- band-agreement
- description
- 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.
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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Show full SKILL.md (193 more words)Show less
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.
Example Trigger Phrases
- "How should we split money?"
- "Who owns our songs?"
- "Our drummer quit."
- "What happens?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/band-agreement of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Band Agreement next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Band Agreement this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Asd Ste100danyuchn/asd-ste100-skill | 4.3k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Technical Writing Standardcursor/plugins | 11k | 10 repos | ~2.3k | Automated safety check: Pass | None | |
| Ponytail AuditDietrichGebert/ponytail | 160k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Natural Japanese Business Writingcoji/natural-japanese | 1.9k | — | ~2.1k | Automated safety check: Pass | MIT | |
| PgjevrealZachi/pg-jev | 1.1k | — | ~2.9k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
Ponytail Audit
DietrichGebert/ponytail
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split.
Natural Japanese Business Writing
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
Pgjev
realZachi/pg-jev
Install, configure, query and explain pgjev (the jev PostgreSQL extension that filters, ranks and classifies rows with plain-language conditions via TypeSafe's Jev model).
Defensive Writing Editor
lennney/stop-that-shit
Cuts defensive disclaimers, stacked hedging and self-protective narration from proposals and summaries, keeping only limits that affect the reader's decision.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Band Agreement
What does Band Agreement 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…. Band Agreement is an agent skill from mohitagw15856/pm-claude-skills. 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.
When should I use Band Agreement?
Band Agreement fits situations like: A band asks how should we split money; who owns our songs; our drummer quit; is about to record/release/sign anything.
How do I install Band Agreement in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill band-agreement -a claude-code`. Or copy the skill folder (skills/band-agreement in mohitagw15856/pm-claude-skills) into .claude/skills/band-agreement in your project. Claude Code loads it when a task matches its description.
How do I install Band Agreement in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill band-agreement -a codex`. Or copy the skill folder (skills/band-agreement in mohitagw15856/pm-claude-skills) into .agents/skills/band-agreement in your project. Codex loads it when a task matches its description.
Can I use Band Agreement in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill band-agreement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/band-agreement, .gemini/skills/band-agreement, .github/skills/band-agreement and .opencode/skills/band-agreement in your project.
What does Band Agreement need to run?
SKILL.md names no scripts, command-line tools or credentials: Band Agreement is instructions for the agent only.
Does Band Agreement access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Band Agreement safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Band Agreement use?
Band Agreement is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Band Agreement use?
About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Band Agreement?
Skills that share tags, products or a category with Band Agreement: Asd Ste100 (danyuchn/asd-ste100-skill, 4.3k stars), Technical Writing Standard (cursor/plugins, 11k stars), Ponytail Audit (DietrichGebert/ponytail, 160k stars) and Natural Japanese Business Writing (coji/natural-japanese, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Band Agreement?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.