SRE - Site Reliability Engineering

Define and enforce SRE practices for reliable, scalable production systems.

4|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/weirdgme/Claude-code-infrastructure-showcase --skill sre-site-reliability-engineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: SRE - Site Reliability Engineering
Source: https://github.com/weirdgme/Claude-code-infrastructure-showcase/tree/main/.claude/skills/sre
Command: npx skills add https://github.com/weirdgme/Claude-code-infrastructure-showcase --skill sre-site-reliability-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to building and operating reliable software systems by applying SRE principles to production environments.

Core Features & Use Cases

  • SLI/SLO/Incident Management: Define reliable metrics, objectives, and runbooks to govern service reliability.
  • Observability & Monitoring: Implement telemetry, dashboards, alerts, and post-incident reviews to improve visibility.
  • Chaos Engineering & Resilience: Design and run resilience experiments to validate blast radius and recovery.
  • Capacity & Disaster Recovery Planning: Plan capacity, perform load testing, and prepare DR procedures.

Quick Start

Start by defining an SLI for a critical service, creating a corresponding SLO, and drafting a basic incident response runbook. Then set up a simple observability dashboard to monitor latency and error rates for ongoing improvement.

Frequently Asked Questions about SRE - Site Reliability Engineering

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

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

To define service reliability, establish SLIs to measure latency and error rates, then set corresponding SLOs to govern objectives and draft runbooks for incident response. This provides structured governance for production environments.

What's the best way to structure incident response runbooks for production services?

The best way to structure incident response runbooks is to align them with defined SLOs and integrate observability telemetry. This enables automated remediation patterns and structured post-incident reviews for continuous improvement.

How does chaos engineering validate system resilience and blast radius?

Chaos engineering validates resilience by designing and running experiments that test system recovery and measure blast radius. This approach proactively identifies weaknesses in disaster recovery procedures before actual production failures occur.

Can I use this approach for capacity planning and disaster recovery?

Yes, this approach supports capacity planning and disaster recovery by enabling load testing and DR procedure preparation. It applies SRE principles to ensure scalable and reliable production environments across critical services.

What observability metrics do I need to set up dashboards for ongoing improvement?

Observability dashboards require telemetry metrics for service latency and error rates. Setting up alerts and post-incident reviews around these metrics provides visibility and drives ongoing reliability improvement across production systems.