incident-triage SKILL.md skillA
incident-triage from trevhud/rote is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add trevhud/rote/incident-triage@git:20261020.d5cace8Pins git:20261020.d5cace8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- trevhud/rote
- Path
examples/holdout/incident-triage/skill/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261020.d5cace8, committed Oct 20, 2026
- Size
- 7,080 bytes
- Repository stars
- 8
- License
- Apache-2.0
First-responder triage for a PagerDuty page. Acknowledges the incident, figures out which service is hurting and who owns it, pulls recent deploys and error logs, assigns a severity from the severity matrix, forms a first hypothesis, digs until the picture is clear, posts the triage summary to the owning team's incident channel, and hands off to the incident commander. Use when you get paged, when someone says "triage incident <id>", or "what's going on with this alert".
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
# On-call incident triage This is the runbook we follow as the first responder when PagerDuty pages us. The goal of triage is NOT to fix the incident. The goal is to get the right people looking at the right thing within the first 15 minutes, with a severity everyone agrees on and a written summary that the incident commander (IC) can work from. Fixing comes after. We wrote this down after a bad quarter where three incidents sat unacknowledged for 20+ minutes and two more were run at the wrong severity for an hour because the responder "had a feeling." So some of the steps below are marked MANDATORY. Please don't skip them, even when the incident looks trivial or you already know what's wrong. The only input is the PagerDuty incident id (it's in the page, e.g. `Q1ABCD2EFGH3IJ`). ## Step 1: Acknowledge the page (MANDATORY) Acknowledge the incident in PagerDuty right away with the `acknowledge_incident` tool on the PagerDuty MCP. Do this before you read anything else. An unacknowledged page escalates to the secondary after 5 minutes and to the engineering manager after 10, and nobody wants that. At the same time, pull the full incident with `get_incident` (also on the …
Read the whole file at its exact version.
How to install
mdr add trevhud/rote/incident-triage@sha256:ae533865178bf1b5The line at the top of this page pins the label git:20261020.d5cace8, 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_jgoqnfygp76cupaq)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 20, 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 (7080 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
trevhud/rote · 8 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jgoqnfygp76cupaq GET https://markdownregistry.com/api/v1/resolve?ref=trevhud/rote/incident-triage GET https://markdownregistry.com/api/v1/blob/ae533865178bf1b5a856673e7d81a2dd5cfb5fd2468037515d4d99055e5232c7
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.