sre-engineer

Define SLIs and SLOs, calculate error budgets, and implement burn-rate alerting.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill sre-engineer-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sre-engineer
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/claude-skills/skills/sre-engineer
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill sre-engineer-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you prevent outages and reduce operational toil by turning reliability goals into measurable SLOs, actionable monitoring, and well-defined response automation.

Core Features & Use Cases

  • SLO/SLI Definition: Define user-centered SLIs, set quantitative SLO targets, and ensure the measurement matches real user impact.
  • Error Budget Management: Calculate error budgets, track burn rates, and apply clear operational policies when budgets are strained.
  • Monitoring & Incident Readiness: Build golden-signal dashboards and alerts that route responders to runbooks with remediation steps.
  • Toil Reduction & Resilience Testing: Identify repetitive operational work, automate it, and validate recovery behavior using chaos engineering.

Quick Start

Use the sre-engineer skill to design SLOs, monitoring, and incident response for your production service by providing your current reliability goals and operational constraints.

Frequently Asked Questions about sre-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define SLIs and SLOs to measure service reliability?

Calculate error budgets from your SLO targets to track burn rates and apply clear operational policies when budgets are strained. This method tracks how fast your service consumes its allowed unreliability margin and enforces corrective actions.

How do I set up multi-window burn-rate alerting for production incidents?

Multi-window burn-rate alerting monitors how quickly your error budget is consumed across different time windows. It triggers alerts based on burn rate thresholds, routing responders to runbooks with specific remediation steps to reduce incident response time.

How does chaos engineering validate resilience and reduce operational toil?

Chaos engineering validates resilience by executing controlled failure experiments that test recovery behavior. Simultaneously, identifying repetitive operational work allows you to automate toil, ensuring your service withstands production failures while minimizing manual intervention.

What is the best way to build golden-signal monitoring for incident readiness?

Build golden-signal monitoring by creating dashboards that track latency, traffic, errors, and saturation. Pair these dashboards with actionable alerts that route responders directly to runbooks containing predefined remediation steps for operational readiness.