Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.
Install with Tessl CLI
npx tessl i github:Dicklesworthstone/pi_agent_rust --skill slo-implementation89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
SLO Recording Rules
Availability SLI name
87%
100%
Latency SLI name
85%
100%
SLI group interval
0%
100%
SLO group interval
0%
100%
Availability SLI formula
100%
100%
Latency SLI formula
0%
100%
28-day window
0%
100%
Error budget remaining formula
50%
100%
Burn rate formula
100%
100%
SLO compliance bool
100%
100%
SLO metric prefix
100%
100%
Without context: $0.3351 · 7m 46s · 10 turns · 81 in / 6,731 out tokens
With context: $0.3226 · 10m 28s · 14 turns · 336 in / 3,947 out tokens
Burn Rate Alerting
Fast burn threshold
0%
100%
Fast burn dual-window
100%
100%
Fast burn `for` duration
0%
100%
Fast burn severity
100%
100%
Slow burn threshold
0%
100%
Slow burn dual-window
100%
100%
Slow burn `for` duration
0%
100%
Slow burn severity
100%
100%
Error budget exhausted expr
75%
100%
Error budget exhausted `for`
0%
100%
Error budget exhausted severity
100%
100%
Alert group interval
0%
0%
Without context: $0.2061 · 9m 22s · 10 turns · 72 in / 3,083 out tokens
With context: $0.3397 · 10m 34s · 15 turns · 393 in / 3,633 out tokens
Error Budget Policy
Error budget formula
100%
100%
Policy tier: 100%
100%
100%
Policy tier: 50%
87%
100%
Policy tier: 10%
87%
0%
Policy tier: 0%
100%
100%
SLO YAML fields
100%
100%
28-day window
0%
100%
Sub-100% targets
100%
100%
Multiple SLI types
100%
100%
Review cadence
100%
100%
Error budget status
100%
100%
Without context: $0.3975 · 12m 9s · 13 turns · 89 in / 8,190 out tokens
With context: $0.9310 · 16m 10s · 24 turns · 163 in / 14,332 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.