slo-architect
Use when defining, reviewing, or operating SLOs/SLIs/error budgets. Triggers on "define an SLO", "what should our SLO be", "error budget", "burn rate", "SLI", "service level objective", "Google SRE workbook", "multi-window burn-rate alert", or any reliability-target question. Ships SLO designer, error-budget calculator with multi-window burn-rate thresholds, and SLO reviewer that catches the common bugs (target too aggressive, window too short, conflicting SLOs, no SLI definition). 4 references on SLO principles + SLI design + error budget math + composition with feature-flags-architect/chaos-
Profile →npx skills add alirezarezvani/claude-skills --skill slo-architect --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 - General observability strategy (metrics + logs + traces) → use `observability-designer` - Customer-facing SLAs with legal teeth → that's contract drafting, not engineering - Performance load testing (capacity, not reliability) → use `performance-profiler` - Active incident response → use `incident-response` ## Core principle: an SLO is a promise about user experience ``` SLI ⟶
- When to use
- When NOT to use
- Core principle: an SLO is a promise about user experience
- Quick start
- The 3 Python tools
- slodesigner.py
- errorbudgetcalculator.py
- sloreview.py
- SLI selection cheatsheet
- Error budget math (the basics)
- Composition with the rest of the portfolio
- Workflows
- Workflow 1: Define a new SLO
- Workflow 2: Quarterly SLO review
python "$SKILL/scripts/slo_designer.py" \ python "$SKILL/scripts/error_budget_calculator.py" \ python "$SKILL/scripts/slo_review.py" --slo-doc docs/slos/ python scripts/slo_designer.py \ python scripts/error_budget_calculator.py --target 99.9 --window-days 30 python scripts/error_budget_calculator.py --target 99.95 --window-days 7 --format json python scripts/slo_review.py --slo-doc docs/slos/
What does the slo-architect skill do?
Use when defining, reviewing, or operating SLOs/SLIs/error budgets. Triggers on "define an SLO", "what should our SLO be", "error budget", "burn rate", "SLI", "service level objective", "Google SRE workbook", "multi-window burn-rate alert", or any reliability-target question. Ships SLO designer, error-budget calculator with multi-window burn-rate thresholds, and SLO reviewer that catches the common bugs (target too aggressive, window too short, conflicting SLOs, no SLI definition). 4 references on SLO principles + SLI design + error budget math + composition with feature-flags-architect/chaos-
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill slo-architect --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.