sre-engineer

Defines SLIs and SLOs, calculates error budgets, and generates monitoring, alerting, and incident runbooks for production systems.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jsdfhasuh/emosonic --skill sre-engineer-jsdfhasuh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sre-engineer
Source: https://github.com/jsdfhasuh/emosonic/tree/main/.agents/skills/sre-engineer
Command: npx skills add https://github.com/jsdfhasuh/emosonic --skill sre-engineer-jsdfhasuh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams prevent outages and reduce firefighting by translating reliability targets into concrete SLI/SLOs, monitoring, and operational runbooks you can actually execute during incidents.

Core Features & Use Cases

  • SLI/SLO definition with error budgets: Create quantitative SLOs, compute error budgets, and use burn-rate thinking to decide when to slow down or act.
  • Alerting and monitoring that drives action: Design golden-signal dashboards and alerts with clear severity and remediation runbooks, avoiding symptom-only paging.
  • Incident readiness and resilience testing: Run incident response frameworks, produce blameless postmortems, and plan chaos experiments to validate recovery under failure.

Quick Start

Use the sre-engineer skill to define SLOs for your service, compute the current error budget status, and generate burn-rate alerting plus an incident runbook tailored to the signals that matter most.

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 with error budgets for my service?▼

To define SLIs and SLOs, establish quantitative reliability targets and compute error budgets to govern availability and latency. This translates reliability goals into measurable thresholds for monitoring and alerting decisions.

How do I set up burn-rate alerting and monitoring for production systems?▼

Set up burn-rate alerting by designing golden-signal dashboards and configuring alerts with clear severity levels. This approach avoids symptom-only paging by attaching actionable remediation runbooks to each alert.

What is the best way to create incident response runbooks for production outages?▼

The best way to create incident runbooks is to map golden-signal instrumentation to specific remediation steps. This ensures operational runbooks are actionable and tailored to the signals that matter most during incidents.

Do I need golden-signal instrumentation to use error-budget burn policies?▼

Yes, golden-signal instrumentation is required to provide the quantitative SLO targets and error-budget burn policy logic needed. Without these signals, the system cannot accurately measure availability or trigger alerts.

How does chaos engineering fit into SLO and incident preparedness workflows?▼

Chaos engineering validates recovery under failure by planning controlled experiments within incident preparedness workflows. This tests resilience against error-budget exhaustion and confirms incident response frameworks function correctly.

How do I write a blameless postmortem after an incident response?▼

Write a blameless postmortem by applying structured guidance to review incident responses and identify systemic reliability gaps. This process helps adjust SLOs, error budgets, and future chaos testing to prevent recurring outages.