← 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": "Create, configure, visually review, publish, and verify a SAIRYO event through its MCP tools. Use when a user wants to create or copy an event; do not use for attendee-only or reporting-only requests.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 543
}
],
"name": "create-sairyo-event",
"skill_md_contents": "---\nname: create-sairyo-event\ndescription: Create, configure, visually review, publish, and verify a SAIRYO event through its MCP tools. Use when a user wants to create or copy an event; do not use for attendee-only or reporting-only requests.\n---\n\n# Create a SAIRYO event\n\nPreserve the user's choices and keep the event private until publication is explicitly confirmed.\n\n1. Call `get_event_creation_options` before collecting or writing event settings. Never guess category IDs, currencies, or supported configuration values.\n2. If the user asks to reuse a prior event, retrieve that event before gathering inputs.\n3. Gather only missing essentials: category, title, description, start, duration, timezone, location or public stream, admission model, currency when applicable, and poster intent.\n4. Call `create_event`. It creates a private pending draft; a cover URL is optional.\n5. Attach supplied poster, gallery, promotional video, video thumbnail, or tier thumbnails with the file-aware media tools. Do not ask the user to host attached files publicly.\n6. Configure admission with `set_event_admission`, streaming with `set_event_streaming_configuration`, and ticket tiers with the tier tools. After every write, use the returned event version for the next write.\n7. Apply only optional settings requested or confirmed by the user, including donations, co-hosts, referrals, discounts, checkout questions, and refund policy.\n8. Call `get_event_publish_readiness`. Resolve blocking issues; distinguish warnings from blockers.\n9. Call `render_event_publish_preview` so the user can visually review the complete stored configuration.\n10. Obtain explicit confirmation to publish after showing the preview. Do not treat an earlier request to create an event as publish confirmation.\n11. Call `publish_event` with `confirmed: true` only after readiness passes and confirmation is obtained.\n12. Call `get_event_detail`, `get_event_ticket_tiers`, and `get_event_media` after publication. Compare the read-back with the user's requested configuration and report any mismatch.\n\nNever expose RTMP credentials, stream keys, provider secrets, private payment identifiers, or attendee PII without the required permission.\n\n## SAIRYŌ Event / Content type handling\n\nSAIRYŌ calls the main record an Event whether the creator is setting up a scheduled gathering or a video-content experience. Ask which experience they want before requesting time, location, admission and ticket details. Use `get_event_creation_options` to establish supported types and fields. Only configure dates, streams, tiers and admissions if applicable. The promotional-video attachment tool does not, by itself, prove regular or spatial content ingestion/playback support. For a content Event requiring functionality not exposed through these tools, create only a supported draft (with authorization), then hand off remaining upload steps to the website; never publish or claim a spatial asset is processed before confirmation.\n\n## Events also include content (regular and spatial videos)\n\nSAIRYŌ uses Events for both scheduled activities and standalone content/video listings. At discovery ask which type the user is creating. For regular or spatial primary video use the appropriate specialized skill as needed, and never conflate `attach_event_media` promotional media with primary video ingestion.\n"
}SHA-256 of public snapshot: a2f6ef2f7a4667798707d6ef6da8d1fd4ce0980a44ee735197fff7acbda4989a