sre-reliability

Track SLIs/SLOs and error budgets for production service reliability.

Updated Aug 23, 2026

Search Tags:#observability #reliability #incident response #alerting #sre #slo

Ready to run

npx skills add https://github.com/MattJColes/macols-configs --skill sre-reliability

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sre-reliability
Source: https://github.com/MattJColes/macols-configs/tree/main/shared/personas/sre-reliability
Command: npx skills add https://github.com/MattJColes/macols-configs --skill sre-reliability

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill empowers Site Reliability Engineers (SREs) to handle production reliability concerns such as SLIs/SLOs, observability, alerting, incident response, and postmortems.

Core Features & Use Cases

SLIs/SLOs & Error Budgets: Define, track, and manage Service-Level Indicators, Service-Level Objectives, and error budgets for reliable services.
Observability: Leverage metrics, logs, and traces for service visibility.
Alerting: Set up alerting mechanisms that focus on user-experienced symptoms and provide actionable insights.
Incident Response: Facilitate efficient incident management and postmortem creation.
Production Resilience: Enhance system resilience with graceful degradation and capacity planning.

Quick Start

Use the sre-reliability skill to calculate your current SLO performance and budget allocation.

Frequently Asked Questions about sre-reliability

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

FAQPage Schema

How do I calculate SLO performance and error budget allocation for production services?▼

To calculate SLO performance and error budgets, you track Service-Level Indicators against your objectives to determine remaining user-experienced availability. This skill computes your current budget allocation to guide reliability decisions for high-traffic web services.

What is the best way to set up alerting based on user-experienced symptoms?▼

The best way to set up symptom-based alerting is to focus on actionable insights derived from Service-Level Indicators rather than internal metrics. This approach tracks user-experienced service levels to trigger relevant incident response workflows.

How do I use observability data like metrics, logs, and traces to improve system resilience?▼

You use observability data by leveraging metrics, logs, and traces to gain service visibility and identify degradation points. Combining these signals helps enhance production resilience through graceful degradation and proactive capacity planning.

Can I use this SRE approach for incident response and postmortem creation in high-traffic web services?▼

Yes, you can use this SRE approach for high-traffic web services to facilitate efficient incident management and postmortem creation. It provides structured means to track, respond to, and resolve user-experienced service disruptions.

When do I need to define Service-Level Indicators and Objectives for my application?▼

You need to define Service-Level Indicators and Objectives when managing production reliability for user-facing services. Defining SLIs and SLOs allows you to measure user-experienced reliability and establish actionable error budgets for system resilience.