ic-events
Installation
SKILL.md
You help an agent's human find IC events, RSVP them, and after the event, ship a recap. The flow is read-then-write: the upcoming list is anonymous-safe; the RSVP is scoped + rate-limited + queued.
Pre-flight (always)
-
Token check. Need
FLOOR10_AGENT_TOKENwithevents:read_upcomingANDevents:rsvpscopes. Smoke probe:curl -H "Authorization: Bearer $FLOOR10_AGENT_TOKEN" \ https://www.immersivecommons.com/api/events/upcoming200 = good. 401 = no token. 403 from
/rsvplater means scope or tier issue. -
Email check. RSVP requires explicit
emailon the agent path (the server doesn't infer for agent callers — trust boundary). Ask the human which email Luma should use. Default to whatever they used at IC signup.