google-sre

Implement Google SRE methodology with error budgets, SLOs, and postmortems.

Updated Jan 24, 2026

Search Tags:#reliability #operations #incident response #sre #error budget #slo #toil

Ready to run

npx skills add https://github.com/copyleftdev/sk1llz --skill google-sre

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: google-sre
Source: https://github.com/copyleftdev/sk1llz/tree/main/organizations/google/sre
Command: npx skills add https://github.com/copyleftdev/sk1llz --skill google-sre

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of building and operating highly reliable services by providing a structured methodology and practical patterns for ensuring uptime and performance.

Core Features & Use Cases

SLO-Driven Operations: Define, measure, and manage Service Level Objectives (SLOs) and their associated error budgets.
Toil Elimination: Identify and automate repetitive operational tasks to free up engineering time.
Incident Management: Implement blameless postmortems and structured on-call practices.
Use Case: A team launching a new microservice can use this Skill to define clear reliability targets (SLOs), track their error budget, and establish an on-call rotation that prevents burnout, ensuring the service remains stable as it scales.

Quick Start

Apply Google's Site Reliability Engineering methodology to ensure service reliability.

Frequently Asked Questions about google-sre

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

FAQPage Schema

How do I calculate and track error budgets for SLO-driven operations?▼

Error budgets measure the gap between your Service Level Objective and actual performance. This Skill provides Python scripts to calculate error budget consumption and track SLO compliance automatically. You can define reliability targets and monitor burn rates to decide when to throttle releases.

What is the best way to eliminate toil in production operations?▼

Toil elimination identifies repetitive, manual operational tasks lacking enduring value. This Skill offers Python scripts to track toil hours and patterns, helping teams quantify operational overhead. By measuring toil, teams can prioritize automation efforts and cap operational work below 50% of engineering time.

How do I implement blameless postmortems for incident response?▼

Blameless postmortems focus on systemic root causes rather than individual mistakes. This Skill includes Markdown templates for structuring incident analysis, documenting timelines, and capturing action items. These templates ensure consistent postmortem documentation that drives improvements without assigning blame.

Do I need Python to use this SRE methodology Skill?▼

Python is required for the error budget calculation and toil tracking scripts. The Skill also includes Markdown templates for postmortems and on-call policies that do not require Python. You need Python installed to run the automated measurement components of this Skill.

Can I use this Skill to establish on-call policies for a new microservice?▼

Yes, this Skill provides Markdown templates for on-call policies suitable for new microservices. You can define rotation schedules, escalation rules, and paging thresholds. The templates help structure incident response practices that prevent burnout as your service scales.

What distinguishes SLO-driven operations from traditional monitoring approaches?▼

SLO-driven operations define explicit reliability targets and use error budgets to balance feature development with stability. Traditional monitoring tracks metrics without clear thresholds. This Skill implements Google's methodology, where error budget burn rate governs release decisions rather than subjective reliability judgments.