Agent skill · product strategy · aiskillstore
slo-implementation
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.
Why this skill is useful
Provides specific Prometheus recording rules and SLO definitions that the AI wouldn't reliably generate on its own.
What it needs
Requires prometheus installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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 Defining SLIs Common SLI Types 1. Availability SLI 2. Latency SLI 3. Durability SLI Reference: See references/slo-definitions.md Setting SLO Targets Availability SLO Examples SLO % Downtime/Month Downtime/Year ------- ---------------- --------------- 99% 7.2 hours 3.65 days 99.9% 43.2 minutes 8.76 hours 99.95% 21.6 minutes 4.38 hours 99.99% 4.32 minutes 52.56 minutes Choose Appropriate SLOs Consider: User expectations Business requirements Current performance Cost of reliability Competitor benchmarks Example SLOs: Error Budget Calculation Error Budget Formula Example: SLO: 99.9% availability Error Budget: 0.1% = 43.2 minutes/month Current Error: 0.05% = 21.6 minutes/month Remaining Budget: 50% Error Budget Policy Reference: See references/error-budget.md SLO Implementation Prometheus Recording Rules SLO Alerting Rules SLO Dashboard Grafana Dashboard Structure: Example Queries: Multi-Window Burn Rate Alerts SLO Review Process Weekly Review Current SLO compliance Error budget status Trend analysis Incident impact Monthly Review SLO achievement Error budget usage Incident postmortems SLO adjustments Quarterly Review SLO relevance Target adjustments Process improvements Tooling enhancements Best Practices 1. Start with user-facing services 2. Use multiple SLIs (availability, latency, etc.) 3. Set achievable SLOs (don't aim for 100%) 4. Implement multi-window alerts to reduce noise 5. Track error budget consistently 6. Review SLOs regularly 7. Document SLO decisions 8. Align with business goals 9. Automate SLO reporting 10. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/slo-implementation--49e21c