incident-response
100 / 100 · Low risk
Fine to try.
Incident response and analysis via Harness MCP. Correlate incidents with recent deployments, assess blast radius and downstream service impact, and generate comprehensive postmortem documents. Use when asked to investigate an incident, determine if a deployment caused an issue, assess blast radius, or create a postmortem. Do NOT use for pipeline debugging (use debug-pipeline instead) or SLO management (use manage-slos instead). Trigger phrases: incident, deployment correlation, blast radius, po…
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'incident-response' ] || [ -L ~/.agents/skills/'incident-response' ]; then echo 'A skill folder named incident-response already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/harness/harness-skills' "$d" && git -C "$d" checkout --quiet '9c274a3c1cebc5cf26e5501c118e1ff03b63502f' -- 'skills/observability-governance/incident-response' && mkdir -p ~/.agents/skills && cp -R "$d"/'skills/observability-governance/incident-response' ~/.agents/skills/'incident-response' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'incident-response' ~/.claude/skills/'incident-response' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/harness/harness-skills/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-13 | 9c274a3 | 100 |
| 2026-11-07 | e01dc72 | 100 |