sre-runbook-advisor

Generate SRE incident runbooks and analyze SLO burn rates.

3|3|Updated Mar 8, 2026

Search Tags:#operations #incident response #runbook #postmortem #sre #slo

Ready to run

npx skills add https://github.com/jaskaranhundal/usap-skills --skill sre-runbook-advisor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sre-runbook-advisor
Source: https://github.com/jaskaranhundal/usap-skills/tree/main/platform/sre-runbook-advisor
Command: npx skills add https://github.com/jaskaranhundal/usap-skills --skill sre-runbook-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the creation of SRE runbooks, analyzes Service Level Objective (SLO) burn rates, and facilitates blameless postmortems, streamlining incident response and operational efficiency.

Core Features & Use Cases

Runbook Generation: Creates structured runbooks for common failure modes, including security considerations.
SLO Analysis: Analyzes SLO burn rates and error budget consumption to determine incident severity.
Postmortem Facilitation: Guides users through blameless postmortem processes, including 5-Why analysis.
Use Case: When an alert fires for a critical service, this Skill can instantly generate a runbook with immediate actions, diagnosis steps, and escalation paths, while also assessing the SLO burn rate to inform the response urgency.

Quick Start

Use the sre-runbook-advisor skill to generate a runbook for a database connection pool exhaustion alert.

Frequently Asked Questions about sre-runbook-advisor

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

FAQPage Schema

How do I generate an SRE runbook for common failure modes like database connection pool exhaustion?▼

To generate an SRE runbook for database connection pool exhaustion, provide the alert context to trigger structured runbook creation. The output includes immediate actions, diagnosis steps, security considerations, and on-call escalation paths.

How does SLO burn rate analysis determine incident response urgency?▼

SLO burn rate analysis determines incident response urgency by evaluating error budget consumption against your Service Level Objectives. This analysis calculates how quickly your error budget is depleting to inform the required severity of the operational response.

What is a blameless postmortem and how do I facilitate one after an incident?▼

A blameless postmortem is a post-incident review focusing on systemic issues rather than individual fault. Facilitate one by guiding the team through structured processes like 5-Why analysis to identify root causes and prevent future recurrence.

Can I use this for on-call escalation guidance when a critical service alert fires?▼

Yes, you can use this for on-call escalation guidance when a critical service alert fires. It bridges incident detection and structured operational response by providing contextual escalation paths alongside the generated runbook and SLO burn rate data.

What is the best way to structure incident response runbooks for operational efficiency?▼

The best way to structure incident response runbooks is to use templated generation for common failure modes. This ensures consistent formatting covering immediate actions, diagnostic steps, and security considerations to streamline operational efficiency.