agentsclimarketplace

Incident response

Skill theinterneti/TTA.dev/.github/skills/incident-response

AI devops for vibe coders

Install
npx -y skills add theinterneti/TTA.dev --skill incident-response

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Emergency response workflow for production issues

SKILL.md

1.4 KB, as published. Nobody here has run it

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

Gives 0 of the 12 instructions most incident response skills give

Counted across 224 of the 224 authors here whose files we hold, read 2026-08-06

  • Conduct a blameless postmortem within 48 hoursin 24 of 224, across 14 files
  • perform root cause analysis using five whysin 24 of 224, across 20 files
  • write a blameless postmortemin 22 of 224, across 19 files
  • Update stakeholders every 15 to 30 minutesin 19 of 224, across 9 files
  • assign an owner and due date to every action itemin 18 of 224
  • Classify incident severity within 5 minutesin 17 of 224, across 7 files
  • Create a post-mortem documentin 17 of 224, across 14 files
  • Assign all action items with deadlinesin 14 of 224, across 6 files
  • Implement immediate mitigation prioritizing user restorationin 13 of 224, across 3 files
  • assign one incident commanderin 12 of 224
  • Stop and ask for clarification if inputs are missingin 10 of 224, across 2 files
  • Escalate earlyin 10 of 224, across 2 files

Said here and by no other author read

  • receive alert from monitoring
  • check Grafana dashboards
  • query Prometheus for metrics
  • review recent deployments
  • check application logs
  • analyze distributed traces

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.