Our review

This skill helps design SLO frameworks, define SLIs, and build monitoring systems that use error budgets to balance reliability with feature delivery velocity.

Strengths

Clear structure to align reliability targets with business priorities
Practical approach with dedicated resources (implementation playbook)
Data-driven decision-making for reliability vs. features trade-offs

Limitations

Requires access to service telemetry and metrics
Stakeholder alignment is critical and can be challenging
Not suitable for basic monitoring without reliability targets

When to use it

Use this skill when you need to define SLIs/SLOs and error budgets, build SLO dashboards, and standardize reliability practices across teams.

When not to use it

Do not use this skill if you only need basic monitoring without reliability targets or if there is no access to service telemetry.

Examples

Define SLOs for a payment service

I need to implement SLOs for our payment processing service. Define appropriate SLIs, set realistic SLO targets, and create an error budget policy that balances reliability with feature velocity.

Create SLO dashboard and alerting

Design an SLO dashboard and alerting workflow for our microservices. Include burn rate alerts and error budget tracking. Our services are monitored with Prometheus and Grafana.

Standardize SLO practices across teams

Help me standardize SLO practices across our platform team. We need a framework for defining SLIs, setting SLOs, and reporting on error budgets. Provide examples for different service tiers (critical, important, best-effort).

name: observability-monitoring-slo-implement description: "You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that balances reliability with delivery velocity."

SLO Implementation Guide

You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based engineering practices. Design comprehensive SLO frameworks, establish meaningful SLIs, and create monitoring systems that balance reliability with feature velocity.

Use this skill when

Defining SLIs/SLOs and error budgets for services
Building SLO dashboards, alerts, or reporting workflows
Aligning reliability targets with business priorities
Standardizing reliability practices across teams

Do not use this skill when

You only need basic monitoring without reliability targets
There is no access to service telemetry or metrics
The task is unrelated to service reliability

Context

The user needs to implement SLOs to establish reliability targets, measure service performance, and make data-driven decisions about reliability vs. feature development. Focus on practical SLO implementation that aligns with business objectives.

Requirements

$ARGUMENTS

Instructions

Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.

Safety

Avoid setting SLOs without stakeholder alignment and data validation.
Do not alert on metrics that include sensitive or personal data.

Resources

resources/implementation-playbook.md for detailed patterns and examples.

SLO Implementation & Observability

Recommended for