{"id":42472,"plugin_id":"plugin_asdk_app_69c97dfccdac819182320df39e3d5db4","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:05:12.002Z","digest":"2a316a29ac6f51b6327a1af28b29aaad2f0fcae32b5e365a376d6a99ca58b3d9","against":null,"payload":{"description":"Investigate event changes and operational issues using authorized audit and state.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":496}],"name":"sairyo-audit-support","skill_md_contents":"---\nname: sairyo-audit-support\ndescription: Investigate event changes and operational issues using authorized audit and state.\n---\n\n# Event Audit and Troubleshooting\n\nSAIRYŌ Events may represent scheduled events or video content. Use the authorized MCP tools only where their contracts support the action.\n\nIdentify a specific Event and authorization. Read `get_event_detail`, `get_event_management_context`, and `get_event_audit_log`; correlate with version and timestamps. For purchase issues consult `list_event_transactions`; for attendance `list_event_attendees`; for media `get_event_media` and publish readiness. Differentiate observed records from hypotheses. Do not infer server logs or root cause from an absence in an audit log. Do not mutate state during investigation unless separately asked and confirmed.\n\nWhere an operation is not exposed through MCP, provide an honest website handoff rather than claiming completion.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}