SLO Design
Design service level objectives and reliability targets for a system, with validation so targets hold up across teams.
Before & after
Same prompt, same agent — the only difference is the skill.
Reliability is important. You'll want to think about what acceptable downtime looks like for your service. Different services have different requirements depending on their criticality. You might measure things like uptime percentage or response time. Setting targets is helpful for your team. You could look at what industry standards are. Think about the impact of outages on your business. It's worth discussing with your team what matters most. There are various metrics you could track.
SLO DESIGN FRAMEWORK STEP 1: Classify your service (by customer impact) TIER 1 - Critical (revenue-blocking): 99.95% SLA required TIER 2 - Important (features): 99.5% SLA required TIER 3 - Nice-to-have (admin): 99% SLA required Your service: TIER 2 (booking calendar, non-revenue-blocking but core feature) STEP 2: Define SLI (what you'll measure) For booking calendar: SLI 1: Availability = Successful requests / Total requests (target: 99.5%) SLI 2: Latency = Response time p99 < 500ms (target: 95% of requests) STEP 3: Translate to SLO (what you promise) SLO: Maintain 99.5% availability + p99 latency under 500ms, measured monthly Error budget: 0.5% × 43,200 minutes/month = 216 minutes (3.6 hours) downtime allowed STEP 4: Allocate error budget across causes Infrastructure outages: 120 min budget Deployment failures: 60 min budget Data corruption/rollback: 20 min budget Wildcard/unplanned: 16 min budget STEP 5: Monitoring gates Alert at 80% error budget consumed (in-month) Freeze deployments at 90% consumed Post-mortem required for any breach STEP 6: Fallback behavior If calendar booking fails, show cached 24-hr history → graceful degradation, not failure REVISION CADENCE: Quarterly review; adjust if error budget consistently unused (loosen SLO) or breached (tighten/invest)
About this skill
name: slo-design description: Use when Structured Claude skill that gives Claude a repeatable workflow for slo design.
Slo Design
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the Slo Design workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the slo-design 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 Design; 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-design
description: Use when a team needs a repeatable workflow for designing service level objectives and related reliability targets for a system.
version: 1.0.0
category: AI Agents / Development
author: AgentVolt
license: proprietary
tags:
- ai-agents
- development
---
# Slo Design
Runs a repeatable workflow for designing service level objectives (SLOs), packaging the process with its own instructions and validation so outputs stay consistent across teams and services.
## When to use
… (sign up to view the full skill)More ai & agents skills
View all AI & Agents skills →Skill Status Report
Scan every skill in a project and report which pass validation, which are stale, and which lack required metadata.
Skills Scaffolder
Scaffold a new skills directory — folder structure, metadata, a baseline validation pass — with the right conventions from day one.
Research Bundle
Run a multi-step research task as one pipeline: gather sources, extract findings, validate consistency, emit one structured bundle.
Workspace Admin
Administer a Cowork or Claude workspace — settings, access, configuration — with every change scoped and verified.