agentleFS
Sign inStart free
ByronScottJonesByronScottJones/Agents/skills/incident-triage/SKILL.md

incident-triage

Skill7 starsChanged 2 months agoMITView on GitHub

Use when triaging a production incident, outage, security event, or service degradation. Collects bounded evidence and coordinates incident-response guidance in read-only mode unless mitigation is explicitly authorized.

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 6 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

  • srclightSkill

    explore-codebase

    This skill should be used when the user asks to "explore this codebase", "understand this project", "give me an overview", "how does this work", "onboard me", "walk me through the architecture", "map the codebase", or any request to understand a codebase's structure, architecture, or design.

    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

  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 3

    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:

    Do not expose secrets or personal data in the incident record.

    line 37
  2. Distinctive:

    Do not restart, roll back, scale, or modify production by implication.

    line 38
  3. Distinctive:

    Treat security incidents as evidence-sensitive and escalate appropriately.

    line 39

“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

Provide a disciplined first response using incident-response.md and observability.md.

Parameters

  • service: affected service or repository.
  • incidentId: optional incident identifier.
  • severity: known severity or unknown.
  • timeWindow: investigation window; default last 30 minutes.
  • includeLogs, includeMetrics, includeDeployments: default true.
  • mode: triage or mitigate; default triage.
  • format: summary or json; default summary.

Workflow

  1. Establish impact, start time, scope, and current symptoms.
  2. In read-only triage mode, recommend an incident commander and communication channel without creating assignments or channels. Execute those actions only when explicitly authorized.
  3. Collect bounded logs, metrics, traces, deployment history, and dependency status.
  4. Build a timeline and identify plausible changes or failure domains.
  5. Recommend containment and next evidence; do not make speculative changes.
  6. In mitigate mode, require explicit authorization for each operational action.
  7. Record recovery evidence and follow-up actions.

Safety

  • Preserve evidence before changing systems.
  • Do not expose secrets or personal data in the incident record.
  • Do not restart, roll back, scale, or modify production by implication.
  • Treat security incidents as evidence-sensitive and escalate appropriately.

Output

Return impact, severity, timeline, evidence sources, hypotheses, confidence, recommended actions, authorized actions, owners, and unresolved questions.

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