$ skilldirectory
— zsh — registry.skilldirectory.dev
skill library blog

home / DevOps / Slo Architect Skill by @alirezarezvani

Slo Architect Skill by @alirezarezvani

FREE
github stars★ 29,369updatedOct 2026repo@alirezarezvani
$git clone https://github.com/alirezarezvani/claude-skills

The skill is the engineering/skills/slo-architect folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.

Read the opening of the original SKILL.md
# 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
…

Excerpt only, quoted from the author's repository. Open the repository for the complete file.