{"id":100562,"plugin_id":"plugin_asdk_app_6af6336b8b60819192e81fbcfbe45857","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-17T00:14:02.109Z","digest":"c1996cba33800589346c6f66a24b17751ea415a71cc1f54f686be9abcf54cdd6","against":null,"payload":{"description":"Register an attendee for a Swoogo event, update an existing registration, or manage that attendee's session selection. Use for attendee registration requests and registration troubleshooting; not for bulk marketing, payment processing, or aggregate reporting.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":448}],"name":"registration-assistance","skill_md_contents":"---\nname: registration-assistance\ndescription: Register an attendee for a Swoogo event, update an existing registration, or manage that attendee's session selection. Use for attendee registration requests and registration troubleshooting; not for bulk marketing, payment processing, or aggregate reporting.\n---\n\n# Assist with registration\n\nRead [the shared workflow rules](../../references/workflow-rules.md).\n\n1. Resolve the event and attendee. Reuse profile details the user has supplied or authorized. Ask only for missing required non-password answers or ambiguous choices. Never ask for account passwords or other authentication credentials in chat or an embedded form. Never invent attendee details, dietary preferences, consent, or eligibility; use fictional data only for an explicitly requested test.\n2. Call `swoogo_get_registration_form` for field definitions, choices, and validation. This tool also supports external website builders and may return password-field metadata. For chat registration, exclude any password field identified by its type, name, or label, including custom field IDs. Never place password values in `additional_fields`, other MCP arguments, generated defaults, or chat. Keep its submission token private. Resolve registration types and prices using `swoogo_registration-types_get` with `include_pricing: true` when needed. Do not assume every event or type is free.\n3. Call `swoogo_get_registrants` with `event_id` and the exact email before creating. If a matching registration exists, report it or update it as requested. Clarify multiple matches; never create a second registration just to avoid resolving the first.\n4. For a new registration, call `swoogo_create_registrant` with `event_id`, `email`, and supported common fields. Put `reg_type_id`, `job_title`, `phone`, and discovered custom fields in `additional_fields`; map choices to the actual IDs. Set `send_email` true only when the user requested a confirmation email, otherwise false. If the user wants to fill a form themselves and requests a confirmation email, use `swoogo_registration_form` instead of also creating the registration. The current embedded form submits with `send_email: true`; for registration without email, use the programmatic create workflow with `send_email: false`. The hidden submit tool belongs to the UI.\n5. For an existing registration, read it and call `swoogo_registrants_save` with `registrant_id` and only requested changes. This update tool accepts `reg_type_id` and `job_title` at the top level. A cancellation must be explicitly requested; do not substitute it for deletion or a refund.\n6. Resolve requested sessions with `swoogo_get_sessions`. Check event membership, times, availability, and the attendee's current selections. For a normal session addition, first call `swoogo_add_registrant_to_session` with `validate_only: true` and without `waitlist`. On successful validation, commit the requested addition with `validate_only: false`. Do not override capacity unless specifically authorized.\n7. A waitlist is a different outcome from enrollment. Use `waitlist: true` only when requested or after the user chooses it. Never combine waitlist with a validation-only check: the server ignores other options when waitlist is true and writes immediately. For removals/moves, use the update tool's `remove_session_ids`/`add_session_ids` after resolving the requested IDs; inspect partial results and read back selections before retrying.\n\nIf there is a charge or payment requirement, explain it and use a verified Swoogo event/registration link for the user's next step; never collect payment-card details or claim payment succeeded. Report the actual registration ID/status and confirmed session or waitlist outcomes. If a create times out, search by event and email before retrying. A confirmation email request is not proof of delivery.\n\nAn optional password question must not prevent registration: omit it and submit the other supported answers. A password definition, even one marked required for the website, is not by itself proof that the API requires it. If the API rejects a registration because password setup is required, stop that attempt and direct the user to the verified external event registration website. Do not ask for the password, generate one, retry with a placeholder, or add a password input to the in-chat UI.\n\nWhen explicitly building an external registration website, password definitions may describe browser-only inputs. Their values must go directly from the attendee's browser to the returned registration API endpoint (`/api/register`), never through chat or MCP tools. This external workflow does not permit password inputs inside ChatGPT.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}