Update to EventHex

{
  "name": "eventhex-event-setup",
  "description": "Create and fully set up an event — event, tickets, speakers, sessions, website — in the right order.",
  "included_files": [],
  "skill_md_contents": "---\nname: eventhex-event-setup\ndescription: Create and fully set up an event — event, tickets, speakers, sessions, website — in the right order.\n---\n\n# Event setup\n\nEnd-to-end flow for \"create my event\" requests. You act on ONE franchise.\n\n## Order of operations\n\n1. `create_event(title, startDate, endDate, …)` — returns the new `eventId` and `websiteUrl`. Share that link.\n2. Tickets — one `create_ticket` per tier (see the `ticketing` guide for pricing/early-bird fields).\n3. Agenda — `create_speakers` then `create_sessions` (see the `agenda` guide for breaks, sub-sessions, roles).\n4. Website — `generate_website` → `apply_website` → `publish_website` (see the `website` guide; `improve_website` is for editing an existing live site).\n5. `generate_seo(eventId)` for metadata; `getSetupChecklist(eventId)` to verify nothing is missing.\n\n## Other event operations\n\n- `updateEventDetails(eventId, …)` — change title, dates, venue, description.\n- `clone_event(eventId, …)` — duplicate an existing event as the starting point for a new edition.\n- `delete_event(eventId)` — destructive; only on explicit user request, restate what will be deleted.\n- `getEventInfo(eventId)` — full event record; `get_event_domains(eventId)` — real website URL, slug, domains.\n\n## Notes\n\n- Dates: pass ISO strings; the event's timezone governs how they display.\n- If the user asks for \"an event like last time\", `list_events` → `clone_event` beats rebuilding from scratch.\n"
}