Use when a job run failed with an error, to walk the incident from the error to the root cause, the workaround, two solutions, the future risks, the email drafts and the log entry.
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
The job: from the first error to the log entry. It proposes and drafts. It never fixes and never sends.
Input: the date of the failed run, or the job and its run.
## Steps
1. Where it failed: the job, the task, the file and line, and the error message.
2. Status: the severity, the impact on the consumers, and the next step.
3. What happened: the run layer by layer, with each check and its result.
4. Root cause: what changed, with the rows before and after.
5. Seen before: check the incident log for the same kind of failure and its known fix.
6. Workaround: how the consumers get fresh data today.
7. Solutions: 2 options with the effort of each, and which one to recommend.
8. Future risks: every table with the same weakness, and which ones are safe.
9. Email drafts: one to the consumers and one to the source owner.
10. Log entry: draft it for the incident log, and write it after the yes.
11. Give the result as one web page.
## Output
…
The line at the top of this page pins the label git:20261029.2e2b6c2, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_o7luk2e7lb5ebho3
GET https://markdownregistry.com/api/v1/resolve?ref=datawithbaraa/claude-code-data-engineering-skills/incident
GET https://markdownregistry.com/api/v1/blob/c57a74636ddaed7645cddd3488a89abdcc455dde65a05cbd88ef6fb93a828c48
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.
datawithbaraa/claude-code-data-engineering-skills · skills/big-review/SKILL.md · Use once a month, or when the platform feels slow, heavy or cluttered, to review the whole platform from the query logs…
datawithbaraa/claude-code-data-engineering-skills · skills/contract/SKILL.md · Use when a new source is connected or a source changes how it delivers, to write the data contract with the source…
datawithbaraa/claude-code-data-engineering-skills · skills/cost-review/SKILL.md · Use for the monthly cost review of the platform, to see where the compute and the storage money goes, per job, pipeline…
datawithbaraa/claude-code-data-engineering-skills · skills/data-product/SKILL.md · Use when a table is served to consumers, released or changed, to build everything a consumer needs as a data product…
datawithbaraa/claude-code-data-engineering-skills · skills/docs/SKILL.md · Use after a change or a release, to write and refresh the runbook and the how-to guides of the project, so the runbook…
datawithbaraa/claude-code-data-engineering-skills · skills/impact/SKILL.md · Use before you change a table, a column or a function, to see what it is built from, what depends on it, who reads it…
datawithbaraa/claude-code-data-engineering-skills · skills/knowledge-refresh/SKILL.md · Use after a release, to compare the knowledge Claude Code reads, CLAUDE.md, the standards, the source pages and the…
datawithbaraa/claude-code-data-engineering-skills · skills/metadata/SKILL.md · Use when the metadata of a source has to be built or extended, to describe every table and column, the names and types…
datawithbaraa/claude-code-data-engineering-skills · skills/migration/SKILL.md · Use when an old estate of jobs and tables has to move to a new platform, to inventory it, rate it, and write the…
datawithbaraa/claude-code-data-engineering-skills · skills/pr-review/SKILL.md · Use before a pull request or another change goes in, on a file, the current diff or a branch, to review it pass by pass…
datawithbaraa/claude-code-data-engineering-skills · skills/profile/SKILL.md · Use when a new source or new files arrive, to profile them before any data contract or pipeline code is written, the…
jikig-ai/soleur · plugins/soleur/skills/incident/SKILL.md · This skill should be used when scaffolding a redaction-gated post-incident report (PIR) after a production incident.
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.github/skills/incident/SKILL.md · WHAT - Draft and review incident reports and RCA notes using Incident Management guidance;
ulises-jeremias/agent-toolkit · plugins/agent-toolkit-complete/.opencode/skills/incident/SKILL.md · WHAT - Draft and review incident reports and RCA notes using Incident Management guidance;
lamngockhuong/aiteamkit · plugins/atk/skills/incident/SKILL.md · Run a production incident and close it properly: a timeline built from evidence, impact and severity, the proven root…
greglas75/zuvo · skills/incident/SKILL.md · Incident response and postmortem generation from git/deploy context. When something breaks in production, this skill…
umararshad4/honey-stack · skills/incident/SKILL.md · Respond to a production outage: assess severity, mitigate first (roll back/flip a flag/scale), investigate safely…
