sre-engineer

Name: sre-engineer
Availability: InStock
Author: belokonm

Plan and implement SRE practices for SLOs, incident management, and reliability monitoring.

8|11|Updated Feb 15, 2026

Search Tags:#observability #reliability #sre #slo #incident-management #chaos-engineering #capacity-planning

Ready to run

npx skills add https://github.com/belokonm/claude-supercode-skills --skill sre-engineer-belokonm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sre-engineer
Source: https://github.com/belokonm/claude-supercode-skills/tree/main/sre-engineer-skill
Command: npx skills add https://github.com/belokonm/claude-supercode-skills --skill sre-engineer-belokonm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Site reliability engineering (SRE) combines software engineering and operations to build resilient systems. It provides structured methods to define service reliability goals, manage incidents, and improve observability, reducing toil and outages.

Core Features & Use Cases

Define and implement SLOs and error budgets for services to align reliability with business needs.
Manage incidents end-to-end from detection to post-mortem, with runbooks and escalation paths.
Conduct chaos engineering experiments and capacity planning to validate resilience and scaling.
Build observability platforms with metrics, logs, and traces to monitor health and performance.
Create automation and post-incident improvements to reduce toil and recurring outages.

Quick Start

Define an SLO for a new service, set up incident response, and implement basic observability dashboards.

Frequently Asked Questions about sre-engineer

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

FAQPage Schema

How do I define SLOs and error budgets for microservices?▼

To define SLOs and error budgets for microservices, you establish service reliability targets that align with business needs, tracking error budgets to balance feature velocity against system stability. This structured approach reduces outages and operational toil.

What is the best way to manage incident response workflows end-to-end?▼

Managing incident response workflows end-to-end involves handling incidents from initial detection through post-mortem, utilizing runbooks and defined escalation paths. This ensures structured resolution and drives post-incident automation to prevent recurring outages.

How does chaos engineering validate resilience for multi-region deployments?▼

Chaos engineering validates resilience for multi-region deployments by conducting controlled experiments that intentionally inject failures. This proactive testing uncovers architectural weaknesses, allowing you to validate scaling and capacity planning before real outages occur.

How do I build observability dashboards to monitor service health?▼

Building observability dashboards to monitor service health requires aggregating metrics, logs, and traces into a unified platform. This provides comprehensive visibility into performance and system behavior, enabling rapid detection of reliability issues across services.

Can I use SRE practices for capacity planning and scaling automation?▼

Yes, you can use SRE practices for capacity planning and scaling automation by analyzing observability data to forecast resource needs. This approach validates resilience and automates scaling actions, effectively reducing manual operational toil.