sre

Define SLOs, error budgets, and observability for production systems.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/elihuvillaraus/skills --skill sre-elihuvillaraus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sre
Source: https://github.com/elihuvillaraus/skills/tree/main/sre
Command: npx skills add https://github.com/elihuvillaraus/skills --skill sre-elihuvillaraus

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the critical need for robust, reliable production systems by providing expert guidance on Site Reliability Engineering (SRE) principles and practices, ensuring high availability and efficient operations.

Core Features & Use Cases

  • SLO Management: Define, track, and manage Service Level Objectives and error budgets to balance velocity and reliability.
  • Observability: Implement and leverage metrics, logs, and traces for deep system insight and rapid debugging.
  • Toil Reduction: Systematically identify and automate repetitive operational tasks to free up engineering time.
  • Chaos Engineering: Proactively uncover system weaknesses through controlled experiments.
  • Use Case: A team is struggling with frequent production incidents. The SRE skill can help them define clear SLOs, set up appropriate monitoring, and identify automation opportunities to reduce manual interventions.

Quick Start

Use the sre skill to define SLOs for the payment-api service.

Frequently Asked Questions about sre

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

FAQPage Schema
How do I define SLOs and error budgets to balance development velocity and reliability?

To define SLOs and error budgets, you establish Service Level Objectives that set clear reliability targets, allowing you to balance development velocity and system stability through data-driven decisions.

What is the best way to reduce operational toil in production systems?

The best way to reduce operational toil in production systems is to systematically identify repetitive manual tasks and implement automation, freeing up engineering time for higher-value work.

How does chaos engineering help uncover system weaknesses proactively?

Chaos engineering uncovers system weaknesses proactively by running controlled experiments on your production systems, identifying hidden failures before they cause actual incidents.

How do I implement observability for rapid debugging using metrics, logs, and traces?

You implement observability for rapid debugging by leveraging metrics, logs, and traces to gain deep system insight, enabling quick identification and resolution of issues in production environments.

Can I use site reliability engineering practices for a team struggling with frequent production incidents?

Yes, you can use site reliability engineering practices for a team struggling with frequent production incidents by setting up appropriate monitoring, defining clear SLOs, and identifying automation opportunities.

Why does a blameless culture matter when maintaining system reliability?

A blameless culture matters for maintaining system reliability because it prioritizes data-driven decisions over individual fault, fostering an environment where teams can safely learn from production incidents.