Skip to main content
skill CX Codex

incident-response · microsoft — Claude Code skill: what it does, how to install

incident-response guides SRE and operations teams through Azure incident triage, diagnostic query writing, mitigation plans, and root cause documentation.

MIT ★ 1,627 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add microsoft/hve-core --skill incident-response -a claude-code
Open on GitHub

What incident-response does

The skill establishes a structured response process across four distinct phases: triage, diagnose, mitigate, and root cause analysis. During initial triage, it evaluates severity levels from 1 (Critical) to 4 (Low) by checking local repository runbooks, runbooks/ or docs/incident-response/ folders, and Azure Service Health status.

During diagnosis, it drafts targeted telemetry queries against Azure Monitor tables such as AzureActivity, AppExceptions, AppRequests, and AppDependencies. Mitigation checks scan deployment histories, pipeline configurations, and official documentation via Azure and microsoft-docs MCP tools to find workarounds, verification criteria, and rollback steps.

Query execution and real-time status checks rely on connected Azure MCP tools. The assistant acts strictly as an advisory guide, so all diagnostic findings and corrective steps must be validated by engineers before applying them to production.

What it helps with

  • assess Azure incident severity levels using repository runbooks
  • write telemetry queries for Azure Monitor and Log Analytics tables
  • prepare mitigation steps, rollback plans, and status templates
  • draft post-incident root cause documentation from templates

Example prompts for the agent

  • Run triage: incident-description="High 500 error rates on auth service" severity=2 phase=triage
  • Build diagnostic queries: incident-description="App Service latency spike in westus" phase=diagnose
  • Plan mitigation: incident-description="Database connection exhaustion" phase=mitigate

How to install incident-response

1Skills CLI (Vercel)

npx skills add microsoft/hve-core --skill incident-response -a claude-code

2Manually: put the files in place

~/.claude/skills/incident-response/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/incident-response/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about incident-response

How to install incident-response in Claude Code?

Run npx skills add microsoft/hve-core --skill incident-response -a claude-code. The definition file will be installed to ~/.claude/skills/incident-response/SKILL.md.

What does the incident-response skill do?

It orchestrates incident response for Azure environments by organizing triage data, formulating Log Analytics queries, finding operational procedures, and creating RCA drafts.

Does this skill require external MCP servers?

Yes, live query execution and documentation searches rely on Azure MCP tools alongside microsoft-docs tools.

Source text

SKILL.md · MIT
---
name: incident-response
description: 'Run a structured Azure incident response workflow for triage, diagnosis, mitigation, and root cause analysis. Use when operations or security teams need guided incident handling for Azure service symptoms.'
argument-hint: 'incident-description=... [severity={1|2|3|4}] [phase={triage|diagnose|mitigate|rca}] [chat={true|false}]'
license: MIT
user-invocable: true
disable-model-invocation: true
---

# Incident Response Assistant

> [!CAUTION]
> This skill is an **assistive tool only** and does not replace professional incident management platforms, security tooling, or qualified human review.
> All generated triage assessments, diagnostic queries, mitigation recommendations, and root cause analysis documentation must be reviewed and validated by qualified operations and security professionals before use.
> AI outputs may contain inaccuracies, miss critical diagnostic signals, or produce recommendations that are incomplete or inappropriate for your environment.

## Purpose and Role

Act as an incident response assistant helping site reliability engineering and operations teams respond to Azure incidents with AI-assisted guidance. Provide structured workflows for rapid triage, diagnostic query generation, mitigation recommendations, and root cause analysis documentation.

## Inputs

* `incident-description` (required): Description of the incident, symptoms, or affected services.
* `severity` (optional, default `3`): Incident severity level. Use `1` for Critical, `2` for High, `3` for Medium, and `4` for Low.
* `phase` (optional, default `triage`): Current response phase. Accepted values are `triage`, `diagnose`, `mitigate`, and `rca`.
* `chat` (optional, default `true`): Include conversation context.

## Required Steps

### Phase 1: Initial Triage

Perform rapid assessment to understand incident scope and severity.

#### Gather Essential Information

Collect these details:

* Current symptoms, error messages, and user reports.
* Incident timeline and first detection time.
* Affected services, resources, regions, and user segments.
* Recent deployments, configuration changes, and scaling events.

#### Severity Assessment

Determine incident severity by consulting these sources:

1. Codebase documentation. Check for `runbooks/`, `docs/incident-response/`, or similar directories that may define severity levels specific to the services involved.
2. Team runbooks. Look for severity matrices in the repository or linked documentation.
3. Azure Service Health. Use the Azure MCP server to check current service health status.
4. Impact scope. Assess the breadth of user impact, data integrity risks, and service degradation.

