agentleFS
nickmerichnickmerich/artist-led-events-skills/skills/artist-deal-terms/SKILL.md

artist-deal-terms

Skill0 starsChanged 25 days agoMITView on GitHub

Structures the artist side of an artist-led athletic event, including role, time ask, compensation model, name and likeness approvals, music use, content rights, brand conflicts and exclusivities, cancellation, and safety responsibilities, then drafts a term sheet for lawyer review. Use for "what do we offer the artist", "draft the artist agreement", "how do we split profit", "can we use their name and music", or when an artist's team says yes and you need it in writing.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Keep talent compensation separate from event production funding.

    line 31
  2. Distinctive:

    Unreleased music: if previewed, no recording.

    line 40
  3. Distinctive:

    Before any partner is pitched with the artist's name:

    line 44
  4. Distinctive:

    Ask for the artist's active brand deals and category exclusivities.

    line 45
  5. Distinctive:

    Run every partner against that list.

    line 46

≈ “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

Artist Deal Terms

A clear deal protects the artist's time and name, and protects the producer from building an event around a maybe. Draft the term sheet; a lawyer finalizes the agreement.

Step 1: Pick the ask size

Smaller asks get faster yeses. Offer two shapes:

  • Low-lift: one morning, about 90 minutes on site, one point of contact, no promotion required. Private or small public.
  • Full: on-site role plus a set number of promotional posts and one pre-event content moment.

Step 2: Choose the money model

ModelHow it worksUse when
Profit share after costsAgreed costs come off the top; profit splits by an agreed ratio (50/50 is a clean default).Paid entry or meaningful partner revenue; both sides want upside.
Flat feeFixed appearance or performance fee.Artist needs certainty; event is partner-funded.
Fee + shareSmaller guaranteed fee plus share above break-even.Larger events.
No fee, value exchangeContent, audience growth, cause alignment, product.Small pilots, community events, artist's own idea.

Rules:

  • Split profit after agreed costs, not gross. List the cost categories in the term sheet so nobody argues later.
  • Keep talent compensation separate from event production funding. A partner funding coffee and permits isn't paying the artist, and the term sheet should say which money is which.
  • Settlement date and statement: within an agreed number of days after the event, with a line-item statement.

Step 3: Rights and approvals (the part people skip)

  • Name, likeness, logos, marks: list exactly which uses are approved (event title, poster, social posts, merch). Merch needs its own approval.
  • Approval rights: artist approves the announcement, event title, and any partner associated with their name. Set a response window (for example, 48 hours) and a default if no answer.
  • Music: recorded music played at the event needs public performance licensing, and the event owner is responsible, not the DJ or artist (see permits-insurance-and-risk). Music in published video needs sync rights from the publisher and label. Artist-owned masters and publishing simplify this; confirm who owns what.
  • Content: who can capture, who owns footage, who can post, approval for posts featuring the artist, usage window, and whether partners can reuse it (usually requires extra permission and sometimes payment).
  • Unreleased music: if previewed, no recording; say how that's enforced.

Step 4: Conflicts and exclusivities

Before any partner is pitched with the artist's name:

  • Ask for the artist's active brand deals and category exclusivities.
  • Run every partner against that list. Conflicts beat the original sponsor list; replace the category, don't stall the event.
  • Note sensitive topics or substances. If the artist's brand involves anything not legal or appropriate at a public athletic event, keep the event footprint clean and move any adult or licensed component to a separate, legal, controlled setting after the athletic portion.

Step 5: Safety and conduct

  • Artist participates under the same waiver as everyone, or a separate talent agreement covers it.
  • Talent protection: arrival and exit route, one handler, no guaranteed photo line, a hard stop time.
  • Producer owns safety decisions, including weather calls. The artist doesn't override them.

Step 6: Cancellation

  • Weather or safety cancellation: who pays what, reschedule window.
  • Artist cancellation: replacement artist allowed? Refund policy for paid entry?
  • Producer cancellation: costs already incurred.

Output

Fill assets/term-sheet.md. Mark every term as AGREED (with the message or doc that shows it), PROPOSED, or OPEN. A proposal sent is not agreement.

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.