SLO implementation: SLIs, error budgets and SLO-based alerting
Define measurable reliability targets — availability/latency/durability SLIs in PromQL, SLO targets, error budget calculation and burn-rate alerting
- What
- Define measurable reliability targets — availability/latency/durability SLIs in PromQL, SLO targets, error budget calculation and burn-rate alerting
- Cost
- Free
- Needs
- a metrics backend (Prometheus-style) where the SLI queries can run; a service whose reliability you want to target; nothing else — the skill is a methodology plus PromQL patterns, no accounts or keys required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @wshobson's SRE framework for defining and implementing Service Level Indicators, Service Level Objectives and error budgets: the SLI/SLO/SLA hierarchy, ready-to-adapt PromQL SLI definitions (availability, latency with histogram buckets, durability), an SLO target table with allowed downtime (99% → 99.99%), example YAML SLO configs with 28-day windows, error-budget calculation, and burn-rate-based alerting guidance — with decision notes on choosing appropriate targets from user expectations, business requirements and current performance. By @wshobson, listed here with credit to its creator. Honest caveats: methodology plus PromQL patterns — metric names and labels must be adapted to your stack; it assumes a metrics backend (Prometheus-style) to measure against; does not include the companion observability-monitoring skills; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
SLO Implementation is a free Muse skill that defines measurable reliability targets, with availability, latency and durability SLIs in PromQL, SLO targets, error budget calculation and burn-rate alerting. It covers the SLI, SLO and SLA hierarchy, ready-to-adapt PromQL definitions, an SLO target table with allowed downtime, and example YAML configurations.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 46891e7Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a metrics backend (Prometheus-style) where the SLI queries can run; a service whose reliability you want to target; nothing else — the skill is a methodology plus PromQL patterns, no accounts or keys required Install "SLO implementation: SLIs, error budgets and SLO-based alerting" for me. It gives the agent @wshobson's SRE framework: the SLI/SLO/SLA hierarchy, PromQL SLI definitions (availability, latency, durability) to adapt to your stack, an SLO target/downtime table, example YAML SLO configs, error-budget calculation, and burn-rate alerting guidance — with decision notes on choosing targets. MIT-licensed. Repository: https://raw.githubusercontent.com/wshobson/agents/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/observability-monitoring/skills/slo-implementation/SKILL.md Pinned version: install the code at commit 46891e7e60da0e52baf1050b7b6391b64e84c6d9 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "slo-implementation". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. adapt the PromQL SLI queries to your metric names/labels; define SLO targets with the stakeholders). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 46891e7 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: files.pythonhosted.org, pypi.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.