Home / sigistry / marketplace · GitHub

incident-response SKILL.md skillA

incident-response from sigistry/marketplace is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add sigistry/marketplace/incident-response@git:20260826.571bc2f

Pins git:20260826.571bc2f in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: sigistry/marketplace
Path: plugins/ci-incident-medic/skills/incident-response/SKILL.md
Versions recorded: 3
Latest version: git:20260826.571bc2f, committed Aug 26, 2026
First version recorded: Jul 8, 2026
Size: 3,089 bytes
Repository stars: 3
License: MIT

This skill should be used when the user mentions "postmortem", "incident", "root cause analysis", "blameless", "severity", "SEV1", "on-call", "RCA", or "outage", or is writing up an incident. It provides a blameless postmortem methodology, a severity model, and reliability metric definitions.

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 and Blameless Postmortems

## Purpose
A consistent, blameless methodology for writing incident postmortems and classifying severity, so writeups drive systemic fixes instead of finger-pointing. This is incident-management domain knowledge (structure, blameless framing, severity, metrics), applied uniformly every time.

## The blameless principle
Analyze **systems and processes, never individuals**. People act rationally given the information and tools they had; if a human error caused harm, the real finding is the missing guardrail that let it. This is not about avoiding accountability, it's that blame suppresses the honest disclosure you need to actually fix the system.

**Reframe every human-error statement:**
| Blameful (reject) | Blameless (use) |
|-------------------|-----------------|
| "X pushed a bad config" | "the change reached prod because no test covered this path" |
| "on-call was slow" | "the alert didn't page; ack took N minutes" |
| "someone ran the wrong command" | "the safe and destructive commands were indistinguishable" |

## Postmortem structure (standard sections)
1. **Summary**: 2-3 sentences: what broke, blast radius, duration.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add sigistry/marketplace/incident-response@sha256:7a59311b7edf4211

The line at the top of this page pins the label git:20260826.571bc2f, 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_svgafvwm6k3uy5es.svg)](https://markdownregistry.com/a/art_svgafvwm6k3uy5es)

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

Versions

The registry has recorded 3 versions of this file, between Jul 8, 2026 and Aug 26, 2026, about one every 24 days.

version	committed	commit	size	audit
git:20260826.571bc2f latest	2026-08-26	571bc2f	3,089 B	A	view · diff
git:20260715.fcd8714	2026-07-15	fcd8714	3,115 B	A	view · diff
git:20260708.c0884a9	2026-07-08	c0884a9	3,160 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 (3089 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

sigistry/marketplace · 3 stars · license MIT · pushed 2026-10-30 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_svgafvwm6k3uy5es
GET https://markdownregistry.com/api/v1/resolve?ref=sigistry/marketplace/incident-response
GET https://markdownregistry.com/api/v1/blob/7a59311b7edf4211295e901e18074beb4d7ce7d057af691df2cf8b7dd353fdcb

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 sigistry/marketplace

catalog-hygiene SKILL.md skill

sigistry/marketplace · plugins/a11y-i18n-remediator/skills/catalog-hygiene/SKILL.md · This skill should be used when the user mentions "translation catalog", "i18n keys", "missing translations", "unused…