← SAIRYOCONTENT HISTORY
WHAT CHANGED
Update to SAIRYO
Snapshot Oct 24, 2026 · 13:05 UTC · version 2.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save SAIRYO and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Review event attendees, check in or undo check-ins, resend tickets, handle QR codes, issue complimentary tickets and export attendee data. Use for attendee lists, guest operations, entrance management and ticket delivery.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 534
}
],
"name": "sairyo-attendee-operations",
"skill_md_contents": "---\nname: sairyo-attendee-operations\ndescription: Review event attendees, check in or undo check-ins, resend tickets, handle QR codes, issue complimentary tickets and export attendee data. Use for attendee lists, guest operations, entrance management and ticket delivery.\n---\n\n# SAIRYO attendee operations\n\n1. Resolve the exact managed event, check caller permissions, and use `list_event_attendees` (or `get_event_attendees` if appropriate) with necessary search, cursor and filters. Use `render_event_attendees` for interactive operations when supported.\n2. For an individual, disambiguate using permitted ticket or attendee identifiers and call `get_attendee_details`, optionally `render_attendee_details`. Do not expose personal data not required for the task.\n3. For check-in, use `check_in_attendee` with verified ticket ID or opaque QR token, not a guessed identity. Treat duplicate scans idempotently and convey recorded status.\n4. For undo, verify target check-in, gather required reason, confirm intent, then use `undo_attendee_check_in`; inspect resulting state.\n5. For resend, verify the permitted recipient and use `resend_attendee_ticket`. Do not redirect to an arbitrary third-party address.\n6. For complimentary tickets, confirm event, recipient, tier, inventory and that zero-value issuance is intended before calling `issue_complimentary_ticket`.\n7. Use `get_ticket_qr_code` for existing signed QR data; `regenerate_ticket_qr_code` only with explicit confirmation that it revokes a previous token.\n8. For attendee export, use `export_event_attendees_csv` only after checking authorization and intended filters. Treat download links as sensitive and short-lived.\n9. Clearly state whether an operation succeeded, was blocked, or needs a separate host-dashboard action.\n\nNever include ticket QR tokens, private buyer contact data, or exported attendee rows in public summaries.\n"
}SHA-256 of public snapshot: 425440aaaada27561ee7e600f54d3095b925197439996ce9f01e8d466bd819bd