incident-response SKILL.md skillA
incident-response from harness/harness-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add harness/harness-skills/incident-response@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- harness/harness-skills
- Path
skills/observability-governance/incident-response/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 14, 2026
- Size
- 6,935 bytes
- Repository stars
- 122
- License
- Apache-2.0
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Incident Response Correlate incidents with deployments, assess blast radius, and generate postmortem documents using Harness MCP. ## Instructions ### Step 1: Establish Scope Confirm the affected service, environment, and incident details. ``` Call MCP tool: harness_list Parameters: resource_type: "service" org_id: "<organization>" project_id: "<project>" ``` ### Step 2: Identify the Incident Response Task Determine which workflow the user needs: 1. **Deployment-to-Incident Correlation** -- Determine if a recent deployment caused the incident 2. **Blast Radius Assessment** -- Map affected services and downstream impact 3. **Postmortem Generation** -- Create a structured postmortem document ### Step 3: Correlate Deployment to Incident Gather from the user: - Affected service name and environment - Alert or incident name and start time - Observed symptoms (error rate spike, latency, outage) Pull recent deployments: ``` Call MCP tool: harness_list Parameters: resource_type: "execution" org_id: "<organization>" project_id: "<project>" status: "Success" ``` For each recent deployment, check: …
Read the whole file at its exact version.
How to install
mdr add harness/harness-skills/incident-response@sha256:54ea9b44cbafef7aThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kd4pq2larn7ohr24)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 14, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6935 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
harness/harness-skills · 122 stars · license Apache-2.0 · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kd4pq2larn7ohr24 GET https://markdownregistry.com/api/v1/resolve?ref=harness/harness-skills/incident-response GET https://markdownregistry.com/api/v1/blob/54ea9b44cbafef7a34e54678f0ce552ffb4ae14d45d19456a9283c0d017098a1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from harness/harness-skills
Every file in harness/harness-skills