slo

Define SLOs, calculate error budgets, and configure burn-rate alerts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes measurable reliability targets and operational guardrails so teams can detect SLO violations early, allocate error budgets, and balance feature velocity against customer impact. It replaces ad-hoc threshold alerts with proportional SLIs, clear burn-rate policies, and release gating to prevent repeated outages and blindspots.

Core Features & Use Cases

  • SLO, SLI & SLA alignment: Distinguishes external contracts (SLA) from internal targets (SLO) and prescribes measurable SLIs.
  • Error budget math & burn rates: Calculates per-window budgets, multi-window burn-rate thresholds, and alert severity mappings.
  • Release gating & policy: Defines rollout/rollback rules, canary thresholds, and freeze policies tied to budget remaining.
  • Dashboards & reviews: Suggests panels and review cadences for operational visibility and stakeholder alignment.
  • Use Case: Define availability and latency SLOs for a Payments API, compute monthly budgets, configure burn-rate alerts, and gate deployments when budget is low.

Quick Start

Define SLOs and error budgets for the Payments API targeting 99.9% availability over a 30-day window and configure multi-window burn-rate alerts.

Frequently Asked Questions about slo

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

FAQPage Schema
How do I define SLOs and calculate error budgets for my API?

SLOs and error budgets replace ad-hoc threshold alerts by establishing measurable reliability targets, calculating per-window budgets, and configuring multi-window burn-rate alerts to detect violations early.

How do I configure multi-window burn-rate alerts for my service?

Configuring multi-window burn-rate alerts involves calculating per-window error budgets and setting proportional alert thresholds that map to severity levels based on remaining budget and customer impact.

What is the difference between SLI, SLO, and SLA when measuring reliability?

SLIs are measurable indicators of service health, SLOs are internal reliability targets set using those SLIs, and SLAs are external contracts with customers that dictate the consequences of missing targets.

Can I use error budgets to gate deployments and prevent outages?

Yes, error budgets can gate deployments by defining rollout and rollback rules, setting canary thresholds, and enforcing release freeze policies tied to the remaining budget to prevent repeated outages.

How do I set up dashboard panels for SLO monitoring and stakeholder reviews?

Setting up SLO dashboards involves creating panels that visualize SLI formulas, error budget consumption, and burn rates, paired with regular review cadences to ensure operational visibility and stakeholder alignment.

What is the best way to apply SLOs to batch pipelines and internal services?

The best way to apply SLOs to batch pipelines and internal services is to select appropriate SLIs, set internal reliability targets distinct from external SLAs, and configure burn-rate alerts to catch violations.