Updated 3d ago
by mawero83
google-sre-skills
Unofficial agnet skills for Google SRE practices (SLOs, incidents, AI ops). Not affiliated with Google.
20 GitHub stars (20)
+20 in 4 days
| Period | New stars |
|---|---|
| Nov 2 | +1 |
| Nov 3 | +1 |
- 30 skills (30 skills found in its SKILL.md files)
- 4 forks (4 forks)
- 3d ago last update (Last updated 3d ago)
Install
Skills CLI
npx skills add mawero83/google-sre-skills
Asks which skills and agents to install. Just one: npx skills add mawero83/google-sre-skills --skill ai-supports-sre — add -g for every project.
Claude Code
git clone https://github.com/mawero83/google-sre-skillscp -r "google-sre-skills/.cursor/skills/ai-supports-sre" ~/.claude/skills/
Copies the ai-supports-sre skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add mawero83/google-sre-skills
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md — showing the first 30 of 55 files.
-
ai-supports-sre
Use AI as an SRE force multiplier safely: triage assistance, telemetry interrogation, toil reduction, and bounded autonomy — from SRE Book 2e Ch21. Use when adopting AI ops tools or agentic incident helpers.
.cursor/skills/ai-supports-sre/SKILL.md on GitHub (opens in a new tab) -
alert-noise-reduction
Diagnose and reduce paging noise using SRE practices: symptom vs cause, actionability, dependency fan-in, flapping, and SLO-based alerting. Use when on-call is drowning, auditing alert health, or cutting false positives.
.cursor/skills/alert-noise-reduction/SKILL.md on GitHub (opens in a new tab) -
alerting-on-slos
Turn SLOs into actionable multi-window multi-burn-rate alerts that page on significant error-budget consumption. Use when creating burn alerts, replacing threshold spam, or tuning pages-per-shift.
.cursor/skills/alerting-on-slos/SKILL.md on GitHub (opens in a new tab) -
anomaly-detection
Apply statistical and ML-aware anomaly approaches for SRE: baselines, seasonality, binomial error-rate intuition, and post-alert analysis. Use when tuning detectors, investigating weird metrics, or adding intelligent alerting.
.cursor/skills/anomaly-detection/SKILL.md on GitHub (opens in a new tab) -
automation-tooling
Decide what to automate and how: levels of automation, incremental approach, pitfalls, and human factors from Google SRE. Use when building ops automation, Autopilot-style systems, or AI ops agents.
.cursor/skills/automation-tooling/SKILL.md on GitHub (opens in a new tab) -
availability-math
Use availability math tactically: nines tables, downtime budgets, and error-budget arithmetic for planning and communication. Use when converting SLOs to allowed downtime/failure counts.
.cursor/skills/availability-math/SKILL.md on GitHub (opens in a new tab) -
canarying-releases
Design and evaluate canaries: metrics, blast radius, abort criteria, and automation from the SRE Workbook. Use before risky prod changes and when building progressive delivery.
.cursor/skills/canarying-releases/SKILL.md on GitHub (opens in a new tab) -
capacity-planning
Plan capacity the modern Google SRE way: demand forecasting, uncertainty, failure domains, efficiency, and AI-era accelerator constraints. Use for capacity reviews, launches, and resource risk.
.cursor/skills/capacity-planning/SKILL.md on GitHub (opens in a new tab) -
cascading-failures
Detect and break cascading failures: latency death spirals, retry storms, shared fate, and recovery strategies from Google SRE. Use during incidents with amplifying failure or design reviews for cascade risk.
.cursor/skills/cascading-failures/SKILL.md on GitHub (opens in a new tab) -
cloud-reliability
Apply SRE in cloud and hybrid environments: shared responsibility, managed services, multi-cloud observability, and platform trends from Google SRE 2e and sre.google/cloud. Use for cloud architecture and ops model design.
.cursor/skills/cloud-reliability/SKILL.md on GitHub (opens in a new tab) -
composing-slos
Compose multi-service reliability mathematically: serial vs parallel dependencies, hedging, and dependency budgets. Use when deriving platform or path SLOs from dependencies.
.cursor/skills/composing-slos/SKILL.md on GitHub (opens in a new tab) -
configuration-design
Design safe configuration systems: validation, separation of config/code risks, rollout of config, and avoiding dangerous defaults — from the SRE Workbook. Use for config platform design and config-caused outages.
.cursor/skills/configuration-design/SKILL.md on GitHub (opens in a new tab) -
crisis-management
Manage organizational crises spanning reliability and security: prestaging, crisis comms, cross-functional command, and aftermath — from Building Secure & Reliable Systems. Use for wide-impact disasters and security crises.
.cursor/skills/crisis-management/SKILL.md on GitHub (opens in a new tab) -
data-integrity
Protect data integrity and recoverability: RPO/RTO/RWO, backups vs snapshots, restore testing, and 'what you read is what you wrote'. Use for data risk reviews and backup strategy.
.cursor/skills/data-integrity/SKILL.md on GitHub (opens in a new tab) -
data-pipelines
Design reliable data/processing pipelines: correctness, freshness, completeness, late data, and idempotency per Google SRE. Use for ETL/stream reliability and pipeline SLOs.
.cursor/skills/data-pipelines/SKILL.md on GitHub (opens in a new tab) -
designing-for-resilience
Design resilient products using Google SRE 2e principles: progressive rollout, defense in depth, failure domains, overload controls, data resilience, and emergency modes. Use for architecture reviews and reliability design decisions.
.cursor/skills/designing-for-resilience/SKILL.md on GitHub (opens in a new tab) -
disaster-planning
Create pragmatic disaster plans: prestaging, DR tests, roles, and scenario playbooks from Building Secure & Reliable Systems. Use for DR programs and wide-scale outage preparedness.
.cursor/skills/disaster-planning/SKILL.md on GitHub (opens in a new tab) -
distributed-consensus-reliability
Reason about distributed consensus for reliability: when to use Paxos/Raft style systems, failure modes, and operational risks from Google SRE. Use when designing strongly consistent control planes or debugging quorum pain.
.cursor/skills/distributed-consensus-reliability/SKILL.md on GitHub (opens in a new tab) -
effective-troubleshooting
Run structured troubleshooting: problem statement, hypothesis tree, divide-and-conquer, and evidence logging per Google SRE. Use during incidents or deep production debugging.
.cursor/skills/effective-troubleshooting/SKILL.md on GitHub (opens in a new tab) -
eliminating-toil
Identify, measure, and eliminate toil using Google SRE definitions and automation strategy. Use when on-call is drowning in repetitive work, planning automation, or defending engineering time.
.cursor/skills/eliminating-toil/SKILL.md on GitHub (opens in a new tab) -
embracing-risk
Apply Google SRE risk thinking: reliability targets below 100%, cost of reliability, and risk as a product decision. Use when setting targets, debating uptime goals, or pushing back on perfectionism.
.cursor/skills/embracing-risk/SKILL.md on GitHub (opens in a new tab) -
emergency-response
Execute emergency response playbooks: what to do when paged, prioritization under stress, and safe emergency changes. Use for Sev-level events and emergency rollouts.
.cursor/skills/emergency-response/SKILL.md on GitHub (opens in a new tab) -
error-budget-policy
Draft and enforce Google-style error budget policies that balance feature velocity with reliability: freezes, postmortem triggers, and planning inputs. Use when defining what happens when an SLO is missed.
.cursor/skills/error-budget-policy/SKILL.md on GitHub (opens in a new tab) -
handling-overload
Prevent and handle overload: load shedding, throttling, queue management, and graceful degradation per Google SRE. Use when systems melt under traffic or retries, or designing anti-overload controls.
.cursor/skills/handling-overload/SKILL.md on GitHub (opens in a new tab) -
incident-management
Run Google-style incident management: roles (IC, comms, ops), severity, lifecycle detection→triage→investigate→mitigate→resolve→learn, and state documents. Use for live incidents and process design.
.cursor/skills/incident-management/SKILL.md on GitHub (opens in a new tab) -
learning-from-incidents
Run blameless postmortems and learning systems: action items that fix systems not people, CAST/systems thinking awareness, and follow-through. Use after incidents and when improving learning culture.
.cursor/skills/learning-from-incidents/SKILL.md on GitHub (opens in a new tab) -
learning-path-sre
Guide an SRE learning path from Google canonical books through practical skills in this pack: sequenced study + practice projects. Use when onboarding, self-study, or building a curriculum.
.cursor/skills/learning-path-sre/SKILL.md on GitHub (opens in a new tab) -
load-management
Apply load balancing and load management practices from Google SRE: frontend and datacenter LB concepts, healthy traffic shaping, and Workbook load guidance. Use when designing traffic systems or fixing imbalanced load.
.cursor/skills/load-management/SKILL.md on GitHub (opens in a new tab) -
monitoring-observability
Design monitoring and observability the Google SRE way: four golden signals, telemetry vs analytics, OpenTelemetry, customer-centric monitoring, and value-vs-cost of data. Use when building dashboards, instrumentation plans, or observability architecture.
.cursor/skills/monitoring-observability/SKILL.md on GitHub (opens in a new tab) -
nalsd-system-design
Practice Non-Abstract Large System Design (NALSD): quantitative design with back-of-envelope capacity, bottlenecks, and iterative refinement from the SRE Workbook. Use for design interviews, RFCs, and capacity-aware design.
.cursor/skills/nalsd-system-design/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.