{"id":100560,"plugin_id":"plugin_asdk_app_6af6336b8b60819192e81fbcfbe45857","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-17T00:14:02.060Z","digest":"34bc80bcd7bddf1a151df5880cf1291e6c862de49fa66c2c809b8ac7a3a22e11","against":null,"payload":{"description":"Prepare a Swoogo event overview, readiness audit, or registration trend briefing from live event data. Use for event status, agenda gaps, registration counts, or planning summaries; not for applying changes or attendee-level exports.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":421}],"name":"event-briefing","skill_md_contents":"---\nname: event-briefing\ndescription: Prepare a Swoogo event overview, readiness audit, or registration trend briefing from live event data. Use for event status, agenda gaps, registration counts, or planning summaries; not for applying changes or attendee-level exports.\n---\n\n# Prepare an event briefing\n\nRead [the shared workflow rules](../../references/workflow-rules.md).\n\n1. Resolve the event and any requested reporting dates. If no event is specified, use available conversation context or list accessible events so the user can select one.\n2. Call `swoogo_get_event_bundle` with `event_id` for the initial event, sessions, speakers, sponsors, registration types, packages, and questions. The bundle fetches initial pages and may omit records or return component errors. It is a starting snapshot, not proof of completeness. Use the corresponding list tools and their pagination for a complete audit.\n3. For registration totals or trends, call `swoogo_registrations_get` using `event_id` and, when useful, `group_by: day`, `week`, `month`, or `reg_type`. Use `date_from` and `date_to` in `YYYY-MM-DD` format. Do not pass an email for an aggregate briefing. The schema does not support grouping by source.\n4. Map registration type IDs to names from the bundle or `swoogo_registration-types_get`. The aggregate total comes from pagination metadata, but grouped counts cover at most 5000 records. Surface `_warning`; narrow date windows if complete grouped counts are needed. Weekly buckets begin Sunday.\n5. Check only requested readiness areas: event dates/timezone, incomplete session details, speaker assignments, capacity versus registration counts, and form requirements. Use `swoogo_get_sessions` with `expand: registrantCount` for session registrations; those counts differ from attendance. Fetch detail before calling a field absent. Capacity zero means unlimited for sessions.\n6. For form audits, inspect `swoogo_get_registration_form`; report observed required fields, choices, and validation constraints. Do not infer conversion rates or claim a form change would produce a measured lift without supporting data.\n\nDeliver a concise briefing with event identity and dates, key counts and reporting scope, agenda/readiness findings, and prioritized suggested next actions. Identify missing, failed, and partial data separately from zero. Keep this workflow read-only; hand requested edits to the appropriate registration or agenda workflow.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}