site-reliability-engineer

Define SLI/SLOs, configure monitoring stacks, and draft incident response runbooks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gaebalai/CodeGraphMCPServer --skill site-reliability-engineer-gaebalai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: site-reliability-engineer
Source: https://github.com/gaebalai/CodeGraphMCPServer/tree/main/.claude/skills/site-reliability-engineer
Command: npx skills add https://github.com/gaebalai/CodeGraphMCPServer --skill site-reliability-engineer-gaebalai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables organizations to implement robust production monitoring, observability, and incident response capabilities, reducing mean time to resolution and improving service reliability.

Core Features & Use Cases

  • SLI/SLO definition and tracking to quantify availability, latency, and error budgets.
  • Monitoring stack setup guidance for Prometheus, Grafana, logging backends (ELK/Datadog), and instrumentation recommendations.
  • Alert rules and notification workflows to detect incidents and notify on-call in real time.
  • Incident response runbooks and post-mortem templates to drive blameless learning and continuous improvement.
  • Health checks, dashboards, and traces to maintain end-to-end visibility across services.

Quick Start

Start by defining your service-level objectives, then configure your monitoring stack, set up alerting, and draft runbooks to standardize incident response.

Frequently Asked Questions about site-reliability-engineer

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

FAQPage Schema
How do I define SLI and SLO metrics to quantify service reliability and error budgets?

To set up production monitoring and observability, you configure a monitoring stack using Prometheus and Grafana, integrate logging backends like ELK or Datadog, and implement instrumentation. This establishes end-to-end visibility across complex software systems and maintains real-time health checks.

How do I configure alert rules and notification workflows for incident response?

To configure alert rules and notification workflows, you define thresholds based on your SLOs and set up real-time notification channels to alert on-call teams. This detects incidents immediately and standardizes the incident response workflow across operations teams.

What is the best way to create incident response runbooks and post-mortem templates?

The best way to create incident response runbooks and post-mortem templates is to draft standardized documentation that drives blameless learning and continuous improvement. This reduces mean time to resolution by providing clear, actionable steps during live service incidents.

Can I use this for managing complex software systems requiring dashboards and traces across multiple stacks?

Yes, you can use this for managing complex software systems requiring dashboards and traces across multiple stacks. It provides health checks, dashboards, and traces to maintain end-to-end visibility across services, satisfying requirements for operations teams managing live services.