sre-runbook

Generates structured operational runbooks for failure scenarios and publishes them to Confluence.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill sre-runbook-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sre-runbook
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/ai-sre/skills/sre-runbook
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill sre-runbook-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When production incidents occur, teams often lack documented troubleshooting procedures, forcing engineers to improvise diagnosis and remediation steps under pressure. This Skill creates standardized, actionable runbooks for specific failure scenarios so on-call engineers can resolve issues faster. ## Core Features & Use Cases - Structured Runbook Generation: Produces runbooks with overview, prerequisites, symptoms, diagnosis, remediation, escalation, and prevention sections, pre-filled with real kubectl and Azure CLI commands. - Multi-Product Support: Covers Trigent products including Emergency Management, Training Platform, Visitor Management, CPOMS StudentSafe/StaffSafe, SmartPass, and SchoolPass, with product-specific namespaces and resource names resolved from the sre-kb GitLab group. - Confluence Publishing: Creates or updates runbook pages directly in the MI Confluence space under the Runbooks folder, checking for existing pages first. - Use Case: An SRE notices push notifications failing in Emergency Management and runs the skill with the scenario, receiving a complete runbook with ANH diagnosis commands, remediation options, and escalation contacts published to Confluence. ## Quick Start Ask the assistant to create a runbook for a specific product and failure scenario, for example: generate a runbook for em push notifications failing.

Frequently Asked Questions about sre-runbook

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

FAQPage Schema
How do I create an operational runbook for a Kubernetes failure scenario?

Run the skill with a product slug and failure scenario, such as a runbook for em push notifications failing. It gathers current pod state via kubectl, searches recent Jira incidents, and generates a structured runbook with diagnosis and remediation commands published to Confluence.

What products does the sre-runbook skill support?

It supports Emergency Management, Training Platform, PSW Canada, Visitor Management, Volunteer Management, DismissalSafe, CPOMS StudentSafe and StaffSafe, SmartPass, SchoolPass, EventSafe, and Badge Alert. Product slugs are resolved against the sre-kb GitLab group for infrastructure details.

Does the runbook skill update existing Confluence pages?

Yes, before creating a new page it checks the MI Confluence space under the Runbooks parent folder for an existing runbook matching the scenario. If one exists, it offers to update that page instead of creating a duplicate.

What tools are required to generate a runbook?

The skill uses kubectl for pod state, Azure CLI for subscription access, the GitLab API for pipeline history, Jira for recent incident search, and Atlassian MCP tools for Confluence publishing. Missing access to these limits the gathered context.

What sections does a generated runbook contain?

Each runbook includes overview, prerequisites, symptoms table, step-by-step diagnosis with kubectl commands, remediation options with risk levels, escalation contacts, and a prevention checklist. Commands are pre-filled with product-specific namespaces and resource names.