Agent skill · operations · aiskillstore
operating-production-services
SRE patterns for production service reliability: SLOs, error budgets, postmortems, and incident response. Use when defining reliability targets, writing postmortems, implementing SLO alerting, or establishing on-call practices. NOT for initial service development (use scaffolding skills instead).
Why this skill is useful
Provides specific SRE patterns and templates for incident response and reliability management that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Operating Production Services Production reliability patterns: measure what matters, learn from failures, improve systematically. Quick Reference Need Go To ------ ------- Define reliability targets SLOs & Error Budgets Write incident report Postmortem Templates Set up SLO alerting references/slo-alerting.md --- SLOs & Error Budgets The Hierarchy Common SLIs SLO Targets Reality Check SLO % Downtime/Month Downtime/Year ------- ---------------- --------------- 99% 7.2 hours 3.65 days 99.9% 43 minutes 8.76 hours 99.95% 22 minutes 4.38 hours 99.99% 4.3 minutes 52 minutes Don't aim for 100%. Each nine costs exponentially more. Error Budget Example: 99.9% SLO = 0.1% error budget = 43 minutes/month Policy: Budget Remaining Action ------------------ -------- > 50% Normal velocity 10-50% Postpone risky changes < 10% Freeze non-critical changes 0% Feature freeze, fix reliability See references/slo-alerting.md for Prometheus recording rules and multi-window burn rate alerts. --- Postmortem Templates The Blameless Principle Blame-Focused Blameless --------------- ----------- "Who caused this?" "What conditions allowed this?" Punish individuals Improve systems Hide information Share learnings When to Write Postmortems SEV1/SEV2 incidents Customer-facing outages > 15 minutes Data loss or security incidents Near-misses that could have been severe Novel failure modes Standard Template Quick Template (Minor Incidents) --- Postmortem Meeting Guide Structure (60 min) 1. Opening (5 min) - Remind: "We're here to learn, not blame" 2. Timeline (15 min) - Walk through events chronologically 3. Analysis (20 min) - What failed? Why? What allowed it? 4. Action Items (15 min) - Prioritize, assign owners, set dates 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/operating-production-services