Skip to main content
skill CX Codex

generic-mitigations — Claude Code skill: what it does, how to install

generic-mitigations guides your agent to halt production outages quickly using standard SRE strategies before diving into root-cause analysis.

Apache-2.0 ★ 151 updated 2026-10-12

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add gemini-cli-extensions/sre
/plugin install sre-extension@sre
Open on GitHub

What generic-mitigations does

This skill focuses the agent on emergency SRE triage. During an active outage, stopping user impact takes precedence over finding the root cause.

It embeds a mitigation reference covering rollbacks, data restoration, feature degradation, capacity upsizing, traffic blocking, draining, and quarantining. When presented with incident signals, the model maps symptoms to these tactics and produces an ordered operational sequence.

Applying an unpracticed intervention during a live incident is hazardous. For example, building degradation toggles during firefighting will likely fail unless your service already supports turning off expensive workflows.

What it helps with

  • select stabilizing tactics during severe traffic saturation
  • structure safe rollback plans while checking for schema mismatch hazards
  • drain failing infrastructure zones without cascading secondary overloads
  • shed load by identifying non-essential workflows to degrade

Example prompts for the agent

  • Latency spiked following the latest push, draft an emergency rollback plan
  • One noisy tenant is overwhelming the database, outline quick quarantine actions
  • We face regional infrastructure issues, plan a safe traffic drain to our secondary site

How to install generic-mitigations

1Plugin marketplace

/plugin marketplace add gemini-cli-extensions/sre
/plugin install sre-extension@sre

This installs the whole sre-extension plugin with all its skills

2Skills CLI (Vercel)

npx skills add gemini-cli-extensions/sre --skill generic-mitigations -a claude-code

3Manually: put the files in place

~/.claude/skills/generic-mitigations/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/generic-mitigations/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about generic-mitigations

How to install generic-mitigations in Claude Code?

Add the marketplace and install the package with /plugin marketplace add gemini-cli-extensions/sre followed by /plugin install sre-extension@sre.

What does generic-mitigations do?

It equips the agent with standard incident response playbooks, driving swift recovery through proven actions rather than speculative debugging.

What prerequisite does the Degrade mitigation require?

Your codebase must already have toggles ready to switch off heavy or non-essential features before an incident strikes.

Source text

SKILL.md · Apache-2.0
---
name: generic-mitigations
description: 🐉 Guidance on utilizing generic mitigations for rapid incident response.
metadata:
  author: "[Ramón Medrano Llamas](https://github.com/rmedranollamas)"
  version: 0.0.1
  status: published
---

# Generic Mitigations Skill

You are an expert SRE orchestrating high-pressure incident response. Your
primary objective during an outage is to **minimize time to mitigate**, rather
than time to deeply root-cause.

Use this guidance to execute rapid actions that stabilize production systems,
buying you the time needed for detailed diagnostics.

## Core Philosophy: Duct-Tape Outage Resolution

1. **Mitigate First, Root-Cause Later:** You do not need to fully understand an
   outage to stop user impact.
1. **Favor Broad-Spectrum Actions:** Rely on predictable, pre-tested procedures
   over spontaneous hotfixes.
1. **Practice Safety Controls:** Constantly monitor health metrics after
   deploying a mitigation to confirm success or failure.

## The Generic Mitigations Reference Table

