agency-sre-site-reliability-engineer

Define SLOs, implement observability, and automate toil reduction for production systems.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-sre-site-reliability-engineer-immamdouhaboammar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-sre-site-reliability-engineer
Source: https://github.com/imMamdouhaboammar/kaku-chatgpt-harness/tree/main/.agents/skills/engineering-sre
Command: npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-sre-site-reliability-engineer-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of maintaining high-availability production systems by replacing reactive firefighting with data-driven reliability engineering and automated toil reduction.

Core Features & Use Cases

  • SLO & Error Budget Management: Define and monitor service level objectives to balance feature velocity with system stability.
  • Observability Framework: Implement the three pillars of observability (metrics, logs, traces) to diagnose system health and latency issues.
  • Use Case: When a service experiences intermittent 5xx errors, use this Skill to analyze the burn rate against your error budget and generate an automated runbook to mitigate the impact.

Quick Start

Use the agency-sre-site-reliability-engineer skill to define a new availability SLO for the payment-api service with a 99.95 percent target over a 30 day window.

Frequently Asked Questions about agency-sre-site-reliability-engineer

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

FAQPage Schema
How do I define and monitor SLOs to balance feature velocity with system stability?

Define service level objectives and track error budgets to balance feature velocity with system stability. This approach replaces reactive firefighting with data-driven reliability engineering, allowing automated toil reduction while maintaining high availability.

What is the best way to implement observability for diagnosing cloud infrastructure health and latency issues?

Implement observability by utilizing the three pillars of metrics, logs, and traces. This framework diagnoses system health and latency issues in cloud infrastructure, enabling proactive reliability engineering and faster incident response planning.

How does error budget burn rate analysis help with intermittent 5xx errors?

Error budget burn rate analysis measures the impact of intermittent 5xx errors against your service level objectives. It triggers automated runbooks to mitigate impact, ensuring system stability through data-driven reliability engineering rather than reactive firefighting.

Can I use blameless post-incident reviews for data-driven risk assessment in production systems?

Blameless post-incident reviews are required protocols for data-driven risk assessment in production systems. They support proactive reliability engineering by focusing on systemic issues rather than individual blame, improving future incident response planning.

When do I need automated toil reduction for maintaining high-availability production systems?

Automated toil reduction is needed when maintaining high-availability production systems becomes heavily manual. It replaces reactive firefighting with data-driven reliability engineering, optimizing capacity and ensuring sustained system stability.