site-reliability-engineering

Define SLOs/SLIs, burn-rate alerts, runbooks, and postmortems for production reliability.

15|3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/LazyIsEfficient/agentic-os --skill site-reliability-engineering-lazyisefficient
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: site-reliability-engineering
Source: https://github.com/LazyIsEfficient/agentic-os/tree/main/.claude/skills/site-reliability-engineering
Command: npx skills add https://github.com/LazyIsEfficient/agentic-os --skill site-reliability-engineering-lazyisefficient

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

In production, reliability is the difference between user trust and churn. This Skill provides a structured playbook for operating systems in production through SLOs/SLIs, alerting policies, runbooks, and blameless postmortems to reduce toil and improve resilience.

Core Features & Use Cases

  • Define and monitor SLOs/SLIs to quantify service reliability.
  • Create and maintain incident response runbooks and postmortems to learn and improve.
  • Plan and run resilience exercises (tabletops, gamedays) and chaos engineering to validate readiness.
  • Manage runtime capacity and toil through automation backlogs and resilience planning.

Quick Start

Draft a simple SLO for a live service, implement one burn-rate alert, and prepare a basic runbook template for the next incident.

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 and monitor SLOs and SLIs to quantify service reliability?

To define SLOs and SLIs, you establish measurable service level indicators and set objective thresholds for reliability. This Skill provides structured playbooks to operationalize these metrics, enabling you to monitor service uptime and quantify reliability concretely.

What is the best way to create incident response runbooks and blameless postmortems?

Creating incident response runbooks and blameless postmortems requires structured templates for escalation and learning. This Skill enforces concrete, auditable requirements for observability and blameless postmortems to reduce toil and improve incident response.

How do I plan and run chaos engineering and resilience exercises like gamedays?

Planning chaos engineering and resilience exercises involves organizing tabletops and gamedays to validate readiness. This Skill helps you plan and run these exercises to test runtime capacity, manage toil, and validate your system's resilience against failures.

How do burn-rate alerts work for SLO-based incident response?

Burn-rate alerts monitor how quickly you are consuming your error budget relative to defined SLOs. This Skill helps you implement these alerts to trigger incident response runbooks proactively before service reliability drops below acceptable thresholds.

Does this approach to site reliability engineering require existing observability setup?

Site reliability engineering requires existing observability data to define meaningful SLIs and burn-rate alerts. This Skill enforces concrete, auditable requirements for observability, meaning you need baseline monitoring data to operationalize reliability effectively.