| Mitigation Strategy | Ideal Scenarios | Key Prerequisites | Primary Risks / Cautions |
| :--- | :--- | :--- | :--- |
| **Rollback** | Deployment-triggered errors, regression in business logic. | A clearly demarcated known-good build. *Note: Most services support this, but too many discover their rollbacks are broken during an outage.* | State incompatibilities (schema changes, API version mismatches). |
| **Data Rollback** | Corrupt pipeline builds, stale data, bad configurations. Highly useful for content-heavy services. | Frequent, tested backups and decoupled state. | Possible loss of legitimate transaction data during the rollback window. |
| **Degrade** | Capacity saturation, cascade failures, system-wide load. | Toggles to turn off expensive/non-essential workflows. | Reduced functionality for end-users. *Warning: Do not attempt to implement new degradation paths while firefighting.* |
| **Upsize** | Unexpected traffic spikes, resource starvation. | Scalable backing infra. It is expensive but avoids outages. | Resource exhaustion further downstream. *Note: Scaling is complex; adding replicas may shift bottlenecks.* |
| **Block List** | Single disruptive tenant, "Query of Death", DoS attack. | Quick filtering rules (API Gateway, WAF, proxy). | Over-blocking legitimate users if filters are too broad. |
| **Drain** | Localized infrastructure failures, regional blackouts. | Multi-homed environments capable of absorbing rerouted traffic. | Overloading the healthy secondary region, cascading failures. |
| **Quarantine** | Hot DB rows, spammy users, poisoned traffic streams. | Ability to separate logical usage streams instantly. | Complex orchestration; might only delay cascading side effects. |

## Model Instruction: Applying Mitigations

When dealing with a live incident:

1. **Classify symptoms immediately:** Do not jump to debugger tools. Identify
   the blast radius. Is it localized to one region? Is it tied to a recent push?
1. **Consult the Mitigations Table:** Cross-reference your observed symptoms
   against the optimal strategies above.
1. **Draft the Execution Steps:** Formulate a structured sequence (e.g., *Drain
   us-east1 -> Confirm load balances -> Evaluate latency*).
1. **Evaluate Constraints:** Check if state transitions (e.g., database schema)
   prohibit rollbacks.

*Remember: An unfamiliar mitigation is a hazard. Rely primarily on tools you
have exercised.*

## References

- **Generic Mitigations: A Philosophy of Duct-Tape Outage Resolution** by Jennifer Mace: [Google SRE Classroom](https://sre.google/classroom/generic-mitigations/)
- **How Google SREs Use Gemini CLI to Solve Real-World Outages** by Ramón Medrano Llamas and Riccardo Carlesso: [Google Cloud Blog](https://cloud.google.com/blog/topics/developers-practitioners/how-google-sres-use-gemini-cli-to-solve-real-world-outages?e=48754805)

© [Ramón Medrano Llamas](https://github.com/rmedranollamas) · Apache-2.0 · gemini-cli-extensions/sre

Similar skills

All skills for DevOps and infrastructure →

From the same set17

The whole set →
safe-sre-investigator safe-sre-investigator creates dedicated read-only service accounts for GCP and Kubernetes, then hands you gcloud and kubectl commands with a risk rating attached. CX Codex +1 ★ 151repo stars cloud-monitoring Interacts with Google Cloud Monitoring through MCP, rendering ASCII sparklines and concise CSV summaries to prevent context bloat. CX Codex +1 ★ 151repo stars postmortem-aggregator postmortem-aggregator turns Post Mortem files in a folder into incident statistics and updates POMO_AGGREGATED.md. Use it to spot recurring causes across incidents. CX Codex +1 ★ 151repo stars gcp-mcp-setup gcp-mcp-setup — a skill for Claude Code, Codex, and Gemini CLI that wires up Google Managed MCP servers (OneMCP) to your CLI environment. It enables APIs, generates an API key, and writes the MCP config to the right settings file. CX Codex +1 ★ 151repo stars monitoring-graphs monitoring-graphs — a skill for Claude Code, Codex and Gemini CLI that generates annotated incident graphs in Python. Use it to visualize outages, plot error spikes, or correlate metrics with incident milestones. CX Codex +1 ★ 151repo stars anomaly-detection anomaly-detection detects outliers in time-series metrics from CSV, cloud monitoring, and other sources. Chooses smoothing and algorithms automatically, or accepts your tuning parameters. CX Codex +1 ★ 151repo stars investigation-entrypoint The investigation-entrypoint skill for Claude Code, Codex, and Gemini CLI coordinates GCP incident investigations across GKE and Cloud Run. CX Codex +1 ★ 151repo stars postmortem-generator postmortem-generator is a Claude Code skill that turns incident context into a postmortem, timeline, action items, and a Google Doc draft. It starts after investigation and root-cause work. CX Codex +1 ★ 151repo stars

Project sponsors

Companies that keep this analytics open