SLO Architect
Use when defining, reviewing, or operating SLOs/SLIs/error budgets.
Before & after
Same prompt, same agent — the only difference is the skill.
Service level objectives help you define reliability targets for your systems. You typically set a percentage uptime or availability goal. Common targets are 99.9percent or 99.95percent availability. You'd also want to think about different types of failures - some might be more critical than others. Error budgets can help you decide when it's safe to take risks like major refactors or deploy without waiting. You'd need to define what actually counts as a success or failure for your service. Monitoring and alerting are important to track whether you're meeting your targets.
SLO DEFINITION FOR PAYMENT PROCESSING: SLI METRIC DEFINITION (Service Level Indicator) Measurement: Successful payment transactions / Total payment attempts Calculation: count(payment.status = 'settled') / count(payment.status IN 'attempted', 'settled', 'failed') Exclusions: Test transactions (env='test'), Manually refunded (category='refund') Window: 30-day calendar month SLO TARGET: 99.5percent - Equals 3.6 hours downtime/month - Rationale: Payment is critical path; 99.9percent (43 min/month) overly stringent for infrastructure variance ERROR BUDGET ALLOCATION (43.2 minutes/month available) Planned maintenance: 15 minutes (database backup window 2am-2:15am weekdays) Infrastructure incidents: 20 minutes (DNS failover, load balancer reboot contingency) Deployment risk: 8.2 minutes (reserved for emergency rollbacks) Burn rate thresholds: • >14.4 min/week = YELLOW (stop non-critical changes, page team) • >7.2 min/week = RED (halt all deploys, incident response) MULTI-WINDOW BURN RATE ALERTS 1-hour window: if error rate 10X baseline → page on-call 6-hour window: if error rate 5X baseline → alert team lead 24-hour window: if budget burn >20percent monthly → meeting required SLO REVIEW MONTHLY Track: Were SLI targets met? What caused misses? Adjust: Next month's error budget spend based on learnings Communicate: Share brief 'how we did' report with stakeholders
About this skill
name: slo-architect description: Use when Use when defining, reviewing, or operating SLOs/SLIs/error budgets.
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-engineering/kubernetes-operator. NOT a generic observability skill — specifically the SLO discipline.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the slo-architect skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Slo Architect; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: slo-architect
description: Define, review, and operate service level objectives, SLIs, and error budgets, including multi-window burn-rate alerting.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Slo Architect
Define, review, and operate service level objectives, SLIs, and error budgets, including multi-window burn-rate alerting.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.