Individual skill

slo-error-budget

Define Service Level Objectives (SLOs) and an error budget policy for a service. Use when asked to write SLOs, define SLIs, calculate an error budget, set reliability targets, or create an error budget policy. Produces a complete SLO document with SLI definitions, target calculation, error budget policy, burn rate alerts, and review cadence.

skills/slo-error-budget/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,540
Repository last updated: Nov 10, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

product-management Repository topic
productivity Repository topic
skills Repository topic
claude-skills Repository topic
agent-skills Repository topic
chatgpt Repository topic
claude-code Repository topic
cursor Repository topic
gemini Repository topic
prompt-engineering Repository topic
finance Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 12,272 bytes

Read excerpt


# SLO and Error Budget Skill

Produce a complete, implementable SLO document for a service — covering what to measure, what target to set, how to calculate the error budget, and what to do when it burns.

A good SLO is not a target to hit. It is an agreement about what reliability means for your users — and a framework for making principled trade-offs between reliability and velocity.

## Where this sits — the frame of the spine

This is the governor of the incident-response spine: **`slo-error-budget` (frame) →
`/debugging-log-analyser` → `/incident-postmortem` → `/oncall-runbook`**. It sets the
**error budget** the whole loop runs inside — the objective forcing function that later
decides whether a postmortem's action items get done now (budget spent) or deferred
(budget healthy). Shared terms (SLO, error budget, incident, action item) are defined
once in [`docs/craft/incident-response.md`](../../docs/craft/incident-response.md).