SLO implementation: SLIs, error budgets and SLO-based alerting

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://github.com/wshobson/agents/blob/main/plugins/observability-monitoring/skills/slo-implementation/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.