agentleFS
Sign inStart free
ulises-jeremiasulises-jeremias/agent-toolkit/skills/delivery/incident/SKILL.md

incident

Skill19 starsChanged 2 months agoMITView on GitHub

WHAT - Draft and review incident reports and RCA notes using Incident Management guidance;

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for unplanned events that disrupt or degrade production systems, live users, or critical operations.

    line 10
  2. Very specific:

    Use meeting-minutes if a validation or post-incident meeting needs minutes.

    line 16
  3. Distinctive:

    Create/link follow-up bugs or tasks only after approval.

    line 17

“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 (WHAT)

Use for unplanned events that disrupt or degrade production systems, live users, or critical operations.

Default guardrails

  1. Apply output-handshake before final output.
  2. Capture immediate mitigation separately from root cause and follow-up actions.
  3. Use meeting-minutes if a validation or post-incident meeting needs minutes.
  4. Create/link follow-up bugs or tasks only after approval.

References

  • references/default-template.md
  • references/example-payment-outage.md — example incident with full timeline, RCA, and action items
  • bug
  • meeting-minutes

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