Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dicklesworthstone/slo-implementation
Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting.
Passed 18 of 25 test cases with the skill, and 16 of 25 without it.
and 2 more in the full report
4 fixed14 passed either way5 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are writing Prometheus recording rules for our HTTP availability metrics. What standard metric prefix format should we use for the raw SLI ratio metric versus the SLO compliance metric?
| Checked | Without skill | With skill |
|---|---|---|
| Names the SLI ratio metric with prefix sli:http_availability:ratio. | Missed | Passed |
| Names the compliance metric with prefix slo:http_availability:compliance. | Missed | Passed |
The instructions your model reads when the skill loads.
Framework for defining and implementing Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets.
Implement measurable reliability targets using SLIs, SLOs, and error budgets to balance reliability with innovation velocity.
SLA (Service Level Agreement)
↓ Contract with customers
SLO (Service Level Objective)
↓ Internal reliability target
SLI (Service Level Indicator)
↓ Actual measurement
# Successful requests / Total requests
sum(rate(http_requests_total{status!~"5.."}[28d]))
/
sum(rate(http_requests_total[28d]))
test cases passed, vs 16 / 25 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.