← 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": "Create, adjust, pause, resume, or inspect event ticket tiers, discounts, donations and sales settings. Use when a host asks about ticket availability, tier prices or quantities, promo codes, sales windows, checkout rules or ticketing configuration.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 522
    }
  ],
  "name": "manage-sairyo-ticketing",
  "skill_md_contents": "---\nname: manage-sairyo-ticketing\ndescription: Create, adjust, pause, resume, or inspect event ticket tiers, discounts, donations and sales settings. Use when a host asks about ticket availability, tier prices or quantities, promo codes, sales windows, checkout rules or ticketing configuration.\n---\n\n# Manage SAIRYO ticketing\n\n1. Locate the managed event; verify role and current version using `get_event_management_context`, `get_event_ticket_tiers`, and `get_ticket_tier_sales_status`.\n2. If changing admission model or currency, check `get_event_creation_options` and existing sold ticket restrictions before `set_event_admission`. Do not invent supported IDs or currencies.\n3. For a single tier, prefer `create_ticket_tier`, `update_ticket_tier`, `archive_ticket_tier`, `duplicate_ticket_tier`, `pause_ticket_tier_sales`, `resume_ticket_tier_sales`, or `reorder_ticket_tiers` as appropriate.\n4. `replace_event_ticket_tiers` replaces the complete active tier set. Use only when a full replacement is explicitly intended after showing its effects. Preserve sold-ticket history.\n5. Use `replace_event_discount_codes` only after reviewing the complete current set; manage donations via `set_event_ticket_donation_settings` and ticket sales via `set_event_sales_status`.\n6. Confirm monetary amounts, currency, capacities, sale windows, visibility and discount impacts before write actions. Do not promise a ticket is purchasable until `get_ticket_tier_sales_status` confirms it.\n7. Respect returned event versions between writes, refresh on conflict, and verify result with `get_event_ticket_tiers` and `get_ticket_tier_sales_status`.\n8. Report user-facing totals and any caveats (paused, unpublished, sold out, outside sale window).\n\nChatGPT does not process ticket purchases, payment cards, refunds, or checkout. Direct buyers to SAIRYO.live when a purchase is requested.\n"
}

SHA-256 of public snapshot: 1f843556507a51a8c8f0fa915b927460599cac187fa86f2f2be0463d192bc9eb