sre-engineer

Define SLIs and SLOs, automate toil reduction, and plan capacity for reliable systems.

30|7|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/saeed-vayghan/gemini-agent-skills --skill sre-engineer-saeed-vayghan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sre-engineer
Source: https://github.com/saeed-vayghan/gemini-agent-skills/tree/main/.gemini/skills/sre-engineer
Command: npx skills add https://github.com/saeed-vayghan/gemini-agent-skills --skill sre-engineer-saeed-vayghan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill addresses the challenge of balancing rapid feature development with maintaining robust system stability and reliability.

Core Features & Use Cases

  • SLO/SLI Management: Define, track, and manage Service Level Objectives and Indicators.
  • Toil Reduction: Automate repetitive operational tasks to free up engineering time.
  • Chaos Engineering: Proactively identify system weaknesses through controlled experiments.
  • Use Case: Implement a Site Reliability Engineering framework for a new microservice to ensure it meets uptime targets and can withstand simulated failures.

Quick Start

Use the sre-engineer skill to analyze the reliability of the user authentication service and propose improvements.

Frequently Asked Questions about sre-engineer

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

FAQPage Schema
How do I define and track SLI and SLO metrics for a new microservice?

Defining SLI and SLO metrics requires analyzing service architecture and reliability requirements to establish measurable indicators. You can track Service Level Objectives and Indicators to balance feature velocity with system stability and ensure uptime targets are met.

What is the best way to reduce operational toil through automation?

Reducing operational toil through automation involves identifying repetitive operational tasks and implementing automated solutions. This frees up engineering time and supports sustainable on-call practices by minimizing manual intervention in system reliability engineering.

How does chaos engineering help identify system weaknesses proactively?

Chaos engineering identifies system weaknesses proactively by running controlled experiments that simulate failures. This approach tests system stability and resilience, allowing you to address potential issues before they impact actual service uptime.

Do I need service architecture data to implement an SRE framework?

Yes, implementing an SRE framework requires context on service architecture, reliability requirements, and operational data. This information is essential to create solutions that accurately balance feature velocity with system stability.

How do I balance feature velocity with system stability when planning capacity?

Balancing feature velocity with system stability during capacity planning involves using error budgets to manage risk. This approach allows rapid feature development while maintaining highly reliable and scalable systems through structured SRE practices.