agentleFS
nickmerichnickmerich/artist-led-events-skills/skills/registration-and-capacity/SKILL.md

registration-and-capacity

Skill0 starsChanged 25 days agoMITView on GitHub

Designs registration for an artist-led athletic event, covering free versus paid entry, numbered tickets, allocation across artist community and club, waitlists, waivers and consent, reminders, check-in, and honest counting from RSVP to attendance to return. Use for "set up registration", "how many spots should we release", "what show rate should we plan for", "build the check-in flow", or "how many people actually came".

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:

    Never: health details beyond what the medical lead needs.

    line 31
  2. Distinctive:

    Run a real test registration end to end: form, confirmation email, waiver stored, appears in check-in list, cancel/release works.

    line 53

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

Registration and Capacity

Step 1: Free, paid, or hybrid

  • Free (partner-funded): widest door; expect lower show rates. Only announce free when partners have committed to cover costs.
  • Paid: higher show rates; price must clear break-even at a conservative sell assumption.
  • Refundable deposit: small fee returned at check-in or donated. Raises show rates without making it a ticket. Check the payment platform's refund costs first.

Step 2: Allocate the spots

Split capacity on purpose so the artist's people and the existing crew both get in. Example split for 100 numbered spots (an illustration, not a rule): 70 artist community, 20 club welcome, 10 discretionary for partners, press, and people who need a hand getting in.

Numbered tickets (001 of 100) mark belonging, not finish order.

Step 3: Plan the show rate

Release registrations above capacity only with a justified show-rate ASSUMPTION. Base it on your own past events if you have them. Free community events commonly see a meaningful share of RSVPs not show; paid events show up at higher rates. If you have no data, release to capacity and run a waitlist instead of guessing.

Step 4: Collect only what you need

Required: name, email, emergency contact, waiver acceptance, level or group choice. Optional, separate checkboxes: photo/video consent, partner offers opt-in, newsletter. Never: health details beyond what the medical lead needs; never share the list with partners.

Step 5: Reminders

  • Confirmation with date, time, exact meeting spot (map link), what to bring, and the weather plan.
  • 3 days before: logistics and parking.
  • Day before: weather status and "can't make it? release your spot" link (feeds the waitlist).
  • Morning of, if weather is borderline: go/no-go message at a time announced in advance.

Step 6: Check-in

  • QR or name lookup, one line per 75 arrivals at peak.
  • Paper waiver backup.
  • Walk-up policy decided in advance (allowed up to capacity, must sign waiver).
  • Live count visible to the event lead.

Step 7: Count honestly

Report separately: registered, checked in, finished (if tracked), first-timers, returned within 30 days. Check-ins are the source of truth for attendance. Missing records are UNKNOWN, not zero.

Test before announcing

Run a real test registration end to end: form, confirmation email, waiver stored, appears in check-in list, cancel/release works. Mark tested records clearly and delete them.

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.