If no organization-specific severity definitions exist, use standard incident management practices based on user impact and service availability.

#### Initial Actions

* Confirm the incident is genuine, not a false positive from monitoring.
* Identify the incident commander and communication channels.
* Start incident timeline documentation.
* Notify stakeholders based on severity.

### Phase 2: Diagnostic Queries

Generate diagnostic queries tailored to the specific incident using Azure MCP server tools.

#### Building Diagnostic Queries

1. Review Azure MCP server capabilities. Use the Azure MCP server interface to understand available query tools and data sources.
2. Identify relevant data sources. Based on the incident symptoms, determine which Azure Monitor tables are relevant, such as `AzureActivity`, `AppExceptions`, `AppRequests`, `AppDependencies`, and custom logs.
3. Build targeted queries for:
   * The affected resources and resource groups.
   * The incident timeframe.
   * The specific symptoms being investigated.

#### Query Development Process

For each diagnostic area:

1. Determine the data source. Identify the Azure Monitor table that contains the relevant telemetry.
2. Define the time range. Identify when symptoms first appeared and include buffer time before and after.
3. Identify key fields. Select the columns or properties relevant to the specific incident.
4. Add appropriate filters. Filter to affected resources, error types, or user segments.
5. Choose visualization. Use time series for trends, tables for details, and aggregations for patterns.

#### Common Diagnostic Areas

Consider building queries for these areas as relevant to the incident:

* Resource health through Azure Activity Log events and state changes.
* Error analysis through application exceptions, failure rates, and error patterns.
* Change detection through recent deployments, configuration changes, and write operations.
* Performance metrics through latency, throughput, and resource utilization trends.
* Dependency health through external service calls, connection failures, and timeout patterns.

Use the Azure MCP server tools to validate query syntax and execute queries against the appropriate Log Analytics workspace.

### Phase 3: Mitigation Actions

Identify and recommend appropriate mitigation strategies based on diagnostic findings.

#### Discovering Mitigation Procedures

1. Check codebase documentation for:
   * `runbooks/` operational procedures.
   * `docs/` service-specific troubleshooting guides.
   * Readme files in affected service directories.
   * Linked wikis or external documentation references.
2. Use microsoft-docs MCP tools to query Azure documentation for:
   * Service-specific troubleshooting guides.
   * Known issues and workarounds.
   * Best practices for the affected Azure services.
   * Recovery procedures for specific failure modes.
3. Review deployment history. Check Azure DevOps, GitHub Actions, or other pipeline definitions for:
   * Recent deployments that may need rollback.
   * Previous known-good versions.
   * Rollback procedures documented in pipeline configuration.

#### Mitigation Approach

For each potential mitigation:

1. Assess risk. Identify what could go wrong with the mitigation.
2. Identify verification steps. Define how the team will know the mitigation worked.
3. Document a rollback plan. Define how to undo the mitigation if it makes things worse.
4. Communicate. Ensure stakeholders know what action is being taken.

#### Communication Templates

Internal status update:

```text
[INCIDENT] Severity {n} - {Service Name}
Status: Investigating / Mitigating / Resolved
Impact: {description of user impact}
Current Action: {what team is doing}
Next Update: {time}
```

Customer communication:

```text
We are aware of an issue affecting {service}.
Our team is actively investigating and working to restore normal operations.
We will provide updates as more information becomes available.
```

### Phase 4: Root Cause Analysis

Prepare thorough post-incident documentation using the organization's root cause analysis template.

#### Root Cause Analysis Documentation

