sre-practices

Define SLIs, SLOs, and error budgets to govern deployment decisions.

364|53|Updated May 9, 2026
One-click install
npx skills add https://github.com/cosmicstack-labs/mercury-agent-skills --skill sre-practices-cosmicstack-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sre-practices
Source: https://github.com/cosmicstack-labs/mercury-agent-skills/tree/main/categories/devops/sre-practices
Command: npx skills add https://github.com/cosmicstack-labs/mercury-agent-skills --skill sre-practices-cosmicstack-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SRE practices prevent recurring outages by turning reliability goals (SLIs/SLOs/error budgets) into clear decision rules and disciplined incident response.

Core Features & Use Cases

  • SLO/SLI/SLA guidance: Define measurable service objectives that align with user impact, such as latency and availability targets.
  • Error budget operating model: Use remaining or exhausted error budget to decide when to deploy or focus on reliability work.
  • Incident and postmortem process: Establish severity levels, incident roles, and blameless action items with owners and due dates.
  • Reliability patterns: Apply common resilience techniques like circuit breakers, bulkheads, retries with backoff, rate limiting, and graceful degradation.

Quick Start

Draft an SLO set for our service using the metrics our users care about, explain the error budget policy for deployments, and outline a blameless postmortem template with SEV levels and incident roles.

Frequently Asked Questions about sre-practices

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

FAQPage Schema
How do I define SLOs and error budgets for my service deployments?

SLOs and error budgets are defined by establishing SLIs for metrics like latency and availability, then calculating the remaining error budget to govern whether to deploy new features or focus on reliability work.

What is a blameless postmortem template for incident response?

A blameless postmortem template outlines incident severity levels, assigns specific response roles, and tracks actionable incident items with designated owners and due dates to prevent recurring outages without assigning blame.

How do I use error budgets to make deployment decisions?

Error budgets operationalize deployment decisions by using the remaining or exhausted budget as a clear rule: if the budget is depleted, deployments pause to prioritize reliability work over new features.

What resilience patterns should I apply to prevent production outages?

Resilience patterns like circuit breakers, bulkheads, retries with backoff, rate limiting, and graceful degradation should be applied to protect production services and maintain availability during partial failures.

When do I need an incident response playbook with severity levels?

An incident response playbook with severity levels is needed when operationalizing reliability targets, ensuring disciplined response roles and blameless action item tracking during production service outages.