slo-implementation SKILL.md skillA
slo-implementation from wshobson/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wshobson/agents/slo-implementation@git:20260929.156b7a5Pins git:20260929.156b7a5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wshobson/agents
- Path
plugins/observability-monitoring/skills/slo-implementation/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260929.156b7a5, committed Sep 29, 2026
- First version recorded
- Oct 17, 2025
- Size
- 7,163 bytes
- Repository stars
- 42,320
- License
- MIT
Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# SLO Implementation
Framework for defining and implementing Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets.
## Purpose
Implement measurable reliability targets using SLIs, SLOs, and error budgets to balance reliability with innovation velocity.
## When to Use
- Define service reliability targets
- Measure user-perceived reliability
- Implement error budgets
- Create SLO-based alerts
- Track reliability goals
## SLI/SLO/SLA Hierarchy
```
SLA (Service Level Agreement)
↓ Contract with customers
SLO (Service Level Objective)
↓ Internal reliability target
SLI (Service Level Indicator)
↓ Actual measurement
```
## Defining SLIs
### Common SLI Types
#### 1. Availability SLI
```promql
# Successful requests / Total requests
sum(rate(http_requests_total{status!~"5.."}[28d]))
/
sum(rate(http_requests_total[28d]))
```
#### 2. Latency SLI
```promql
# Requests below latency threshold / Total requests
sum(rate(http_request_duration_seconds_bucket{le="0.5"}[28d]))
/
sum(rate(http_request_duration_seconds_count[28d]))
```
#### 3. Durability SLI
```
# Successful writes / Total writes
sum(storage_writes_successful_total)
/
…Read the whole file at its exact version.
How to install
mdr add wshobson/agents/slo-implementation@sha256:538e560a1c10be5fThe line at the top of this page pins the label git:20260929.156b7a5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_op3tkukj7d2oluxe)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 17, 2025 and Sep 29, 2026, about one every 87 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260929.156b7a5 latest | 2026-09-29 | 156b7a5 | 7,163 B | A | view · diff |
| git:20260522.be57c0b | 2026-05-22 | be57c0b | 7,264 B | A | view · diff |
| git:20260307.47a5dbc | 2026-03-07 | 47a5dbc | 8,421 B | A | view · diff |
| git:20260119.5684887 | 2026-01-19 | 5684887 | 8,613 B | A | view · diff |
| git:20251017.65e5cb0 | 2025-10-17 | 65e5cb0 | 8,598 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7163 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wshobson/agents · 42,320 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_op3tkukj7d2oluxe GET https://markdownregistry.com/api/v1/resolve?ref=wshobson/agents/slo-implementation GET https://markdownregistry.com/api/v1/blob/538e560a1c10be5f643d0a048e4e828605420e9b1867a9d4449f8a3471c14049
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.