eng-runbook

Generate engineering runbooks with alerts, dashboards, and incident response procedures.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/MyHeavenDyf/UXAI --skill eng-runbook-myheavendyf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-runbook
Source: https://github.com/MyHeavenDyf/UXAI/tree/main/packages/app/octoapp/templates/eng-runbook
Command: npx skills add https://github.com/MyHeavenDyf/UXAI --skill eng-runbook-myheavendyf

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the complexities of managing engineering runbooks and incident response procedures, providing a comprehensive guide and checklist.

Core Features & Use Cases

  • Engineering Runbook: Offers a structured format for service overview, alerts, dashboards, common procedures, and on-call rotation.
  • Incident Response: Provides a checklist for handling incidents efficiently.
  • Use Case: When your team needs a structured guide for service alerts, dashboards, and common procedures during on-call rotations, this Skill can save time and improve incident management.

Quick Start

Generate an engineering runbook for the auth service by mentioning 'runbook' in the prompt.

Frequently Asked Questions about eng-runbook

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

FAQPage Schema
How do I create an engineering runbook for service management?

To create an engineering runbook, this tool automates the generation of a structured document covering service overviews, alerts, dashboards, and common procedures. You simply mention 'runbook' along with your service name to produce the complete guide.

What should an incident response checklist include for on-call rotations?

An incident response checklist should include structured procedures for handling alerts, monitoring dashboards, and executing common operations. This tool provides that checklist format to ensure efficient incident management during your on-call rotations.

Can I dynamically generate ops docs for multiple microservices?

You can generate ops docs dynamically by running the provided scripts for each service. The process uses reference files to automatically populate the runbook structure with the correct links and procedures for the specified service.

Does this runbook generator work without external dependencies?

This runbook generator works entirely standalone without external dependencies. It relies on internal scripts and reference files to dynamically build the service management documentation and incident response procedures.

What is the best way to structure on-call procedures and dashboards?

The best way to structure on-call procedures is using a comprehensive runbook format that separates service overviews, alerts, dashboards, and common procedures. This approach ensures quick access to critical information during active incidents.

Why does my team need a standardized runbook for incident response?

Your team needs a standardized runbook to reduce complexities in managing incident response procedures. Having a structured guide saves time and improves management efficiency when handling service alerts during on-call rotations.