agentleFS
nickmerichnickmerich/artist-led-events-skills/skills/sponsor-inventory-and-pricing/SKILL.md

sponsor-inventory-and-pricing

Skill0 starsChanged 25 days agoMITView on GitHub

Packages brand partner inventory for an artist-led athletic event (title, presenting, activation, product, content, access, and series deals), prices it from costs and delivered value instead of follower counts, and checks category conflicts with the artist. Use for "what can we sell sponsors", "build sponsor tiers", "price this partnership", "what should we ask [brand] for", or turning an event plan into a partner menu.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a conflict appears, swap the category, don't stall.

    line 50
  2. Very specific:

    Use assets/inventory-menu.md.

    line 54

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

Sponsor Inventory and Pricing

Partners don't buy "exposure." They buy a specific useful thing at a specific moment for specific people. Sell that.

Step 1: List the real inventory

Go through the format brief and run of show. Every moment where a partner could be useful is inventory.

Inventory typeExamplesUseful version
Title"[Brand] presents [Artist]'s [Event]"One per event. Needs artist approval.
ActivationCoffee table, hydration station, recovery tent, shakeout warm-upThey solve a real need at the event.
ProductProduct in hand, sampling, gear for leadersSomething people use that day.
AccessFunds free entry for N people ("100 free spots, covered by [Brand]")Strongest story: the partner opened the door.
ContentNamed segment in the recap video, behind-the-scenes seriesDelivered assets with clear usage rights.
Data and follow-upOpt-in offer to participants who check a boxOnly with explicit, separate consent. Never hand over the list.
SeriesSame partner across a season or multiple citiesDiscounted per event, longer commitment.
CommunityPresenting partner of the recurring weekly run or clubBuilds year-round value beyond one day.

Cut anything that makes the experience worse: forced booths in the start corral, mandatory stops, logos on everything.

Step 2: Price it

Price from two floors and one ceiling:

  1. Cost floor: what the inventory costs you to deliver (staff time, product handling, space, content editing) plus your margin.
  2. Funding floor: the share of the budget this partner needs to cover. If the event is free, partners together need to cover the full budget (see event-budget-pnl).
  3. Value ceiling: what the delivered outcome is worth to the brand: verified people reached in person, sampled product, content assets with usage rights, local relevance. Use verified or conservatively assumed numbers only.

Price inside that range. Round to clean numbers. Write a tier menu with 3 to 5 options and one custom option.

Never price from follower counts. In-person participants, product in hand, and usable content are the value.

Step 3: Conflict check (required)

For every prospect:

  • Against the artist's existing deals and exclusivities (from artist-deal-terms).
  • Against other partners in the same event (one per category unless agreed).
  • Against venue rules (some venues have pouring rights or ban sampling; trails may ban sales and giveaways).
  • Against the audience: no alcohol or age-restricted products in all-ages or athletic portions; nothing that undercuts the safety message.

If a conflict appears, swap the category, don't stall.

Step 4: Write the menu

Use assets/inventory-menu.md. Each item states: what the partner gets, what they provide (cash, product, both), the exact deliverables, approvals required, and any limits.

Fiscal sponsorship note

If an event runs through a nonprofit or fiscal sponsor, some contributions may be tax-deductible for the partner. Only say so when the fiscal sponsor relationship is approved and the specific contribution qualifies. Keep commercial benefits (logos, sampling, ads) and charitable gifts separate; ask the fiscal sponsor how they want it structured.

Output

A filled inventory menu, the price logic for each line, and the conflict check results.

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.