create-service-levels

Define SLOs, SLIs, SLAs, and error budgets for a service in OpenSLO format.

11|1|Updated Jul 25, 2025

Search Tags:#observability #reliability #error budget #slo #sla #sli #openslo

Ready to run

npx skills add https://github.com/tomzx/agents --skill create-service-levels-tomzx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-service-levels
Source: https://github.com/tomzx/agents/tree/main/skills/create-service-levels
Command: npx skills add https://github.com/tomzx/agents --skill create-service-levels-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reliability targets are often judged by intuition, leaving teams without a clear definition of healthy service behavior, no signal for when to freeze feature work, and no measurable error budgets. This Skill makes reliability targets explicit and measurable by producing formal service-level definitions. ## Core Features & Use Cases - SLI/SLO/SLA Definition: Derives SLIs from critical user journeys in the architecture context, sets conservative SLO targets, and keeps SLAs looser than SLOs. - Error Budgets & Alerting: Computes error budgets per SLO and specifies burn-rate or threshold alerts with policies for budget exhaustion. - Machine-Readable Output: Writes OpenSLO-format YAML to `.sdlc/context/service-levels.yaml` alongside a human-readable markdown artifact, with revision mode for review feedback. - Use Case: Given an architecture document describing a REST API, generate a 99.9% availability SLO over a 30-day rolling window with a 0.1% error budget and a feature-freeze policy when budget drops below 25%. ## Quick Start Run the create-service-levels skill to define SLOs, SLIs, and error budgets for the services described in my architecture context.

Frequently Asked Questions about create-service-levels

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

FAQPage Schema

How do I define SLOs and SLIs for a service?▼

Start from critical user journeys in your architecture documentation, define each SLI as a ratio of good events to total events, then set a conservative SLO target per SLI. Compute the error budget as 100% minus the target and attach a policy for when it is exhausted.

What is the difference between an SLO, SLI, and SLA?▼

An SLI is the measured indicator, an SLO is the internal target you hold yourself to, and an SLA is the contractual obligation owed to customers. SLAs should be looser than SLOs so internal headroom protects the external agreement.

What format does the OpenSLO YAML output use?▼

The skill writes machine-readable definitions to .sdlc/context/service-levels.yaml in OpenSLO format, covering services, SLIs, SLOs with targets, windows, error budgets, and alert policies. SLAs have no OpenSLO kind and remain in the markdown artifact.

When should a service not have formal SLOs?▼

Internal shared libraries with no user-facing service do not need availability SLOs. Document this as out of scope and recommend alternative measurements such as test pass rate or release cadence instead.

How does error budget policy work with SLOs?▼

The error budget is 100% minus the SLO target, and the policy defines what happens when it runs out, such as freezing non-reliability feature work. An SLO without an exhaustion policy has no operational effect.