Slo Implementation

Provides a complete framework for implementing Service Level Objectives with Prometheus recording rules, multi-window burn rate alerts, and error budget tracking. You'd use this when moving from reactive monitoring to proactive reliability engineering, especially if you're establishing SRE practices or need to balance feature velocity with service reliability. The skill generates specific Prometheus queries for availability and latency SLIs, configures tiered alerting that reduces false positives, and includes Grafana dashboard structures for visualizing error budget consumption. The multi-window burn rate detection is solid and the error budget policy framework gives you concrete thresholds for development freezes.

skills.sh installs: 10.8K
GitHub stars: 42.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add wshobson/agents --skill slo-implementation --agent claude-code

Installs into .claude/skills of the current project.

Files

SLO Implementation

Framework for defining and implementing Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets.

Purpose

Implement measurable reliability targets using SLIs, SLOs, and error budgets to balance reliability with innovation velocity.

When to Use

Define service reliability targets
Measure user-perceived reliability
Implement error budgets
Create SLO-based alerts
Track reliability goals

SLI/SLO/SLA Hierarchy

SLA (Service Level Agreement)
  ↓ Contract with customers
SLO (Service Level Objective)
  ↓ Internal reliability target
SLI (Service Level Indicator)
  ↓ Actual measurement

Defining SLIs

Common SLI Types

1. Availability SLI

# Successful requests / Total requests
sum(rate(http_requests_total{status!~"5.."}[28d]))
/
sum(rate(http_requests_total[28d]))

2. Latency SLI

# Requests below latency threshold / Total requests
sum(rate(http_request_duration_seconds_bucket{le="0.5"}[28d]))
/
sum(rate(http_request_duration_seconds_count[28d]))