agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/incident-triage/SKILL.md

incident-triage

Skill0 starsChanged 18 days agoMITView on GitHub

First response for a production or customer-facing incident — blast radius, stabilize vs fix, evidence to gather. Use when production is down, data is wrong in prod, users are impacted, or the user says incident, outage, sev, or page.

22 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use threat-hunting, api-design and 2 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.
  • 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

  • MicrosoftSkill

    api-design

    Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.

    Also in 3 projects that use this

  • SentrySkill

    security-review

    Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    release-notes

    Author and update release notes for Azure App Configuration libraries and providers. USE FOR: write release notes, add release note entry, update release notes, draft release notes, new version release notes, format release notes. DO NOT USE FOR: generating changelogs from git history, writing internal engineering notes.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Incident triage

Stabilize first. Do not start a feature. Do not silently patch production.

Is this the right skill?

SignalDo this instead
Local test failure / no live impactdebug or shape-work
Known change to undo after stabilizerevert-change
Root-cause after the fire is containeddebug

Required inputs

  • Symptom (what users or systems see)
  • context/environments.md and context/decision-rights.md if present

Human decisions (do not invent)

  • Rollback vs mitigate vs fix-forward vs observe
  • Destructive data repairs

Procedure

  1. Snapshot immediately (unknown allowed): started, symptom, expected, scope, severity, known/unknown. Template: references/incident-template.md.
  2. Blast radius from logs, metrics, flags, recent deploys — read, do not rewrite yet.
  3. Propose one primary action: rollback/flag off; mitigate; fix forward; observe. The incident commander decides using context/decision-rights.md; record decision evidence and environment before any runtime action. This triage profile remains read-only on runtime systems. Rollback/mitigate before a clever fix.
  4. Gather only evidence that changes the next action. No secrets.
  5. Running log of actions. When contained: debug + write-tests; handoff if another session takes over. Workflow: incident.

Output

  • Path: reply (file only if asked or the repo stores incident notes)
  • Template: references/incident-template.md

Quality bar

  • Snapshot exists with unknowns labeled
  • One primary action named
  • No silent prod change
  • Next skill named

Done

Snapshot, blast radius, action, evidence, next skill.

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