Skip to content

SLO Implementation

Define SLIs, SLOs, error budgets and burn-rate alerts for a service's reliability targets.

Repository
wshobson/agents
Stars
42,095
Licence
MIT
Files
2 files

What it does

Once installed, the agent can help a team set measurable reliability goals for a service: choosing indicators such as availability, latency and durability, picking a target like 99.9%, and calculating how much downtime or error budget that allows. It can also write Prometheus recording rules, burn-rate alert rules and a dashboard layout so the team is warned when reliability is slipping. The skill is a guide and template library; it does not monitor anything by itself.

Great for

  • SRE or platform engineers introducing error budgets and SLO-based alerting
  • Developers who run services on Prometheus and want starter PromQL and alert rules
  • Teams that need a shared explanation of SLI, SLO and SLA for non-specialist stakeholders

Skip it if

  • Teams not using Prometheus or a compatible metrics system, since the examples are PromQL-specific and would need rewriting
  • Copying the example targets (99.9%, 28-day window, 14.4x burn threshold) without checking them against real user expectations and traffic, which can produce misleading alerts
  • Legal or contractual SLAs, which need review by the business and legal teams rather than a generated template

Try asking

  • “Help me define availability and latency SLIs for our checkout API and turn them into Prometheus recording rules”
  • “Create multi-window burn-rate alerts for a 99.9% availability SLO”
  • “Calculate our monthly error budget in minutes and suggest an error budget policy for the team”
  • “Draft a Grafana dashboard layout that shows SLO compliance and remaining error budget”
Step-by-step guide: how to use SLO ImplementationInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the MIT licence and an attribution note.

    slo-implementation.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip slo-implementation.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip slo-implementation.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give the agent your real metric names and labels so it adapts the PromQL instead of using the generic http_requests_total examples
  • Treat the example SLO targets and burn-rate thresholds as starting points and validate them against your own traffic before paging anyone
  • Ask the agent to review the generated rules with promtool or a test environment before deploying them to production

What's inside

  • references/details.md
  • SKILL.md

Redistributed unmodified from wshobson/agents under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.