incident-response

Name: incident-response
Availability: InStock
Author: clawpod-app

Analyze production incident metrics and output rollback recommendations.

46|11|Updated Mar 29, 2026

Search Tags:#rollback #production #metrics #latency #on-call #incident

Ready to run

npx skills add https://github.com/clawpod-app/awesome-openclaw-agent-packs --skill incident-response-clawpod-app

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/clawpod-app/awesome-openclaw-agent-packs/tree/main/packs/devops/skills/incident-response
Command: npx skills add https://github.com/clawpod-app/awesome-openclaw-agent-packs --skill incident-response-clawpod-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assess production incidents and recommend rollback decisions by analyzing error rates, latency, and resource metrics to determine severity and next steps.

Core Features & Use Cases

Identify affected service and deployment history to pinpoint root cause and impact.
Collect current metrics (error rate, P50/P95/P99 latency, CPU, memory) and compare against baselines.
Output a structured incident assessment with actionable rollback or mitigation recommendations, suitable for on-call triage and postmortems.

Quick Start

Provide an incident assessment for the current production service and suggest a rollback if thresholds are exceeded.

Frequently Asked Questions about incident-response

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I decide if a production incident requires a rollback based on error rates and latency?▼

Determine if a production rollback is needed by collecting current error rates, P50/P95/P99 latency, CPU, and memory usage, then comparing them against baseline thresholds. This process outputs a structured incident assessment with actionable rollback recommendations.

What metrics do I need to collect for on-call triage during an outage?▼

Collect error rates, P50/P95/P99 latency, and CPU and memory resource metrics for on-call triage during an outage. Comparing these against baseline thresholds identifies the root cause and impact to output a structured incident assessment.

Can I use threshold analysis to assess elevated error rates across my deployments?▼

Yes, you can assess elevated error rates across deployments by applying threshold analysis to current metrics. Comparing current error rates and latency spikes against baselines determines severity and outputs recommended rollback or mitigation actions.

When should I not use an automated rollback decision for a latency spike?▼

You should not rely solely on an automated rollback decision when CPU and memory resource metrics remain within normal baselines despite a latency spike. Accurate rollback decisions require comparing all collected metrics against baselines to confirm a deployment is the actual root cause.

What is the best way to structure an incident assessment for postmortems?▼

Structure an incident assessment for postmortems by outputting a summary that compares current error rates, latency, and resource metrics against baselines. Include threshold analysis results and actionable rollback or mitigation recommendations to guide future prevention.