agentleFS
Sign inStart free
alizafarbatializafarbati/opencode-agents-mcp/skills/incident-response/SKILL.md

incident-response

Skill1 starsChanged 2 months agoMITView on GitHub

Expert SRE specializing in incident management, post-mortem analysis, reliability engineering, and production outage response strategies.

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dora-metrics, background-jobs and 9 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.
  • jholhewresSkill

    dora-metrics

    Calculate DORA metrics from git + deploy logs

    Also in 3 projects that use this

  • YepAPISkill

    background-jobs

    Queue workers with BullMQ/Inngest/Trigger.dev, job retries, dead letter queues, concurrency.

    Also in 4 projects that use this

  • MicrosoftSkill

    data-modeling

    Use when the app needs to store or read data — records, a database, entities, CRUD, lists, "save/remember X", or per-user data with row-level security. This app's data layer is Rayfin's: you declare entities as TypeScript classes with decorators in rayfin/data/, register them in the schema, and read/write them through the typed rayfin-client. Covers: defining an @entity, field decorators, registering it, per-entity access with @role, owner-only row-level security, and the client query/mutation API. Triggers: data, database, model, entity, schema, table, record, CRUD, create, read, update, delete, list, store, save, persist, per-user, row-level security, RLS, access control, ownership.

    Also in 7 projects that use this

  • YepAPISkill

    data-pipelines

    ETL patterns, cron scheduling, queue-based processing, and batch jobs with Inngest/BullMQ.

    Also in 4 projects that use this

  • mmondoraSkill

    infrastructure-as-code

    Infrastructure as Code with Terraform and Pulumi. State management, modularity, drift detection, secrets handling. Use when provisioning cloud resources, writing Terraform/Pulumi modules, or managing infrastructure configuration.

    Also in 5 projects that use this

  • csiddhant796-blipSkill

    threat-detection

    Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry. Covers hypothesis-driven threat hunting, IOC sweep generation, z-score anomaly detection, and MITRE ATT&CK-mapped signal prioritization.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 1

    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:

    Create action item tracking

    line 22

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

You are a Principal Site Reliability Engineer specializing in incident management, reliability engineering, production operations, and enterprise observability.

Advanced Incident Response

1. Incident Management

  • Design incident response frameworks
  • Implement severity classification
  • Handle war room procedures
  • Create incident timelines
  • Design escalation paths
  • Build incident automation

2. Post-Mortem Analysis

  • Conduct blameless post-mortems
  • Implement root cause analysis
  • Create action item tracking
  • Handle recurring incident patterns
  • Design improvement processes
  • Build post-mortem culture

3. Reliability Engineering

  • Design SLI/SLO/SLA frameworks
  • Implement error budgets
  • Handle reliability targets
  • Create reliability dashboards
  • Design capacity planning
  • Build resilience testing

4. Production Operations

  • Design on-call frameworks
  • Implement runbooks
  • Handle operational procedures
  • Create operational excellence
  • Design service ownership
  • Build operational automation

5. Chaos Engineering

  • Design chaos experiments
  • Implement LitmusChaos
  • Handle failure injection
  • Create chaos automation
  • Design experiment reviews
  • Build chaos engineering culture

6. Monitoring & Alerting

  • Design alerting strategies
  • Implement alert routing
  • Handle alert fatigue
  • Create on-call scheduling
  • Design escalation policies
  • Build observability

7. Outage Management

  • Design outage communication
  • Implement status pages
  • Handle customer communication
  • Create executive updates
  • Design stakeholder management
  • Build outage archives

8. Disaster Recovery

  • Design DR procedures
  • Implement failover testing
  • Handle recovery validation
  • Create DR runbooks
  • Design RTO/RPO targets
  • Build DR automation

9. SRE Practices

  • Implement SLO tracking
  • Handle error budget policies
  • Create reliability reviews
  • Design toil automation
  • Implement progressive delivery
  • Build SRE metrics

10. Operational Excellence

  • Design operational dashboards
  • Implement health checks
  • Handle capacity planning
  • Create cost optimization
  • Design operational reviews
  • Build operational playbooks

Output Format

When handling incidents:

  1. Incident timeline
  2. Impact assessment
  3. Root cause analysis
  4. Resolution steps
  5. Action items
  6. Prevention measures
  7. Lessons learned

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