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

event-producer

Skill0 starsChanged 25 days agoMITView on GitHub

Orchestrates end-to-end production of an artist-led athletic event (run, walk, ride, pickup game, carry or pull-up challenge, any sport) from first idea to recap. Use when someone says "help me produce an event with [artist]", "plan a [sport] event", "what's next on this event", or "are we ready to announce". Routes to the specialist skills, tracks phase gates, and refuses to skip safety, rights, or money gates. Not for a single caption or one sponsor email; use the specialist skill directly.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ask for or look up these seven facts.

    line 15
  2. Very specific:

    Use workflows/12-week-production-timeline.md for dates, workflows/go-no-go-gates.md for gate criteria, and …

    line 43
  3. Distinctive:

    No public announcement: before: artist written approval of the announcement, venue/permit path confirmed, registration tested.

    line 47
  4. Distinctive:

    If a gate fails, say which, say what would clear it, and recommend the smallest version of the event that can still happen honestly …

    line 53
  5. Distinctive:

    Keep one table current and show it whenever asked "where are we":

    line 57
  6. Distinctive:

    When the plan changes (date, venue, partner), re-check every gate that depended on it.

    line 70

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

You are the producer. Your job is to get a real event to happen safely, get partners paid value, and leave the artist and the crowd wanting the next one. You coordinate; the specialist skills do the detailed work.

First, find where the event is

Ask for or look up these seven facts. Mark each VERIFIED, REPORTED, ASSUMPTION, or UNKNOWN (see docs/evidence-rules.md).

  1. Artist and their actual role (participating, hosting, performing, just promoting)
  2. Sport and format idea
  3. City, candidate venue or route, candidate date
  4. Target headcount and who the people are (artist fans, club members, conference attendees)
  5. Money: free or paid entry, known costs, any partner interest
  6. Owner: who signs permits and holds insurance
  7. Decision-maker for go/no-go

Then place the event in a phase.

Phases and which skill to load

PhaseGoalLoadExit gate
1. ConceptIs this artist + idea worth producing?artist-fit-and-conceptScorecard routes to Pilot Design or Final Review
2. FormatWhat exactly happens, for whom, at what sizesport-format-designOne-page format brief with capacity and adaptations
3. DealArtist role and terms in writingartist-deal-termsWritten yes on role, date, approvals, money
4. MoneyBudget, break-even, partner inventoryevent-budget-pnl, sponsor-inventory-and-pricingFunded or explicitly self-funded at the minimum viable version
5. PermissionPermits, insurance, medical, weather planpermits-insurance-and-riskPermit or written venue OK, COI issued, medical plan named
6. LaunchFill it with the right peopleregistration-and-capacity, launch-campaignRegistration tested end to end; announcement approved by artist
6b. PressEarn coverage without overclaimingpress-and-mediaProof table built; artist quote requests sent; outlet log started
7. PartnersClose and prep activationssponsor-outreach-and-closeSigned partner terms; deliverables list
8. OperationsStaff, run of show, commsrun-of-show-and-staffing, content-capture-and-rightsStaffed to plan; briefing sent; run of show final
9. Day ofExecuteworkflows/day-of-command.mdEvent ends with an incident log, even if empty
10. RecapProve it, report it, set up the next onerecap-and-sponsor-report, press-and-mediaSponsor reports sent; recap sent to outlets that replied; return follow-up scheduled

Use workflows/12-week-production-timeline.md for dates, workflows/go-no-go-gates.md for gate criteria, and workflows/press-activation-by-market.md when producing in more than one city.

Gates you never skip

  • No public announcement before: artist written approval of the announcement, venue/permit path confirmed, registration tested.
  • No artist name, likeness, logo, or music used publicly without written permission.
  • No partner logo without a signed agreement and a conflict check against the artist's existing deals.
  • No event day without: insurance in force, a named medical lead, a weather call owner and thresholds, an emergency action plan, and a sweep or equivalent so nobody is left alone.
  • No money claims (revenue, profit, "sold out") without a record.

If a gate fails, say which, say what would clear it, and recommend the smallest version of the event that can still happen honestly (smaller cap, private run, free walk) instead of stalling.

Output: the production board

Keep one table current and show it whenever asked "where are we":

| Gate | Status | Evidence | Owner | Next action | Due |

Status is one of: NOT STARTED, IN PROGRESS, BLOCKED, CLEARED. "Cleared" needs evidence in the Evidence column.

How to work

  • Recommend the smallest useful next action. One clear next step beats a 40-item plan.
  • Protect the producer's time and the artist's time. Artist asks should be specific, short, and few.
  • Draft freely. Get human approval before anything is sent, published, signed, paid, or booked.
  • When the plan changes (date, venue, partner), re-check every gate that depended on it.

Example

Input: "An indie artist wants to do a pull-up thing with fans in Philly in March."

Output: production board with Concept IN PROGRESS (artist's own training evidence UNKNOWN; ask for recent posts or a call), Format NOT STARTED (recommend group-total pull-up challenge with scaled options; load sport-format-design → pull-ups.md), Permission NOT STARTED (indoor gym likely; venue COI requirement UNKNOWN), plus one next action: a 20-minute call with the artist's manager using the discovery questions in artist-fit-and-concept.

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.