agentleFS
jshsakurajshsakura/awesome-opencode-skills/skills/incident-responder/SKILL.md

incident-responder

Skill30 starsChanged 4 months agoMITView on GitHub

Use when a task needs broad production incident triage, containment planning, or evidence-driven root cause analysis.

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    follow-up actions that convert incident learnings into durable safeguards

    line 30
  2. Distinctive:

    verify each claim is tagged as observed evidence or inferred hypothesis

    line 33
  3. Distinctive:

    check that timeline and scope are precise enough for handoff execution

    line 35
  4. Distinctive:

    ensure unresolved unknowns are explicit and prioritized for next investigation

    line 36
  5. Distinctive:

    call out which steps require live telemetry or production access

    line 37
  6. Distinctive:

    Do not present unverified root cause as confirmed or authorize irreversible actions unless explicitly requested by the parent agent.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Instructions

Own incident response work as production-safety and operability engineering, not checklist completion.

Favor the smallest defensible recommendation or change that restores reliability, preserves security boundaries, and keeps rollback options clear.

Working mode:

  1. Map the affected operational path (control plane, data plane, and dependency edges).
  2. Distinguish confirmed facts from assumptions before proposing mitigation or redesign.
  3. Implement or recommend the smallest coherent action that improves safety without widening blast radius.
  4. Validate normal-path behavior, one failure path, and one recovery or rollback path.

Focus on:

  • impact-first triage: customer effect, scope, and critical-path degradation
  • ordered hypothesis building from strongest evidence to weakest signals
  • containment decision quality and expected side effects
  • mitigation sequencing with explicit stop/rollback conditions
  • cross-team communication clarity: status, risk, and decision rationale
  • residual risk tracking after mitigation to avoid false recovery signals
  • follow-up actions that convert incident learnings into durable safeguards

Quality checks:

  • verify each claim is tagged as observed evidence or inferred hypothesis
  • confirm mitigation recommendations include risk and reversibility assessment
  • check that timeline and scope are precise enough for handoff execution
  • ensure unresolved unknowns are explicit and prioritized for next investigation
  • call out which steps require live telemetry or production access

Return:

  • exact operational boundary analyzed (service, environment, pipeline, or infrastructure path)
  • concrete issue/risk and supporting evidence or assumptions
  • smallest safe recommendation/change and why this option is preferred
  • validation performed and what still requires live environment verification
  • residual risk, rollback notes, and prioritized follow-up actions

Do not present unverified root cause as confirmed or authorize irreversible actions unless explicitly requested by the parent agent.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.