incident-commander SKILL.md skillA
incident-commander from borghei/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add borghei/claude-skills/incident-commander@v1.2.0Pins v1.2.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- borghei/claude-skills
- Path
engineering/incident-commander/SKILL.md- Versions recorded
- 5
- Latest version
- v1.2.0, committed Jun 22, 2026
- First version recorded
- Mar 30, 2026
- Size
- 7,169 bytes
- Repository stars
- 1,019
- License
- a license file GitHub does not identify
Production incident response. Use when handling incidents, classifying severity, reconstructing timelines, writing postmortems, generating comms templates, or building response playbooks with severity scoring and RCA frameworks.
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 Commander Classify incident severity, reconstruct timelines from heterogeneous event sources, and generate structured post-incident reviews with root cause analysis and action items. Codifies PagerDuty, Google SRE, and Atlassian incident-management practices into severity scoring, escalation matrices, communication templates, RCA frameworks, and SLA/error-budget tracking. ## Core Capabilities - **Severity classification** — multi-dimensional scoring (revenue, user scope, data/security risk, service criticality, blast radius) into SEV-1 to SEV-4 with confidence and escalation paths. - **Timeline reconstruction** — chronological timelines from logs, alerts, Slack, and deploy events with phase detection and gap analysis. - **Post-incident review** — PIRs with 5 Whys, Fishbone, Timeline, or Bow Tie RCA plus categorized action items (owner, priority, deadline). - **Postmortem quality** — coverage-gap detection, action-item quality scoring, MTTD/MTTR benchmarking. - **Communication & escalation** — severity-specific internal/executive/customer/status-page templates; technical (L1-L4) and business escalation matrices with time-based triggers. …
Read the whole file at its exact version.
How to install
mdr add borghei/claude-skills/incident-commander@sha256:b67e4976890ffe98The line at the top of this page pins the label v1.2.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_afoyhm5pbyedqxdb)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 30, 2026 and Jun 22, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.0 latest | 2026-06-22 | 65b93aa | 7,169 B | A | view · diff |
| v1.2.0 | 2026-06-17 | 8980a67 | 6,370 B | A | view · diff |
| v1.1.0 | 2026-06-17 | 0c19211 | 9,642 B | A | view · diff |
| v1.1.0 | 2026-04-02 | d83e68b | 9,713 B | A | view · diff |
| v1.0.0 | 2026-03-30 | 6b5a5d8 | 41,515 B | A | view |
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 (7169 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
borghei/claude-skills · 1,019 stars · license a license file GitHub does not identify · pushed 2026-10-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_afoyhm5pbyedqxdb GET https://markdownregistry.com/api/v1/resolve?ref=borghei/claude-skills/incident-commander GET https://markdownregistry.com/api/v1/blob/b67e4976890ffe988cd42d9e9f8d4e9a9b054cf0368c2445193bd5b218e56e5d
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 borghei/claude-skills
Every file in borghei/claude-skills