Skip to content
Back to skills

Event Registration

ASecurity

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".

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 26, 2026
development

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 26, 2026

npx -y skills add mihirkavi/open-media --skill event-registration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Event Registration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Event Registration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mihirkavi-event-registration/badge)](https://www.skillsdirectory.com/skills/mihirkavi-event-registration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: event-registration
description: 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".
---

# 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.

Files in this skill

  • README.md141 B
  • SKILL.md1.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.