Back to Skills

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.

9,341stars795forksUpdated 5/26/2026

Security Assessment

Medium Risk(60/100)

Detected risks:

Command Injection([references/incident-chaos.md] subprocess.run, [references/automation-toil.md] subprocess.run, [references/automation-toil.md] subprocess.Call)
Security Score60/100

About sre-engineer

The sre-engineer skill provides structured guidance and implementation support for building and operating reliable production systems at scale. It focuses on defining service level indicators (SLIs) and service level objectives (SLOs), calculating and enforcing error budgets, designing monitoring and alerting strategies, and improving operational resilience through automation and incident management practices. The skill is intended to help teams establish measurable reliability goals, reduce operational risk, and ensure that production systems can maintain availability and recover effectively from failures.

Core capabilities include defining quantitative SLO targets, calculating error budgets, implementing monitoring for golden signals such as latency, traffic, errors, and saturation, and creating operational automation to reduce toil. The skill also supports incident response planning, blameless postmortem practices, chaos engineering experiments, and capacity planning workflows. It provides implementation-oriented outputs such as Prometheus alerting configurations, automation scripts in languages like Python, Go, or Terraform, runbooks with remediation steps, and guidance for balancing reliability goals with feature delivery velocity. The workflow emphasizes verification of user-impact alignment before adopting reliability targets and requires testing of resilience and recovery behaviors.

This skill is designed for site reliability engineers, DevOps engineers, platform teams, cloud infrastructure specialists, and organizations operating distributed or production-critical systems. It is useful for teams implementing SRE practices for the first time, improving observability and operational maturity, managing on-call processes, reducing operational toil, or introducing formal reliability engineering standards. Common use cases include building SLO programs, creating incident response procedures, designing monitoring systems, implementing chaos engineering initiatives, and establishing automation-driven operational workflows for scalable infrastructure.

FAQ

What types of outputs does the sre-engineer skill generate?

The skill generates implementation-focused outputs such as SLO definitions, SLI measurements, monitoring and alerting configurations, automation scripts, operational runbooks, and reliability impact explanations.

Does this skill support monitoring and alerting integrations?

Yes. The skill includes guidance for monitoring and alerting systems, including Prometheus-style alerting configurations and golden signal monitoring practices.

Can this skill be used for incident management and chaos engineering?

Yes. The skill supports incident response design, blameless postmortems, resilience testing, and chaos engineering workflows to validate recovery and operational readiness.

What reliability practices are required when using this skill?

The skill requires quantitative SLO definitions, error budget calculations, monitoring of golden signals, toil measurement, automation planning, postmortem practices, and resilience testing before marking experiments complete.

Are there operational limitations or constraints defined by this skill?

Yes. The skill discourages manual recurring processes, unsupported alerting without runbooks, ignoring error budget exhaustion, deploying without capacity planning, and setting SLOs without clear user-impact justification.

All Files

6 files
references/incident-chaos.md16.4 KB
View
references/automation-toil.md14.5 KB
View
SKILL.md6.6 KB
View
references/slo-sli-management.md6.6 KB
View
references/monitoring-alerting.md11.3 KB
View
references/error-budget-policy.md9.6 KB
View

Install sre-engineer

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill