sla-slo-sli-design

Define SLIs, SLOs, and error budgets for service reliability targets.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/marquesfelip/agents-and-skills --skill sla-slo-sli-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sla-slo-sli-design
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/sla-slo-sli-design
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill sla-slo-sli-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define and govern reliability targets by specifying SLIs, SLOs, and error budgets for services to align engineering efforts with business expectations.

Core Features & Use Cases

  • Define SLIs, SLOs, and SLAs to establish clear reliability promises and measurement.
  • Instrument and track reliability metrics across systems using Prometheus, Grafana, or Datadog.
  • Manage error budgets and implement governance policies to guide deployment decisions during budget burn.
  • Conduct monthly reviews to calibrate SLOs to evolving user needs and business priorities.

Quick Start

Configure your first SLI/SLO dashboard and define an initial SLO in your monitoring system.

Frequently Asked Questions about sla-slo-sli-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define SLIs and SLOs for a service?

Error budgets track the remaining tolerance for failures after setting an SLO. You manage them by implementing governance policies that guide deployment decisions, automatically pausing releases when budget burn rates exceed defined thresholds.

Can I use Prometheus queries for SLO monitoring and alerting?

Yes, Prometheus is supported for SLO monitoring. The approach requires Prometheus-compatible queries to instrument and track reliability metrics, feeding data into dashboards for alerting and governance across customer-facing SaaS and internal tools.

What metrics should I track for service reliability targets?

You should track availability, latency, and throughput as core metrics for service reliability targets. These measurable SLI signals are evaluated over rolling 28-day windows to ensure systems meet defined SLOs and governance policies.

When do I need to calibrate SLOs for evolving user needs?

You need to calibrate SLOs during monthly reviews to align with evolving user needs and business priorities. This regular governance process ensures reliability targets remain accurate as customer-facing SaaS demands change over time.

Does this approach work for both internal tools and customer-facing SaaS?

Yes, this SLO design approach works across both customer-facing SaaS and internal tools. It applies standardized SLI measurements, error budget policies, and governance workflows uniformly to match distinct reliability requirements of each environment.