domains / families / devops / slo-implementation

slo-implementation

combined

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. Framework for defining and implementing Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets.

When to use

• Implement measurable reliability targets using SLIs, SLOs, and error budgets to balance reliability with innovation velocity.
• Define service reliability targets
• Measure user-perceived reliability
• Implement error budgets
• Create SLO-based alerts
• Track reliability goals

When not to use

• The task is unrelated to slo implementation
• You need a different domain or tool outside this scope
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies share the same core SLO/SLI/error-budget framework, but the sickn33 copy adds material constraints and steps the rmyndharis copy lacks: a caveat that downtime tables assume time-based SLIs, explicit additional burn-rate recording rules (1h, 6h, 30m) required before the alert examples, and edge-case handling for zero burn and missing telemetry. The rmyndharis copy is a cleaner, self-contained procedure but omits those operational details. Crowning one would hide a real alternative with stricter operational guidance.