skills.rest
jc180105
jc180105COMMUNITY
Explore all skills by this author →
GitHub

SRE (Site Reliability Engineer)

Define and enforce reliability targets with SLOs and error budgets.

Updated Apr 16, 2026
Search Tags:#observability#reliability#sre#slo#chaos-engineering#capacity-planning#toil-reduction
One-click install
npx skills add https://github.com/jc180105/.opencode --skill sre-site-reliability-engineer-jc180105
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: SRE (Site Reliability Engineer)
Source: https://github.com/jc180105/.opencode/tree/main/.opencode/skills/engineering-sre
Command: npx skills add https://github.com/jc180105/.opencode --skill sre-site-reliability-engineer-jc180105

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Site reliability engineering focuses on turning reliability into a controllable, data-driven component of product development. This skill codifies reliability as a budget with SLOs, error budgets, and observability, enabling proactive improvements rather than firefighting.

Core Features & Use Cases

  • SLOs & error budgets — Define, measure, and enforce reliability targets to guide feature shipping and incident response.
  • Observability — Design and implement logs, metrics, and traces that answer "why did this happen?" quickly.
  • Toil reduction & automation — Automate repetitive operational tasks to reduce toil and manual toil-driven risk.
  • Chaos engineering — Proactively test system weaknesses before users are affected.
  • Capacity planning — Right-size resources using data-driven insights and load forecasts.

Quick Start

Define SLOs for critical services and implement automated monitoring to enforce them.

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 define and enforce SLOs for cloud-based microservices?▼

To define and enforce SLOs for cloud-based microservices, you establish measurable reliability targets and error budgets that guide feature shipping and incident response. This approach turns reliability into a data-driven component of product development.

What is the best way to reduce operational toil during on-call rotations?▼

The best way to reduce operational toil during on-call rotations is to automate repetitive manual tasks. This minimizes toil-driven risk and shifts focus from firefighting to proactive system reliability improvements.

How does chaos engineering proactively test system weaknesses?▼

Chaos engineering proactively tests system weaknesses by injecting controlled failures into production services. This validates reliability targets and identifies vulnerabilities before actual users are affected.

Can I use error budgets to balance feature shipping and incident response?▼

Yes, you can use error budgets to balance feature shipping and incident response. By measuring and enforcing SLOs, error budgets dictate whether development should pause for reliability improvements or continue deploying new features.

Related Skills

Explore More Software Engineering Skills→
vincent119vincent119

devops-runbooks

Automates creation and maintenance of operational Runbooks for incident response.

Community
Intermediate
vecearvecear

capacity-planning-helper

Forecast infrastructure needs and estimate compute, database, and cache resources.

Community
Advanced
fabioc-alohafabioc-aloha
1

Observability & Monitoring

Implements structured logging, metrics, distributed tracing, and alerting for production systems.

Community
Intermediate
AbdullahMalik17AbdullahMalik17
9

operating-production-services

Define SLOs, error budgets, and blameless postmortems for production service reliability.

Community
Intermediate