slo-error-budget
Define Service Level Objectives (SLOs) and an error budget policy for a service. Use when asked to write SLOs, define SLIs, calculate an error budget, set reliability targets, or create an error budget policy. Produces a complete SLO document with SLI definitions, target calculation, error budget policy, burn rate alerts, and review cadence.
npx skills add mohitagw15856/pm-claude-skills --skill slo-error-budget --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 and Error Budget Skill Produce a complete, implementable SLO document for a service — covering what to measure, what target to set, how to calculate the error budget, and what to do when it burns. A good SLO is not a target to hit. It is an agreement about what reliability means for your users — and a framework for making principled trade-offs between reliability and velocity. ## Required Inputs Ask for these if not already provided: - **Service name** and brief description of what it does - **Primary users** — who depends on this service and how - **User-facing interactions** to protect — e.g. API calls, page loads, transactions - **Current reliability data** — error rate, latency, uptime (last 30–90 days if available) - **Existing on-call setup** — who responds to alerts? - **Deployment frequency** — how often does the team ship? - **Any existing SLAs** with customers — these constrain SLO targets ## Key Definitions Always establish these before writing the SLO: | Term | Definition | |---|---| | **SLI** (Service Level Indicator) | The metric being measured — e.g. "% of requests completing successfully in <500ms" | | **SLO** (Service Level Objective) | The target for that me
- Required Inputs
- Key Definitions
- Output Format
- Why This SLO Exists
- Service Overview
- SLIs — What We Measure
- SLI 1: [Name — e.g. Request Success Rate]
- SLI 2: [Name — e.g. Latency]
- SLI 3: [Name — e.g. Data Freshness / Queue Depth / etc.]
- SLO Targets
- Error Budget Calculation
- Burn Rate Alerts
- Error Budget Policy
- When budget is healthy (>50% remaining)
What does the slo-error-budget skill do?
Define Service Level Objectives (SLOs) and an error budget policy for a service. Use when asked to write SLOs, define SLIs, calculate an error budget, set reliability targets, or create an error budget policy. Produces a complete SLO document with SLI definitions, target calculation, error budget policy, burn rate alerts, and review cadence.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill slo-error-budget --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 mohitagw15856/pm-claude-skills, a repository with 1,255 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.