agentleFS
Sign inStart free
mihirkavimihirkavi/open-media/skills/event-registration/SKILL.md

event-registration

Skill1 starsChanged 10 days agoMITView on GitHub

Handle event registration, RSVP, tickets and cancellations through Open Media Events without ever fabricating a registration. Use when the person says "register me", "RSVP", "get tickets", "I signed up", "I'm on the waitlist" or "cancel my spot".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. simonkoehler/event-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 2 are distinctive, and 6 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.

  • 6

    Very specific

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

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

    No connected provider lets Open Media register an attendee programmatically (automation.register is handoff).

    line 12
  2. Very specific:

    Call get_event_options. State the price, availability, approval requirement and spots left.

    line 16
  3. Distinctive:

    If paid, say the amount and that payment happens on the provider's page.

    line 17
  4. Very specific:

    Call register_event and give them open_this_link with the checklist in before_you_register.

    line 18
  5. Very specific:

    When they report the outcome, call record_registration with what the provider said: registered, waitlisted, pending_approval or failed.

    line 19
  6. Very specific:

    Never say "you're registered" unless record_registration stored it.

    line 25
  7. Very specific:

    After an uncertain outcome (page timed out, unclear confirmation), call get_registration_status and ask them to check their email before …

    line 26
  8. Distinctive:

    Do not bypass CAPTCHAs, sign-ins or payment steps, or use the browser to register for them.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 registration

Tools: get_event_options, register_event, record_registration, get_registration_status, cancel_registration.

Current capability

No connected provider lets Open Media register an attendee programmatically (automation.register is handoff). Registration is always a handoff: the person completes it on the official page.

Steps

  1. Call get_event_options. State the price, availability, approval requirement and spots left.
  2. If paid, say the amount and that payment happens on the provider's page. Open Media never purchases.
  3. Call register_event and give them open_this_link with the checklist in before_you_register.
  4. When they report the outcome, call record_registration with what the provider said: registered, waitlisted, pending_approval or failed. Ask whether to put it on the calendar, and set user_approved_calendar only if they agree.
  5. Describe the result with its label, for example "Registered (as you reported; not verified with the provider)".
  6. To cancel, call cancel_registration for the link. After they confirm they cancelled, call it again with user_completed_cancellation: true.

Rules

  • Never say "you're registered" unless record_registration stored it. Even then, say it was reported by them, not confirmed by the provider.
  • After an uncertain outcome (page timed out, unclear confirmation), call get_registration_status and ask them to check their email before trying again.
  • Do not bypass CAPTCHAs, sign-ins or payment steps, or use the browser to register for 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.

Check your setup, free