recap-and-sponsor-report
Skill0 starsChanged 25 days agoMITView on GitHub
Produces the post-event recap, sponsor reports with verified numbers and delivered assets, artist debrief, lessons log, and the 30-day return follow-up for an artist-led athletic event, then sets up renewal and the next event. Use for "write the recap", "send the sponsor report", "how did the event do", "what did we learn", or "ask partners to come back".
In this repository13 other files it gives its agents.
- artist-deal-termsSkill
- artist-fit-and-conceptSkill
- content-capture-and-rightsSkill
- event-budget-pnlSkill
- event-producerSkill
- launch-campaignSkill
- permits-insurance-and-riskSkill
- press-and-mediaSkill
- registration-and-capacitySkill
- run-of-show-and-staffingSkill
- sponsor-inventory-and-pricingSkill
- sponsor-outreach-and-closeSkill
- sport-format-designSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 29
Use assets/sponsor-report.md.
- Very specific: line 49
Add to assets/lessons-log.md: format, verified headcount, what broke, what you'd change.
≈ “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.
Files
Recap and Sponsor Report
The recap is where trust gets built or lost. Report what happened, not what you hoped.
Step 1: Pull the verified numbers (within 48 hours)
From check-in and registration records:
- Registered, checked in, first-timers, by level or group if tracked
- Partner deliverables completed (product distributed, station hours, assets delivered)
- Incidents (count and type; no personal details)
- Collective total if the format had one
Label anything not from a record. Missing is UNKNOWN.
Step 2: Public recap
Lead with a real moment (with permission), then the shared result, then thank-yous, then the next step (next event, weekly club, waitlist). No invented quotes. Photos from consenting participants only.
Step 3: Sponsor report (within 7 days)
Use assets/sponsor-report.md. One per partner:
- What they paid for, line by line, and what was delivered
- Verified attendance numbers and how they were counted
- Photos of their activation and their product in use
- Content links and usage rights
- What we'd do better
- The renewal ask: one specific next option with a date
Step 4: Artist debrief
What worked for them, what didn't, would they do it again, what they'd change. Settlement statement if there's a split, on the agreed date.
Step 5: Return follow-up (day 1, 7, and 30)
- Day 1: thank-you with photos and the next event or weekly club invite.
- Day 7: one personal note to first-timers from a crew member.
- Day 30: count how many came back to anything. That's the number that tells you if the event built a crew or just a crowd.
Step 6: Lessons log
Add to assets/lessons-log.md: format, verified headcount, what broke, what you'd change. Fold strong lessons back into the relevant skill.
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
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.

