Update to EventMatch

{
  "description": "Read authorized EventMatch Events, event People profiles and saved prospecting plans. Does not start Event Mode, research, processing or outreach.",
  "included_files": [],
  "name": "event-workspace",
  "skill_md_contents": "---\nname: event-workspace\ndescription: Read authorized EventMatch Events, event People profiles and saved prospecting plans. Does not start Event Mode, research, processing or outreach.\n---\n\n# EventMatch public workspace\n\nUse only the connected public EventMatch MCP tools available in the current host.\nFor \"now\" or \"soon\", resolve `get_current_event_context` first; overlapping events\nrequire a selection. Otherwise open `render_event_workspace` to search Events.\nSelect an exact event ID before reading People or a plan.\n\n- `get_event_overview`: stored original description, existing AI brief and linked\n  organizers. Host names without a Person link remain text, not inferred identity.\n- `list_event_people`: stable Person IDs at this authorized event; reset cursor\n  when the search changes. Each page is at most 20.\n- `get_event_person_profile`: canonical professional profile, saved sources,\n  labeled hypotheses, unknowns and optional existing assessment. A missing score\n  does not mean that the Person is unavailable.\n- `get_event_workspace_plan`: existing meeting order and questions. Use its\n  analysis ID when opening a linked Person so the context remains consistent.\n\nIf these 1.1 tools are not yet available, use the existing 1.0 read-only tools;\ndo not claim that the new UI is installed or approved. If the UI bridge is absent,\nsummarize the tool result in text. Never claim stored research is a live lookup.\n\nReading never queues generation or synchronization. Missing data stays missing.\nDrafts are unsent and require user review. The public app has no access to My picks,\npersonal Prepare/follow-up notes, encounters, camera, QR, media, Omi transcripts,\nbiometrics, contacts hidden by the provider, identity review or browser controls.\nDo not invoke personal/admin tools to satisfy a public request. Sending messages,\nregistration and processing are unavailable even if the user asks for them.\n"
}