skills.rest
TravisLeeeeee
TravisLeeeeeeCOMMUNITY
Explore all skills by this author →
GitHub

SRE (Site Reliability Engineer)

Define SLOs, multi-window burn-rate alerts, and observability plans for production microservices.

110|18|Updated Mar 25, 2026
Search Tags:#observability#incident response#chaos engineering#sre#error budget#runbooks#slo
One-click install
npx skills add https://github.com/TravisLeeeeee/awesome-openclaw-personas --skill sre-site-reliability-engineer-travisleeeeee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: SRE (Site Reliability Engineer)
Source: https://github.com/TravisLeeeeee/awesome-openclaw-personas/tree/main/personas/engineering/sre
Command: npx skills add https://github.com/TravisLeeeeee/awesome-openclaw-personas --skill sre-site-reliability-engineer-travisleeeeee

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It prevents outages and slowdowns by defining reliability targets, measuring real user impact, and triggering the right actions before error budgets are exhausted.

Core Features & Use Cases

  • SLOs & error budgets: Create SLOs and multi-window burn-rate alerts to decide whether to ship or fix reliability first.
  • Observability: Build the three pillars (metrics, logs, traces) and organize golden signals to quickly answer what failed and where latency/error originates.
  • Toil reduction & incident response: Automate repetitive operational work with runbooks, use SLO-based severity, and run blameless post-incident reviews that focus on systemic fixes.
  • Chaos engineering & capacity planning: Proactively uncover weaknesses and right-size resources using data rather than guesses.

Quick Start

Ask the AI to generate an SLO + golden-signals observability plan for your payment API, including burn-rate alert thresholds and an incident-response outline tied to SLO impact.

Frequently Asked Questions about SRE (Site Reliability Engineer)

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

FAQPage Schema
How do I set up multi-window burn-rate alerts for my microservices?▼

Multi-window burn-rate alerts evaluate SLI formulas against SLO thresholds to detect rapid error-budget burn rates. You configure alert parameters across short and long windows to trigger responses before reliability regressions exhaust budgets.

What is an error budget and when do I need it for release gating?▼

An error budget quantifies allowable unreliability from SLO targets. You need it for SLO-based release gating to decide whether to ship features or pause releases and prioritize fixing reliability issues first.

How do I map golden signals to the three pillars of observability?▼

Map golden signals by organizing metrics, logs, and traces to quickly identify what failed and where latency or errors originate. This three-pillar observability structure builds dashboards for rapid incident analysis.

Can I use runbooks to reduce incident response MTTR for production APIs?▼

Runbooks reduce MTTR by automating repetitive operational work and defining severity-based incident response procedures. They guide teams through standardized actions tied to SLO impact during production API outages.

Does chaos engineering help with capacity planning for microservices?▼

Chaos engineering proactively uncovers system weaknesses, while data-driven capacity planning right-sizes resources. Together they replace guesses with measurable data to ensure production microservices reliability.

What is the best way to run blameless post-incident reviews?▼

Blameless post-incident reviews focus on systemic fixes rather than individual blame. Establish severity-based incident response procedures and use observability data to drive structural improvements and reduce toil.

Related Skills

Explore More Software Engineering Skills→
CybLowCybLow
1

perf-slo

Define SLI, SLO, and SLA targets for API reliability metrics.

Community
Intermediate
JeffallanJeffallan
10.9k

sre-engineer

Define SLOs, SLIs, and error budgets for production reliability.

Community
Advanced
chavangorakh1999chavangorakh1999
1

observability-design

Design observability strategies covering logs, metrics, traces, SLOs, and alerts.

Community
Advanced
mjunaidcamjunaidca
27

operating-production-services

Define SLOs, error budgets, and burn-rate alerts for production services.

Community
Advanced