Update to EventHex

{
  "name": "eventhex-attendees-analytics",
  "description": "Attendees, registrations, check-ins, revenue, exhibitor leads, exports and franchise-wide analytics.",
  "included_files": [],
  "skill_md_contents": "---\nname: eventhex-attendees-analytics\ndescription: Attendees, registrations, check-ins, revenue, exhibitor leads, exports and franchise-wide analytics.\n---\n\n# Attendees & analytics\n\n## Per-event numbers\n\n`get_event_stats(eventId, include:[…])` — registration totals, plus inline extras (no file download):\n\n- `trend` — day-by-day registrations + cumulative\n- `revenue` — collected / pending / refunded + net\n- `tickets` — per-ticket registration & paid counts\n\n`getCheckInStats(eventId)` for on-site check-in figures; `audienceInsights(eventId)` for audience breakdowns.\n\n## Franchise-wide\n\n`get_franchise_summary` — event count + total registrations. NOTE: counts ALL participant types (attendees + speakers + exhibitors + sponsors); for attendees-only use `get_event_stats`. `get_franchise_profile` / `list_invoices` for account/billing.\n\n## Individual attendees\n\n- `searchAttendees(eventId, query)` → matches; `getAttendeeDetails(eventId, …)` for one record.\n- `update_attendee(eventId, …)` to fix a registration.\n- `listOrders(eventId)` for payments; `listExhibitors` / `getExhibitorLeads` for exhibitor data.\n- `exportAttendees(eventId)` — PII export; requires the `registrations:export` scope; only on explicit user request.\n\n## Free-form questions\n\n- `queryDatabase(eventId, …)` — analytics queries the dedicated tools don't cover (always event-scoped automatically).\n- `semanticSearch(eventId, query)` — natural-language search across event content.\n\n## Reply rules\n\n- Say which event and which measure each number is (\"paid attendees for WebCastle Meet\", not \"165\").\n- Don't paste bulk PII into chat — summarize, and use exports for full lists.\n"
}