agentleFS
Sign inStart free
theinternetitheinterneti/TTA.dev/.github/skills/incident-response/SKILL.md

Incident Response

Skill0 starsChanged 7 months agoMITView on GitHub

Emergency response workflow for production issues

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Verify metrics return to normal

    line 44
  2. Distinctive:

    Write incident report in Logseq

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Response Skill

Overview

Emergency workflow for handling production incidents with DevOps Engineer and Observability Expert.

Duration: Variable (15 minutes - 2 hours) Personas Required: DevOps, Observability

Incident Workflow

Phase 1: Detect (@observability-expert)

Actions:

  1. Receive alert from monitoring
  2. Check Grafana dashboards
  3. Query Prometheus for metrics
  4. Assess impact and severity

Phase 2: Investigate (@devops-engineer + @observability-expert)

Actions:

  1. Review recent deployments
  2. Check application logs
  3. Analyze distributed traces
  4. Identify root cause

Phase 3: Mitigate (@devops-engineer)

Actions:

  1. Rollback deployment if needed
  2. Scale resources if capacity issue
  3. Apply hotfix if minor bug
  4. Notify stakeholders

Phase 4: Resolve (@devops-engineer)

Actions:

  1. Verify metrics return to normal
  2. Close alerts
  3. Monitor for 30 minutes
  4. Document actions

Phase 5: Postmortem (@observability-expert)

Actions:

  1. Write incident report in Logseq
  2. Identify preventive measures
  3. Update runbooks
  4. Share learnings with team

Success Criteria

  • ✅ Incident detected <5 minutes
  • ✅ Response initiated <10 minutes
  • ✅ Service restored <1 hour
  • ✅ Postmortem complete <24 hours
  • ✅ Preventive measures implemented

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