Individual skill
slo-architect
Use when defining or reviewing SLOs, SLIs, error budgets or burn-rate alerts. Designs SLOs with slo_designer.py, computes budgets and multi-window burn-rate thresholds with error_budget_calculator.py and catches common SLO bugs with slo_review.py.
engineering/slo-architect/skills/slo-architect/SKILL.md
Source commit 9ef0c3c213932e645cc5cbeeb3c35c3a762a2437
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)
- 29,505
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-ai Repository topic
- anthropic-claude Repository topic
- claude-ai Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- claude-code-skills Repository topic
- ai-coding-agent Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- openai-codex Repository topic
- slo Declared skill tag
- sli Declared skill tag
- sla Declared skill tag
- error-budget Declared skill tag
- burn-rate Declared skill tag
- sre Declared skill tag
- reliability Declared skill tag
- google-sre-workbook Declared skill tag
- observability Declared skill tag
- 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 · 10,702 bytesSKILL.mdcore · 10,702 bytesSKILL.mdcore · 10,702 bytesSKILL.mdcore · 10,702 bytesSKILL.mdcore · 10,702 bytesSKILL.mdcore · 10,702 bytesSKILL.mdcore · 10,702 bytesSKILL.mdcore · 10,702 bytesassets/error_budget_policy.mddoc · 2,641 bytesassets/slo_template.yamlasset · 2,293 bytesreferences/composition.mddoc · 5,312 bytesreferences/error_budget.mddoc · 5,281 bytesreferences/sli_design.mddoc · 5,451 bytesreferences/slo_principles.mddoc · 5,333 bytesscripts/error_budget_calculator.pyruns · 5,609 bytesscripts/slo_designer.pyruns · 6,680 bytesscripts/slo_review.pyruns · 5,678 bytes
Read excerpt
# SLO Architect
Define SLOs that mean something. Most "SLOs" in the wild are arbitrary numbers no one believes — 99.9% on every endpoint, no SLI definition, no error budget, no policy for what happens when budget burns. This skill enforces the discipline from Google's SRE Workbook: pick the right SLI, set a target users actually care about, calculate the error budget, wire multi-window burn-rate alerts, and have a written policy for when budget runs out.
## When to use
- Defining a new SLO for a service or feature
- Reviewing existing SLOs for common bugs
- Picking the right SLI (event-based vs time-window based vs request-based)
- Computing error budgets and burn-rate alert thresholds
- Tying SLOs to existing controls — feature flags abort, chaos blast radius, operator capability levels
## When NOT to use
