agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/incident-triage/SKILL.md

incident-triage

Skill1 starsChanged 41 days agoMITView on GitHub

Triage production incidents quickly and safely. Use when handling outages, elevated errors, customer-impacting bugs, or on-call debugging.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use write-runbook, threat-hunting and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MaheshAwasareSkill

    write-runbook

    Generate an operational runbook for a service from its code, config, and dependencies — what to do when it breaks, where to look, how to roll back, who to escalate to. Use proactively before a service goes to production, after a major incident, or when handing off operational ownership.

    Also in 3 projects that use this

  • allanninalSkill

    threat-hunting

    Hunt threats using Sigma detection rules and security analysis techniques. Use when investigating security incidents, creating detection rules, or analyzing suspicious activity.

    Also in 3 projects that use this

  • thlaureSkill

    review-change

    Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 2

    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:

    Scope: start/end time, affected users/regions, error rate, blast radius.

    line 11
  2. Distinctive:

    Do not deploy speculative large changes during active firefighting.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 18 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

Incident Triage

Order

  1. Stabilize: mitigate user impact (rollback, feature flag, scale, rate-limit) before deep fixes.
  2. Scope: start/end time, affected users/regions, error rate, blast radius.
  3. Signal: dashboards, logs, traces, recent deploys, dependency status.
  4. Hypothesize: top causes tied to recent changes or infra signals.
  5. Fix forward or roll back based on risk and time-to-recover.
  6. Verify: metrics return to baseline; monitor for recurrence.
  7. Notes: timeline, cause, fix, follow-ups.

Communication

Status: investigating|mitigated|resolved
Impact: ...
Current action: ...
Next update: ...

Rules

  • Prefer reversible mitigations.
  • Do not deploy speculative large changes during active firefighting.
  • Preserve evidence (logs, deploy IDs) for the postmortem.
  • One clear owner for the next action at all times.

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.

Check your setup, free