← SAIRYOCONTENT HISTORY

Update to SAIRYO

Snapshot Oct 24, 2026 · 13:05 UTC · version 2.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

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 JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Help a user search discoverable SAIRYO events, locate events they manage, retrieve event or report references, or choose the correct record for another workflow. Use for lookup and navigation rather than event edits or payment.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 546
    }
  ],
  "name": "find-sairyo-events-reports",
  "skill_md_contents": "---\nname: find-sairyo-events-reports\ndescription: Help a user search discoverable SAIRYO events, locate events they manage, retrieve event or report references, or choose the correct record for another workflow. Use for lookup and navigation rather than event edits or payment.\n---\n\n# Find SAIRYO events and reports\n\n1. Identify whether the user is asking for managed/owned events, publicly discoverable events, or authorized report references. Do not assume visibility or access.\n2. For keyword search, use `search_sairyo_events_and_reports`; for managed events use `list_managed_events` with user-requested filters.\n3. Where a reference ID is returned, use `get_sairyo_event_or_report_reference` for the supported summary. Use `get_event_detail` for a manageable event when its ID is known and permitted.\n4. When multiple matching events exist, show name, date and other returned distinguishing attributes; request selection instead of guessing.\n5. Provide only tool-returned event URLs and report references; do not construct or invent links or financial values.\n6. State when a result is private, not authorized, missing, or outside the search scope; do not treat a missing result as proof that an event was deleted.\n7. Route subsequent requests to the appropriate event management, ticketing, attendee, transaction, or reporting workflow without performing an unexpected write.\n\nPurchasing tickets requires SAIRYO.live checkout; do not accept card data in chat.\n\n## SAIRYŌ Event / Content type handling\n\nSearch results for an Event may represent a live/scheduled activity or regular/spatial video content. Do not silently discard content Events from searches. Clarify whether the user wants all Events, scheduled Events only, regular videos, spatial videos, or both; only filter when the MCP query supports it and otherwise explain the limitation.\n"
}

SHA-256 of public snapshot: 7e3fc27228fe1a0afaf8ed59bc6df645218fbaf33a234759956589da6b82ae22