Skip to content
ai101.tools
navigateopenescclose
Claude+372Whisper+228LangChain+168Codex+223NotebookLM+276DALL-E 3+192DeepL+249n8n+208Topaz Video AI+153LlamaIndex+161
SLO Implementation logo
Skill

SLO Implementation

Turns a reliability target into a number the team can spend.

0
SaveVisit website ↗

Install

/plugin marketplace add wshobson/agents; /plugin install observability-monitoring
Triggers on

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.

Comments(0)

Sign in to comment

No comments yet — be the first.

Similar skills

Report this comment

Why are you reporting this?