{"id":20725,"plugin_id":"plugins_6aa698dc64588191b48664000f8522de","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:16:27.071Z","digest":"a1f281ca8904c6d1c7da506001e4b1726a78ff77f807269b847477fdfb57a2eb","against":null,"payload":{"description":"Correlate lock, query, and replication signals into causal incident hypotheses with prioritized remediation guidance.","included_files":[],"name":"incident-analysis","skill_md_contents":"---\nname: incident-analysis\ndescription: \"Correlate lock, query, and replication signals into causal incident hypotheses with prioritized remediation guidance.\"\n---\n\n# Incident Analysis\n\n## Use when\n- User asks why an incident happened or wants a causal chain.\n- Response to operational regressions in latency, deadlocks, or replication lag.\n\n## Workflow\n1. Pull recent lock, query, and replication signal snapshots.\n2. Correlate temporal overlap and severity transitions.\n3. Build top incident hypotheses with confidence and remediation order.\n4. Return expected validation probes and rollback readiness.\n\n## Governance\n- Do not trigger any destructive action.\n- Mark confidence clearly before making any operational recommendation.\n\n## Output\n- `timeline`, `incidentHypotheses`, `confidence`, `recommendedActions`\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}