← 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": "Summarize ticket sales, revenue, check-ins, refund patterns and event performance over a date range, compare managed events, and render grounded visuals. Use for KPIs, sales summaries, forecasting-style questions and operational recommendations, not changing event settings.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 548
}
],
"name": "sairyo-event-analytics",
"skill_md_contents": "---\nname: sairyo-event-analytics\ndescription: Summarize ticket sales, revenue, check-ins, refund patterns and event performance over a date range, compare managed events, and render grounded visuals. Use for KPIs, sales summaries, forecasting-style questions and operational recommendations, not changing event settings.\n---\n\n# SAIRYO event analytics and reporting\n\n1. Clarify the date range, timezone, relevant event(s), and whether the user means one event or all accessible managed events. Do not guess missing ranges when materially ambiguous.\n2. For one event, use `get_event_sales_summary`; for multiple events or a period, use `get_sales_metrics_for_date_range`. Use `list_managed_events` to establish eligible scope if needed.\n3. For grounded insights, use `generate_event_insights` and `render_event_insights` when available. Include the underlying source counts, freshness and caveats.\n4. Compare tickets sold, gross revenue, successful refunds, net revenue, tiers and check-ins only when denominators and currencies are comparable. Never sum distinct currencies without a supported FX conversion.\n5. Distinguish ticket attendees from ticketing guests, tickets sold from check-ins, and cashflows from gross bookings; do not estimate unavailable results as observed fact.\n6. For requested datasets, use `export_event_insight_metrics_csv` and explain source range and scope.\n7. For recommendations, ground each suggestion in observed metrics and separate facts from hypotheses. Avoid financial guarantees or fabricated trends.\n8. Deliver concise KPI summary, per-event breakdown if requested, anomalies, and actionable follow-ups. Use available visual tools when they materially help; do not pretend a UI render succeeded if it failed.\n\nNo transaction, ticket, or event modifications occur in this reporting skill.\n\n## SAIRYŌ Event / Content type handling\n\nAn Event might represent a regular or spatial video content experience. Use actual event type and tool metric definitions before interpreting sales as ticket admissions, views, content accesses or entitlements. The MCP inventory does not establish primary-video view or spatial-playback analytics; do not infer those from ticket sales.\n"
}SHA-256 of public snapshot: fe28811a71704eabe0eea8886edc578d4c656cb8865e926c8e25e374b1774c7a