reliability

Define SLOs, track SLIs, enforce error budgets, and coordinate incident response.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill reliability-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reliability
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/reliability
Command: npx skills add https://github.com/arbazkhan971/godmode --skill reliability-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams reduce production risk and operational toil by defining measurable SLOs/SLIs, enforcing error budgets, and running disciplined incident response so services remain available and performant.

Core Features & Use Cases

  • SLO, SLI & SLA design: guidance on selecting metrics (availability, latency, correctness) and setting realistic targets.
  • Error budget policy & burn-rate alerts: multi-window burn-rate thresholds and actions (freeze deploys, all-hands).
  • On-call & runbooks: escalation timelines, minimum staffing, and runbook requirements for pageable alerts.
  • Incident lifecycle & postmortems: detection, triage, mitigation, resolution, and prevention with assigned roles.
  • Production readiness checklist: monitoring, tracing, dashboards, canaries, rollbacks, and automation to reduce toil.
  • Use Case: Define a 99.9% availability SLO for a payments API, configure burn-rate alerts, create a runbook for the top pageable alert, and verify on-call escalation.

Quick Start

Use the reliability skill to define an SLO for a critical service, configure burn-rate alerts, and generate a runnable runbook for the highest-impact alert.

Frequently Asked Questions about reliability

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

FAQPage Schema
How do I define SLOs and SLIs for a web service?

To define SLOs and SLIs, select measurable metrics like availability, latency, and correctness from real user traffic, then set realistic targets such as 99.9% availability for your service.

How do I set up multi-window burn-rate alerts for error budgets?

Setting up burn-rate alerts requires a monitoring system capable of multi-window calculations to track error budget consumption, triggering actions like deploy freezes or all-hands responses when thresholds are exceeded.

What should be included in an on-call runbook for pageable alerts?

An on-call runbook for pageable alerts must include mitigation steps, escalation timelines, and minimum staffing requirements, ensuring responders can triage and resolve incidents effectively.

Do I need existing monitoring systems to enforce SLO error budgets?

Yes, enforcing error budgets requires monitoring and alerting systems capable of multi-window burn-rate calculations, measurable SLIs from real user traffic, and an established on-call escalation policy.

What is the incident response lifecycle for site reliability engineering?

The incident response lifecycle covers detection, triage, mitigation, resolution, and prevention through postmortems, utilizing assigned roles to manage production incidents and reduce operational toil.

How do I use a production readiness checklist to reduce operational toil?

A production readiness checklist reduces toil by verifying monitoring, tracing, dashboards, canaries, rollbacks, and automation are implemented before deployment, ensuring service reliability.