{"id":21345,"plugin_id":"plugins_6aac006819508191a02506fb32a88714","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:16:53.384Z","digest":"2f2705afc099f5c7472275ad67ad949c960f32eb8e77b0ed44d0bcf43b3a9b27","against":null,"payload":{"name":"service-health-sentinel","description":"Detect service health pressure from incident, SLA, outage, ticket, recovery, billing and operations signals. Use when the user needs service health sentinel for CIO decision support.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":139}],"skill_md_contents":"---\nname: service-health-sentinel\ndescription: Detect service health pressure from incident, SLA, outage, ticket, recovery, billing and operations signals. Use when the user needs service health sentinel for CIO decision support.\n---\n\n# Service Health Sentinel\n\n## Mission\n\nTranslate operational service signals into executive health posture.\n\n## Inputs\n\nAccept incident notes, SLA data, support queues, outage risks, service reports, customer-impact notes and operations updates.\n\n## Workflow\n\n1. Identify service health signals.\n2. Classify health as Green, Amber or Red.\n3. Map dimensions: availability, performance, customer impact, recovery and support load.\n4. Recommend next health check.\n5. Identify escalation needs.\n\n## Output Format\n\n- Executive Summary\n- Service Health\n- Service Signals\n- Health Dimensions\n- Next Health Check\n- Escalation Needs\n- Evidence & Assumptions\n\n## Guardrails\n\nDo not claim live monitoring. Use provided context only.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}