slo-implementation

Define SLIs, SLOs, and error budgets with Prometheus alerting rules.

6|2|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/amurata/cc-tools --skill slo-implementation-amurata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slo-implementation
Source: https://github.com/amurata/cc-tools/tree/main/plugins/observability-monitoring/skills/slo-implementation
Command: npx skills add https://github.com/amurata/cc-tools --skill slo-implementation-amurata

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured framework for defining, implementing, and monitoring Service Level Indicators (SLIs) and Service Level Objectives (SLOs), enabling teams to manage service reliability effectively.

Core Features & Use Cases

  • SLI/SLO Definition: Define measurable indicators and target reliability levels.
  • Error Budget Management: Calculate and track error budgets to balance reliability with development velocity.
  • Alerting: Set up alerts for SLO violations and error budget burn rates.
  • Use Case: A team can use this skill to set a 99.9% availability SLO for their API, define the SLIs that measure this availability, and configure alerts to notify them when the error budget is being consumed too quickly.

Quick Start

Use the slo-implementation skill to define an availability SLO for the API with a target of 99.9% over a 28-day window.

Frequently Asked Questions about slo-implementation

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

FAQPage Schema
How do I define SLIs and SLOs for my service reliability?

To define SLIs and SLOs for service reliability, you establish measurable indicators like availability and latency, then set target reliability levels such as a 99.9% uptime objective over a specific time window like 28 days.

What is an error budget and how do I calculate it for my SLOs?

An error budget is the allowable amount of unreliability for a service calculated from your SLO target. You calculate it by subtracting the SLO target from 100% to determine the failure tolerance for your defined time window.

How do I configure Prometheus alerts for SLO burn rates?

You configure Prometheus alerts for SLO burn rates by setting up recording and alerting rules that track error budget consumption speed, notifying the team when violations occur or budgets are being consumed too quickly.

Can I set a 99.9% availability SLO for an API over a 28-day window?

Yes, you can set a 99.9% availability SLO for an API over a 28-day window. This involves defining the specific SLIs measuring API availability and tracking compliance against the target reliability level.

What is the best way to structure SLO dashboards and review processes?

The best way to structure SLO dashboards and review processes is to follow a structured framework that includes guidance on dashboard layout and regular reliability reviews to manage service reliability effectively.

Why use error budget management to balance reliability and development velocity?

You use error budget management to balance reliability and development velocity because it provides a clear mathematical threshold for acceptable failures, allowing teams to safely push updates without compromising overall SLO compliance.