incident SKILL.md skillA

incident from higoralves/orc is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add higoralves/orc/incident@git:20261106.693b476

Pins git:20261106.693b476 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
higoralves/orc
Path
codex/orc/content/skills/incident/SKILL.md
Versions recorded
1
Latest version
git:20261106.693b476, committed Nov 6, 2026
Size
4,113 bytes
Repository stars
7
License
MIT

Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline.

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

# $orc-incident

Run an incident while it happens: triage the evidence, size the blast radius, choose mitigate-first or root-cause-first, and keep a UTC timeline that becomes the postmortem's spine. Stop the bleeding before you study the wound; `$orc-postmortem` learns from the incident afterwards.

## Arguments

- First argument (free-form) — a Sentry issue short ID or URL, a pasted stack trace, or a described symptom.
- `--severity sev-1|sev-2|sev-3` — optional. Skips the severity proposal in P2; P2 still assesses the blast radius.

NOTE: a Sentry short ID looks like `PROJ-123`; `orc-sentry-cli` pulls it live. A symptom reads like "checkout is 500ing since the 14:00 deploy".

## Preconditions

> **🛑 No production mutations**
>
> P3 previews rollbacks, flag flips and scaling calls; the user executes them. orc records; the human acts.

- A `loose` context stops the run in Phase 0: there is no state dir to write.
- Every action or finding in any phase appends a UTC row to `timeline.md` in the same turn.
- Timestamps come from `date -u +%Y-%m-%dT%H:%M:%SZ`.

## Phases
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_6hkdecytquosp3gv/48a90d96efe0b8b8fcbe54362feece4e2aa66632c1fbeaca0c032d61ee8601f2.json

Then /plugin install incident@markdownregistry-6hkdecytquosp3gv in Claude Code. It installs git:20261106.693b476, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add higoralves/orc/incident@sha256:48a90d96efe0b8b8

The line at the top of this page pins the label git:20261106.693b476, 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 badge

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

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

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in higoralves/orc/incident since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of incident from somewhere else? Ask it: where did my incident come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Nov 6, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261106.693b476 latest2026-11-06 693b476 4,113 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

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 (4113 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

higoralves/orc · 7 stars · license MIT · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_6hkdecytquosp3gv
GET https://markdownregistry.com/api/v1/resolve?ref=higoralves/orc/incident
GET https://markdownregistry.com/api/v1/blob/48a90d96efe0b8b8fcbe54362feece4e2aa66632c1fbeaca0c032d61ee8601f2

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 higoralves/orc

AGENTS.md AGENTS.md file
higoralves/orc · AGENTS.md
git:20261106.693b476 · audit A · 7 stars
CLAUDE.md CLAUDE.md file
higoralves/orc · CLAUDE.md
git:20261020.ba1d30b · audit A · 7 stars
playwright-qa SKILL.md skill
higoralves/orc · adapters/codex/content/skills/playwright-qa/SKILL.md · Playwright QA on Codex with preconfigured test agents and MCP; otherwise use the agent-browser driver.
git:20261106.693b476 · audit A · 7 stars
adr-writing SKILL.md skill
higoralves/orc · codex/orc/content/skills/adr-writing/SKILL.md · Author and update Architecture Decision Records (ADRs) — the durable record of a decision and its trade-offs, in…
git:20261106.693b476 · audit A · 7 stars
agent-browser SKILL.md skill
higoralves/orc · codex/orc/content/skills/agent-browser/SKILL.md · Browser automation CLI for AI agents; use for web tasks - navigate, click, fill forms, screenshot, scrape, test…
git:20261106.693b476 · audit A · 7 stars
architecture-patterns SKILL.md skill
higoralves/orc · codex/orc/content/skills/architecture-patterns/SKILL.md · Implement Clean, Hexagonal (Ports & Adapters), and Domain-Driven architecture patterns
git:20261106.693b476 · audit A · 7 stars
browser-qa SKILL.md skill
higoralves/orc · codex/orc/content/skills/browser-qa/SKILL.md · The canonical browser-QA protocol for web changes — target resolution, env attach, the driver gate (Playwright primary…
git:20261106.693b476 · audit A · 7 stars
callouts SKILL.md skill
higoralves/orc · codex/orc/content/skills/callouts/SKILL.md · The orc callout palette — emoji-header blockquotes in conversation, GitHub-flavored [!TYPE] form for GitHub-bound output
git:20261106.693b476 · audit A · 7 stars
caveman-pr SKILL.md skill
higoralves/orc · codex/orc/content/skills/caveman-pr/SKILL.md · Ultra-compressed, signal-only pull request descriptions
git:20261106.693b476 · audit A · 7 stars
caveman-review SKILL.md skill
higoralves/orc · codex/orc/content/skills/caveman-review/SKILL.md · Ultra-compressed code review comments — one line per finding: location, problem, fix
git:20261106.693b476 · audit A · 7 stars
ci-routing SKILL.md skill
higoralves/orc · codex/orc/content/skills/ci-routing/SKILL.md · The canonical route-on-verdict protocol for a red CI diagnosis — fixable/flake/infra/needs-debug handling, the…
git:20261106.693b476 · audit A · 7 stars
cleanup SKILL.md skill
higoralves/orc · codex/orc/content/skills/cleanup/SKILL.md · Clean up after completed or abandoned orc sessions — removes workspace state, registry entry, git worktree, and…
git:20261106.693b476 · audit A · 7 stars

Every file in higoralves/orc

Other files named incident

incident SKILL.md skill
datawithbaraa/claude-code-data-engineering-skills · skills/incident/SKILL.md · Use when a job run failed with an error, to walk the incident from the error to the root cause, the workaround, two…
git:20261029.2e2b6c2 · audit A · 101 stars
incident SKILL.md skill
anantys-oss/koan · koan/skills/core/incident/SKILL.md · Triage and fix a production error from a pasted stack trace or log snippet
v1.0.0 · audit A · 50 stars
incident SKILL.md skill
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.
git:20261105.9914b91 · audit A · 21 stars
incident SKILL.md skill
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;
git:20260831.856ee57 · audit A · 20 stars
incident SKILL.md skill
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;
git:20260831.856ee57 · audit A · 20 stars
incident SKILL.md skill
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…
git:20261106.96eea03 · audit A · 12 stars
incident SKILL.md skill
greglas75/zuvo · skills/incident/SKILL.md · Incident response and postmortem generation from git/deploy context. When something breaks in production, this skill…
git:20260906.015072f · audit A · 7 stars
incident SKILL.md skill
higoralves/orc · orc/skills/incident/SKILL.md · Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep…
git:20261020.7a1f356 · audit A · 7 stars

Browse by kind, by grade A, or by owner.