SLO Architect for Skills
Define service-level objectives and supporting architecture for a collection of Claude skills.
Before & after
Same prompt, same agent — the only difference is the skill.
Defining SLOs is important for reliability. You'll want to think about what uptime or latency targets make sense for your service. Typically services aim for 99.9% or 99.95% availability. You could use error budgets to decide when to focus on reliability versus shipping features. It's also good to define alerts so you know when you're at risk of missing your targets. What level of reliability does your service need? Do you have historical performance data I could use to set realistic targets?
SLO FRAMEWORK: API Infrastructure SERVICE: Authentication API (auth.example.com) OBJECTIVE 1: Availability Target: 99.95% uptime (21.6 minutes downtime/month) Error budget: 3.15 hours/month OBJECTIVE 2: Latency (p99) Target: <200ms for token generation Error budget: 3 hours/month over p99 SLO OBJECTIVE 3: Error Rate Target: <0.1% 5xx errors Error budget: 72 errors/day on 1M daily requests BURN RATE ALERTS: • Fast burn (6h window): If consuming >50% budget in 6 hours → alert ops team • Slow burn (30d window): If consuming >100% budget → freeze feature launches • Critical: If availability drops below 99% in any day → incident response ERROR BUDGET ALLOCATION (3.15 hrs/month): • Deployments: 1.5 hrs (1 deploy/week, accept brief latency spike) • Database maintenance: 1 hr (monthly patches) • Reserved: 0.65 hrs (unexpected incidents) ACTION GATES: ✓ 75% consumed this month → no risky deployments in last week ✓ 100% consumed → rollback last 2 changes, postmortem required METRICS (tracked in Prometheus/Datadog): • Availability: (success requests / total requests) × 100 • Latency p99: histogram quantile(0.99, response_time_seconds) • Error rate: rate of 5xx errors per 1-minute window
About this skill
name: skills-slo-architect description: Use when Structured Claude skill that gives Claude a repeatable workflow for skills slo architect.
Skills Slo Architect
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the Skills Slo Architect workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the skills-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 Skills 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: skills-slo-architect
description: Use this skill when defining service-level objectives and reliability architecture for a set of Claude skills or agent-driven services.
version: 1.0.0
category: AI Agents / Development
author: AgentVolt
license: proprietary
tags:
- ai-agents
- development
---
# Skills Slo Architect
Gives a repeatable workflow for defining service-level objectives (SLOs) and the supporting architecture for a collection of Claude skills, so reliability targets are explicit rather than assumed.
## 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.