Skills Guide

Site Reliability Engineering

VerifiedSafe

Define Service Level Objectives (SLOs), manage Error Budgets, and conduct incident reviews to balance reliability with velocity.

Download and use
Sby Skills Guide Bot
DevOpsIntermediate
6/2/2026
Claude CodeCursorWindsurfCopilotCodex
#site-reliability-engineering#service-level-objectives#error-budget#incident-management#blameless-post-mortem

Recommended for

Backend developerClaude CodeCursorCopilotDevOps engineerWindsurf

Automated summary

Defines Service Level Objectives, manages Error Budgets, and conducts Incident Reviews to balance reliability with velocity.

Strengths

  • Quantifies reliability with measurable SLOs.
  • Provides a clear code freeze mechanism via error budgets.
  • Encourages blameless post-mortems to learn from incidents.
  • Automates runbooks and reduces alert fatigue.

Limitations

  • Requires accurate and reliable monitoring data.
  • Can be challenging to implement without existing DevOps culture.
  • Overly aggressive SLOs can create tension between teams.
When to use it

Use this skill to define objective stability criteria and manage trade-offs between new features and reliability.

When not to use it

Avoid if infrastructure is still being built or if teams lack necessary monitoring tools.

Security analysis

Safe
Quality score85/100

This skill provides guidance on SRE practices such as defining SLIs, setting SLOs, and incident management. It does not involve any executable instructions or use of tools that could compromise security. Therefore, it poses no meaningful execution risk.

No concerns found

How this analysis is made

Examples

Define SLOs for a web service
Help me define SLOs for our e-commerce API. We want 99.9% availability over a 30-day rolling window and latency below 200ms for 95% of requests.
Conduct a blameless post-mortem
We had a production outage last night due to a database migration failure. Can you guide me through a blameless post-mortem using the 5 Whys technique and create an action plan?
Manage error budgets
Our error budget for the month is nearly exhausted (only 0.02% remaining). Should we do a code freeze? What processes should we put in place?

name: Site Reliability Engineering description: Define Service Level Objectives (SLOs), manage Error Budgets, and conduct Incident Reviews to balance reliability with velocity.

Site Reliability Engineering (SRE)

Goal

Treat operations as a software problem. Quantify reliability so we know exactly when to freeze deployments (reliability at risk) and when to push fast (error budget available).

When to Use

  • When defining "Is it stable enough?" criteria.
  • After a production outage (Post-Mortem).
  • When planning on-call rotations.

Instructions

1. Define SLIs (Service Level Indicators)

What is "good"?

  • Availability: Successful requests / Total requests.
  • Latency: Requests faster than 200ms / Total requests.

2. Set SLOs (Service Level Objectives)

What is the target? (100% is impossible).

  • Target: "99.9% of requests in 30 days are successful."
  • Window: Rolling 28 or 30 days.

3. Manage Error Budgets

(100% - SLO) = Error Budget.

  • If you have 0.1% budget, you can fail 43 minutes a month.
  • Rule: If budget is exhausted -> Code Freeze. Only reliability fixes allowed.

4. Incident Management

When things break:

  1. Detect: Alert fires.
  2. Respond: Acknowledge, triage, stabilize (mitigate impact).
  3. Analyze: Root cause analysis (5 Whys).
  4. Learn: Create action items to prevent recurrence.

Constraints

✅ Do

  • DO: Blameless Post-Mortems. Focus on process failure, not human error.
  • DO: Automate runbooks. If you run a command twice, script it.
  • DO: Measure what matters to the user (Client-side latency), not just the server.

❌ Don't

  • DON'T: Alert on things you can't fix immediately.
  • DON'T: Page the whole team. Page the on-call engineer.
  • DON'T: Optimize reliability past the SLO (diminishing returns).

Output Format

  • SLOs.md: Definitions of SLIs and targets.
  • post-mortems/YYYY-MM-DD-incident.md: Incident review records.

Dependencies

  • devops/implementing-observability/SKILL.md

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/site-reliability-engineering-mm5t8c99/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/site-reliability-engineering-mm5t8c99' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/site-reliability-engineering-mm5t8c99/download' --output '.skill-downloads/site-reliability-engineering-mm5t8c99/SKILL.md.part' && mv '.skill-downloads/site-reliability-engineering-mm5t8c99/SKILL.md.part' '.skill-downloads/site-reliability-engineering-mm5t8c99/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: Dependencies
  • devops/implementing-observability/SKILL.md

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/site-reliability-engineering-mm5t8c99/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Configure a Chat Channel with SecretRefs

DevOps

Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.

Claude CodeCodexintermediateSafe 387,940
Skills Guide Bot

Investigate ClickHouse CI Failures

DevOps

Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.

Claude CodeadvancedSafe 49,516
Skills Guide Bot

Ansible PR Review

DevOps

Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.

Claude CodeintermediateSafe 70,491
Skills Guide Bot