SLO Implementation
Turns a reliability target into a number the team can spend.
Install
/plugin marketplace add wshobson/agents; /plugin install observability-monitoring
When reliability targets are being set, error budgets defined, or alerts tied to user-facing impact.
- Author
- wshobson
- License
- MIT
Indicators come first and they are written as PromQL, not as intentions: successful requests over total, requests under a latency bucket, successful writes over attempted. The target is then chosen against what it costs — the difference between 99.9 and 99.99 percent is forty-three minutes a month versus four, and the skill puts that table in front of the decision. From there the error budget becomes a policy: how much of it remains determines whether risky changes ship this week or wait.
Similar skills
Observability & Monitoring
SkillBuilds the Prometheus, Grafana, tracing and SLO layer as one connected stack.
Performance Optimization
SkillProfile first, fix the measured bottleneck, then measure again.
Prompt Engineering Patterns
SkillTreats a production prompt as something to measure, not to reword.

Comments(0)
Sign in to comment