Home / milad-ahmd / agent-skills · GitHub

incident-commander SKILL.md skillA

incident-commander from milad-ahmd/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add milad-ahmd/agent-skills/incident-commander@git:20261025.7c7d700

Pins git:20261025.7c7d700 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: milad-ahmd/agent-skills
Path: skills/incident-commander/SKILL.md
Versions recorded: 1
Latest version: git:20261025.7c7d700, committed Oct 25, 2026
Size: 3,092 bytes
Repository stars: 5
License: MIT

Guides a production incident from first alert to blameless postmortem, covering severity triage, an incident channel and roles, structured investigation (recent deploys, logs, metrics, dependencies), hypothesis tracking, safe mitigation and rollback, status-page and stakeholder updates, a timeline, and a postmortem with action items. Use when the user says production is down, there's an outage, errors are spiking, the site is slow, or asks for help writing a postmortem.

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 🚨

Stay calm, write things down, **restore service first**, and find the root cause second.

## 1. Triage (first 5 minutes)

- **What's broken, for whom, since when?** Get the impact in numbers (error rate, affected users or regions, money at risk).
- **Severity**: SEV1 = full outage or data loss/security · SEV2 = major feature down or heavy degradation · SEV3 = minor or partial issue with a workaround.
- Roles (even if one person holds several): **Incident commander** (decides), **Ops/investigator**, **Comms**.
- Start the **timeline** right away (UTC timestamps) in `incidents/<date>-<slug>.md`.

## 2. Investigate (most likely causes first)

1. **What changed?** Recent deploys, config or feature-flag changes, migrations, infrastructure changes, dependency or provider incidents (check status pages).
   `git --no-pager log --since="6 hours ago" --oneline`, plus the deploy history.
2. **Signals**: the error logs (group by message), the metrics (the RED method: rate, errors, duration), saturation (CPU, memory, DB connections, queue depth).
3. **Scope**: all users or some? One region, endpoint, tenant or app version?
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add milad-ahmd/agent-skills/incident-commander@sha256:e1619f89cca191f3

The line at the top of this page pins the label git:20261025.7c7d700, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_cagnk47ugsur4egd.svg)](https://markdownregistry.com/a/art_cagnk47ugsur4egd)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Oct 25, 2026.

version	committed	commit	size	audit
git:20261025.7c7d700 latest	2026-10-25	7c7d700	3,092 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (3092 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

GitHub

milad-ahmd/agent-skills · 5 stars · license MIT · pushed 2026-10-29 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_cagnk47ugsur4egd
GET https://markdownregistry.com/api/v1/resolve?ref=milad-ahmd/agent-skills/incident-commander
GET https://markdownregistry.com/api/v1/blob/e1619f89cca191f343a3ac3974f00f7cb5c16ed06063e467052eac148ac1eb35

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.