agentleFS
nickmerichnickmerich/artist-led-events-skills/skills/event-budget-pnl/SKILL.md

event-budget-pnl

Skill0 starsChanged 25 days agoMITView on GitHub

Builds an artist-led athletic event budget, break-even point, contribution target, and profit split using deterministic math from a CSV, not model estimates. Use for "what will this cost", "build the budget", "how many tickets to break even", "can partners fund it free", "what's the profit split", or checking whether a plan's numbers add up. Labels every line as quoted, estimated, or committed.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do the arithmetic in code.

    line 11
  2. Distinctive:

    Always include a contingency line: 10% of costs is a reasonable starting assumption for a first event.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Event Budget and P&L

Do the arithmetic in code. Your job is to get the right lines in the sheet and label how sure each number is.

Step 1: Fill the budget

Copy assets/budget-template.csv. Columns:

  • type: cost or revenue
  • category: see categories below
  • item, qty, unit_amount
  • basis: fixed (once) or per_participant (qty is ignored; multiplied by headcount)
  • status: committed (signed or paid), quoted (written quote), estimate
  • source: link or note

Cost categories that get forgotten: insurance add-ons and additional insured fees, permit fees and deposits, music licensing, restrooms, cleanup and trash, medical staffing, radios, signage, payment processing fees, platform fees, volunteer food and shirts, photographer and editor, contingency.

Always include a contingency line: 10% of costs is a reasonable starting assumption for a first event.

Step 2: Run the numbers

python3 scripts/pnl.py path/to/budget.csv --headcount 100 --split 0.5

The script reports: total costs, total revenue, profit, break-even headcount for paid entry, partner revenue as a share of costs, split amounts, and how much of the budget is only an estimate.

Step 3: Pick the funding shape

ShapeRule of thumb
Free, partner-fundedCommitted partner revenue covers 100% of committed and quoted costs before announcing free entry.
Paid entryPrice so break-even sits at or below a conservative show/sell assumption, not at capacity.
HybridPartners cover fixed costs; entry covers per-person costs.
Self-funded pilotCap the loss in advance and write it down.

A contribution target (for example, 25% margin after costs) is a goal, not a forecast. Label it.

Step 4: Sanity checks before sharing

  • More than 40% of costs still estimate two weeks before announcing? Get quotes.
  • Any revenue line estimate? It isn't money. Show the plan with and without it.
  • Profit split math uses profit after the agreed cost categories in the artist term sheet.
  • Fiscal sponsor or nonprofit fees, if money passes through one, are a cost line.

Output

The filled CSV, the script output, and a three-line summary: what it costs, who's paying, what's still a guess.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.