Menu

Individual skill

error-budget-policy

0upvotes

Defines and applies an SLO error-budget policy that gates feature work versus reliability work based on remaining budget. Use when setting up SLOs or when high burn rate lacks a formal team response protocol.

skills/error-budget-policy/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 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)
24
Repository last updated
Oct 13, 2026
License
MIT

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

Files and excerpt

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

Browse files
Read excerpt

# Error Budget Policy

An error budget without a policy is a number nobody acts on. The policy converts budget state into team behavior automatically, without requiring a manager decision each time.

## Define the Budget

Error budget = (1 - SLO target) x window duration.

Example: 99.9% SLO over 30 days = 0.1% x 30 days x 24 hours = 43.2 minutes of allowed downtime.

Track budget as a percentage remaining, not as raw minutes. 'Budget: 34% remaining' is actionable. 'Budget: 14.7 minutes remaining' is not.

## Four Policy States
Back to top