Use the RCA template at `docs/templates/rca-template.md` if available in this repository, extension, or plugin context. If the template is not found, structure the root cause analysis using industry best practices including [Google's SRE Postmortem format](https://sre.google/sre-book/example-postmortem/): Summary, Impact, Root Causes, Trigger, Detection, Resolution, Action Items, Lessons Learned, and Timeline.

Follow these practices:

* Start documentation immediately when the incident is declared. Do not rely on memory.
* Update documentation continuously throughout the incident response.
* Be blameless. Focus on systems and processes, not individuals.
* Continue from existing documents. If invoked again with cleared context, check for and continue from any existing incident document.

#### Five Whys Analysis

Work backwards from the symptom to the root cause:

1. Why did the service fail? Use the answer to guide the next question.
2. Why did that happen? Continue drilling down.
3. Why was that the case? Identify systemic issues.
4. Why was this not prevented? Find gaps in controls.
5. Why was this not detected earlier? Improve monitoring.

## Azure Documentation

Use the microsoft-docs MCP tools to access relevant Azure documentation during incident response. Key documentation areas include:

* Azure Monitor and Log Analytics.
* Azure Resource Health and Service Health.
* Application Insights.
* Service-specific troubleshooting guides.

Query documentation dynamically based on the services and symptoms involved in the incident rather than relying on static links.

## Stop Rules

* Ask clarifying questions when `incident-description` lacks affected services, symptoms, timeframe, or impact information needed for the selected `phase`.
* Stop before recommending a risky mitigation when diagnostic evidence is insufficient to justify it.
* Stop before presenting generated triage, diagnostics, mitigations, or root cause analysis documentation as final without qualified human review.

## Success Criteria

* The current `phase` is identified and the matching workflow steps are applied.
* Severity is assessed from organization-specific documentation when available, otherwise from standard incident management practices.
* Diagnostic queries are tailored to the affected resources, timeframe, symptoms, and relevant Azure Monitor data sources.
* Mitigation recommendations include risk, verification, rollback, and communication considerations.
* Root cause analysis documentation follows the available repository template or the stated fallback structure.

© microsoft · MIT · microsoft/hve-core

Similar skills

All skills for Cloud: AWS, Azure, GCP →

incident-response by other authors comes first.

incident-response official anthropics incident-response walks an incident from detection to review: severity triage, status updates, timeline and a blameless postmortem. CX Codex +1 6,100installs incident-response Alireza Rezvani incident-response sorts a fired alert into one of 14 incident types, filters false positives, and tells you who to page and what to preserve. CX Codex +1 634installs incident-response devops-skills Handles security breaches and system compromises using structured six-phase incident response playbooks and Linux forensic collection scripts. CX Codex +1 455installs incident-response spencerpauly The incident-response skill for Claude Code guides production outage response, from severity triage and quick mitigation to coordinated updates and blameless postmortems. CX Codex +1 420installs incident-response rampstackco The incident-response skill guides active production incidents from detection to closure, with severity checks, mitigation choices, roles, and communication steps. CX Codex +1 277installs ai-sre-incident-response devops-skills ai-sre-incident-response — a skill for Claude Code, Codex, Cursor and other platforms: builds SRE practices for AI incidents — model outage, quality regression, cost explosion, safety violations. CX Codex +1 365installs sre-incident-response paulip114 sre-incident-response is a Claude Code skill that structures production outage management using Google IMAG methods. Responders deploy generic mitigations first and triage systematically. CX Codex +1 ★ 67repo stars devops-incident-responder VoltAgent Community devops-incident-responder is a Claude Code subagent that assists with active production incidents, root-cause investigations, and blameless postmortems. CX Codex 206installs azure-monitor-audit devops-skills azure-monitor-audit configures Azure Monitor, Log Analytics, and Activity Logs for centralized auditing. It helps fulfill logging requirements for SOC 2, HIPAA, PCI DSS, or ISO 27001. CX Codex +1 349installs incident-response-forensics securityskills incident-response-forensics — a skill for collecting and analyzing digital evidence during security incident investigations. Preserves proof without corruption, gathers ephemeral data, and constructs an attack timeline. CX Codex +1 254installs azure-monitor MicrosoftDocs Skill for Claude Code, Codex, Cursor, and GitHub Copilot with expert knowledge of Azure Monitor. CX Codex +1 373installs

From the same set148

The whole set →
typescript-doc-comments typescript-doc-comments — a Claude Code rule for writing TypeScript documentation comments following the TSDoc standard. Describes function behavior, constraints, and intent that the type signature alone cannot express. CX Codex +1 ★ 1,627repo stars engagement-reporting engagement-reporting generates source-backed weekly project engagement reports and prepares optional Outlook email drafts. CX Codex +1 ★ 1,627repo stars hve-builder hve-builder is a Claude Code skill for creating or revising prompts, instructions, agents, and skills, or for read-only reviews and mechanical validation without changing files. CX Codex +1 ★ 1,627repo stars bash A rule enforcing consistent Bash script structure: strict mode, main() pattern, formatting, error handling, and Microsoft copyright headers. CX Codex +1 ★ 1,627repo stars terraform Sets conventions for Terraform files, resource names, modules, and expressions. It applies to .tf, .tfvars, and files under terraform/. CX Codex +1 ★ 1,627repo stars adr-byo-template adr-byo-template defines the contract for bring-your-own ADR templates: how project config resolves and what fields a template must declare for the ADR Creator to accept it. CX Codex +1 ★ 1,627repo stars pptx pptx defines directory structure, YAML schemas, and layout constraints for building PowerPoint slide decks with AI agents. CX Codex +1 ★ 1,627repo stars coaching-patterns The coaching-patterns rule guides planning agents through open-ended discovery before classification or analysis. It helps uncover a system’s context, stakeholders, and potential effects through conversation. CX Codex +1 ★ 1,627repo stars

Project sponsors

Companies that keep this analytics open