Sre Engineer
Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models.
Before & after
Same prompt, same agent — the only difference is the skill.
Reliability is definitely important before launch. You'll want to think about monitoring, error handling, and making sure your systems are resilient. There are lots of best practices out there for building reliable systems. Consider things like logging, alerting, and incident response procedures. You might want to look at error rates and uptime metrics. Testing is important too. Different companies approach this differently depending on their scale and goals. It's a good idea to be proactive about reliability planning.
SLO DEFINITION (production readiness gate) SERVICE TIER: Standard (99% availability) SLI METRICS: Response time p99 = 250ms, Error rate = 0.1% ERROR BUDGET: 7.2 hours downtime per quarter CAPACITY MODEL Daily traffic: 50k req/min Peak multiplier: 3x Current p99 latency headroom: 120% (buffer before breach) CPU saturation trigger: 65% (scale at 75%) MONITORING TARGETS 1. Error rate alarm (threshold: 0.5%, delay: 60s) 2. Latency alarm (p99 > 400ms, window: 5m) 3. Database connection pool (80% full) INCIDENT RESPONSE RUNBOOK Page on-call engineer -> escalate if not resolved in 15m -> post-mortem within 24h Common fixes: cache flush, connection pool drain, zone failover TOIL REDUCTION: Automate zone failover (saves 30min per incident)
About this skill
name: sre-engineer description: Use when Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for pr...
Sre Engineer
Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs/SLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning.
What you get
- Public GitHub repo
- the skills/sre-engineer folder with SKILL.md and references.
Customize your output
- Fork the repo and extend the skill's reference files for your own stack conventions.
Example output
Activates on a matching request (e.g. building or reviewing Sre Engineer code) and can chain with other skills in the pack.
Best for
Full-stack developers and engineering teams using Claude Code.
SKILL.md preview
---
name: sre-engineer
description: Use when defining SLIs/SLOs, managing error budgets, designing incident response for production systems, capacity planning, or building monitoring and automation for reliability.
version: 1.0.0
category: Development / DevOps & Infra
author: AgentVolt
license: proprietary
tags:
- development
- devops-infra
---
# Sre Engineer
Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production reliability.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Chaos Engineer
Designs controlled failure experiments — from a single fault injection to a full game day — and produces the runbook, rollback plan.
Devops Engineer
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates.
Cloud Architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP.
Monitoring Expert
Configures monitoring systems, implements structured logging pipelines, creates Prometheus/Grafana dashboards, defines alerting rules, and instruments distributed tracing.