← 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": "Edit an existing SAIRYO event, manage event media and optional settings, and safely change its visibility or publication state. Use for existing-event management, not new-event creation, attendee operations, or sales reports.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 512
    }
  ],
  "name": "manage-sairyo-event",
  "skill_md_contents": "---\nname: manage-sairyo-event\ndescription: Edit an existing SAIRYO event, manage event media and optional settings, and safely change its visibility or publication state. Use for existing-event management, not new-event creation, attendee operations, or sales reports.\n---\n\n# Manage a SAIRYO event\n\nUse live SAIRYO MCP data; do not infer permissions or stored values from user descriptions.\n\n1. Identify the correct event via `list_managed_events` or `search_sairyo_events_and_reports`; disambiguate similar titles before acting.\n2. Read `get_event_detail` and `get_event_management_context` for the current version, capabilities, and settings. Read `get_event_media` when media is involved.\n3. Summarize requested edits and distinguish safe edits from destructive or public-facing actions. Ask only for missing choices.\n4. Apply scoped changes with `update_event`, `set_event_streaming_configuration`, `set_event_visibility`, `set_event_sales_status`, `set_event_refund_policy`, `set_event_checkout_questions`, `replace_event_cohosts`, `replace_event_referrals`, or `replace_event_discount_codes` only as requested. Replacement tools overwrite entire corresponding sets: retrieve current state, explain the intended replacement, and avoid accidental removal.\n5. For poster, gallery, thumbnail or promotional video, use `attach_event_media`, `remove_event_media`, or `get_event_media`. Never assume uploaded media is already attached. Confirm exact target before removal.\n6. Use the current event version/optimistic concurrency token supplied by preceding reads or writes, if the tool requires it. On conflict, refresh and ask before overwriting newer user edits.\n7. Before publishing, run `get_event_publish_readiness`, present `render_event_publish_preview`, and obtain explicit confirmation. Only then call `publish_event` and read back `get_event_detail`.\n8. For cancellation, explain effects and request explicit confirmation before `cancel_event`. Do not delete financial or attendee records by assumption.\n9. Verify changed fields via read-back and report any error, partial completion, or unmet prerequisite.\n\nNever expose private stream keys, passwords, internal provider secrets, or other attendees' data.\n\n## SAIRYŌ Event / Content type handling\n\nAn Event may be scheduled/live or a regular/spatial video content experience. Check its stored type and media before recommending edits. Do not treat `attach_event_media` promotional videos as proof of primary spatial-content upload support. For content-only management settings not exposed by the MCP tool, provide website guidance without claiming the modification occurred.\n"
}

SHA-256 of public snapshot: 54658700b5a4f04cc66806003467d5c97c5336a5d5ad7db496cc007923e5d0c4