Site Reliability Engineering

Define SLIs and SLOs to quantify system reliability and track error budgets.

1|2|Updated Feb 5, 2026

Search Tags:#observability #reliability #sre #incident management #error budget #slo

Ready to run

npx skills add https://github.com/7a336e6e/skills --skill site-reliability-engineering

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Site Reliability Engineering
Source: https://github.com/7a336e6e/skills/tree/main/devops/site-reliability
Command: npx skills add https://github.com/7a336e6e/skills --skill site-reliability-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams define and maintain service reliability by establishing clear objectives and managing operational risks, ensuring a balance between feature delivery and system stability.

Core Features & Use Cases

SLO Definition: Quantify reliability targets (e.g., availability, latency) for services.
Error Budget Management: Track deviations from SLOs to inform deployment decisions (e.g., code freezes).
Incident Review: Conduct blameless post-mortems to learn from outages and prevent recurrence.
Use Case: After a service experiences downtime, use this Skill to define SLIs, set an SLO, manage the resulting error budget, and conduct a blameless post-mortem to identify root causes and implement preventative measures.

Quick Start

Use the Site Reliability Engineering skill to define SLIs and SLOs for the user authentication service.

Frequently Asked Questions about Site Reliability Engineering

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

FAQPage Schema

How do I define SLIs and SLOs to quantify system reliability?▼

Defining SLIs and SLOs involves quantifying reliability targets like availability and latency for your services. This establishes clear objectives to balance feature delivery with system stability using data-driven operational insights.

How does error budget tracking inform deployment decisions?▼

Error budget tracking monitors deviations from your SLOs to inform deployment decisions. When error budgets are depleted, it triggers operational actions like code freezes to maintain system reliability and prevent outages.

What is a blameless post-mortem in incident management?▼

A blameless post-mortem in incident management is a review process conducted after outages to identify root causes without assigning blame. It focuses on learning from incidents to implement preventative measures and prevent recurrence.

Can I use this approach to manage operational risks for our authentication service?▼

Yes, you can manage operational risks for an authentication service by defining specific SLIs and SLOs. This quantifies reliability targets and tracks error budgets to support operational decision-making and maintain stability.

What is the best way to balance feature velocity and system stability?▼

The best way to balance feature velocity and system stability is by establishing SLOs and tracking error budgets. This provides data-driven insights into system performance, informing exactly when to pause feature delivery for reliability fixes.