{"id":77023,"plugin_id":"plugins_6ab41ed5b8c4819199eb5bbf91ce25f5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:19.293Z","digest":"a846e2acfe6946deb6d6394855e732023564450766af51505f7997d9251c4dd1","against":null,"payload":{"description":"Diagnose an active or recent production software/data/AI incident from logs, monitoring and deployments with safe mitigation planning.","included_files":[],"name":"triage-incident","skill_md_contents":"---\nname: triage-incident\ndescription: Diagnose an active or recent production software/data/AI incident from logs, monitoring and deployments with safe mitigation planning.\n---\n\n# Triage Incident\n\nUse this skill only for its stated purpose. Follow the shared source-of-truth, permission and evidence rules in `../../references/workflow-contract.md`. Read `../../references/incident-triage.md` for detailed method when necessary.\n\n## Procedure\n1. Establish impact, priority, currently verified symptoms and safe operational constraints.\n2. Inspect relevant health signals, recent changes and traces; do not assume a root cause.\n3. Suggest smallest safe containment/mitigation consistent with user permissions and runbooks.\n4. Form and test hypotheses without destructive action; plan recovery checks.\n5. Produce incident timeline, mitigation status, confirmed root cause or open hypotheses and follow-up tests.\n\n## Handoff rule\nState actual artifacts or grounded code findings and validation status. Never invent file paths, executed tests, tool access, or completed subagent work. Keep output proportionate to the user request.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}