SRE Engineer
Guides SLOs, error budgets, monitoring, incident response, chaos tests and toil automation for production systems
- Repository
- Jeffallan/claude-skills
- Stars
- 12,176
- Licence
- MIT
- Files
- 6 files
What it does
Once installed, the agent approaches reliability work the way a site reliability engineer would: it helps define measurable service level objectives (SLOs) and the indicators behind them, calculates how much failure a target allows (an error budget), and proposes policies such as freezing risky releases when the budget runs out. It can also draft monitoring and alerting configurations (for example Prometheus rules and PromQL queries), incident and blameless postmortem procedures, chaos experiments, and small automation scripts that reduce repetitive operational work. The skill ships reference guides that the agent loads for each topic.
Great for
- Engineers or SRE teams setting reliability targets for a production service
- On-call or platform teams who want alerting rules and runbook drafts reviewed against burn-rate patterns
- Teams planning chaos experiments or reducing repetitive operational toil
Skip it if
- Non-technical users with no production systems: the output assumes Prometheus, Kubernetes and similar tooling, so it adds little value outside that context
- Running the sample auto-remediation script against live clusters without review: it restarts Kubernetes deployments via kubectl and queries an internal Prometheus address, so a wrong threshold or target could cause unplanned restarts
- Replacing a real incident process or legal/compliance-grade reliability commitments: the guidance is generic and must be checked against your own systems
Try asking
- “Define SLOs and an error budget policy for my checkout API, based on our request logs”
- “Write Prometheus multiwindow burn-rate alerts for my service and draft the matching runbook”
- “Design a chaos experiment to verify our database failover meets our RTO and RPO targets”
- “Help me find toil in our on-call week and propose automation for the top three tasks”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 6 original files, the MIT licence and an attribution note.
sre-engineer.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip sre-engineer.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip sre-engineer.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Give the agent real service data such as request counts, error rates and incident history so SLO targets and budgets are grounded in your numbers rather than examples.
- Review every generated alert, runbook and script before deploying; the example thresholds (such as 5% errors, 99.9% availability) are illustrations, not recommendations.
- Keep the script's targets and namespaces in a staging environment first, and ask the agent to add dry-run or confirmation steps before any restart or change.
What's inside
- references/automation-toil.md
- references/error-budget-policy.md
- references/incident-chaos.md
- references/monitoring-alerting.md
- references/slo-sli-management.md
- SKILL.md
Redistributed unmodified from Jeffallan/claude-skills under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.