sre-engineer

Define SLOs, error budgets, monitoring, and automation scripts for production systems.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill sre-engineer-shalevamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sre-engineer
Source: https://github.com/shalevamin/The-_Ultimate_agents/tree/main/.claude/skills/sre-engineer
Command: npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill sre-engineer-shalevamin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you define, implement, and maintain highly reliable production systems by focusing on Service Level Objectives (SLOs), error budgets, monitoring, and automation.

Core Features & Use Cases

  • SLO/SLI Definition: Define clear, measurable Service Level Indicators (SLIs) and Service Level Objectives (SLOs) to track system reliability.
  • Error Budget Management: Implement policies for managing error budgets, guiding tradeoffs between reliability and feature velocity.
  • Monitoring & Alerting: Configure robust monitoring for golden signals (latency, traffic, errors, saturation) and set up actionable alerts.
  • Automation & Toil Reduction: Identify and automate repetitive operational tasks to reduce toil and improve efficiency.
  • Incident Management & Chaos Engineering: Develop incident response procedures and proactively test system resilience through chaos engineering.
  • Use Case: A team wants to ensure their e-commerce checkout service is available 99.95% of the time. This Skill can help them define the SLIs for availability, set up monitoring, create alerts for when the error budget is being consumed too quickly, and automate common remediation tasks.

Quick Start

Use the sre-engineer skill to define SLOs for the payment service, focusing on latency and availability.

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 track system reliability?

Defining SLIs and SLOs involves establishing clear, measurable indicators for latency and availability, such as targeting 99.95% uptime for a service, to track system reliability. This Skill helps you formulate these metrics to balance reliability with feature velocity using error budget policies.

What is the best way to manage error budgets and guide development tradeoffs?

Managing error budgets requires implementing specific policies that guide tradeoffs between reliability and feature velocity. This Skill creates error budget policies that help teams decide when to halt feature deployments to focus on stability based on consumed error budget thresholds.

How do I set up monitoring and alerting for golden signals in production systems?

Setting up monitoring for golden signals involves configuring tracking for latency, traffic, errors, and saturation across production systems. This Skill generates monitoring configurations and establishes actionable alerts to notify teams when reliability targets are at risk.

Can I use this to develop incident response procedures and run chaos engineering tests?

Yes, you can develop incident response procedures and proactively test system resilience through chaos engineering. This Skill helps design incident management workflows and creates plans for chaos engineering to validate system robustness before actual outages occur.

How do I reduce operational toil through automation in site reliability engineering?

Reducing operational toil through automation involves identifying repetitive operational tasks and generating scripts to handle them automatically. This Skill produces automation scripts to eliminate manual workload, improving efficiency and allowing teams to focus on engineering work.