Document SRE patterns for SLOs, SLIs, runbooks, and incident response.
npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill sre-patterns
Please help me install this Agent Skill. Skill: sre-patterns Source: https://github.com/Tibsfox/gsd-skill-creator/tree/main/examples/skills/sre-patterns Command: npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill sre-patterns
SRE-patterns provide a structured approach to building reliable software systems by codifying objectives, measurement, and runbooks to prevent outages and toil.
Define a basic SLO for a service, implement a simple availability alert, and document a runbook for incident response.
High-intent search queries and answers about installing and using this skill.
Defining SLOs and SLIs requires establishing measurement frameworks that align engineering and business expectations. This approach codifies service level objectives and indicators to standardize reliability tracking across engineering teams.
Reducing operational toil involves applying automation, runbooks, and capacity planning with scalable SRE patterns. This structured approach prevents repetitive manual work by codifying incident response and reliability reviews.
Conducting a postmortem is guided by established SRE patterns that document incident response and reliability reviews. This process improves resilience across services by systematically analyzing outages and applying governance checks.
Capacity planning is needed when building reliable software systems that require scalable SRE patterns to prevent outages. It helps organizations manage resources proactively and align engineering capacity with service level objectives.
Yes, these SRE patterns satisfy requirements for documenting SRE concepts and performing governance checks across engineering teams. They provide a structured approach to standardize reliability and align business expectations organization-wide.
vibbsDefine structured logging, metrics, and tracing conventions for codebases.
kid-sidTriage production alerts, coordinate response, and document post-incident learnings.
EmmraanDesign monitoring strategies, alerting policies, and SLI/SLO frameworks for distributed systems.
saeed-vayghanOrchestrate chaos experiments with controlled failure injection to validate system resilience.
