eng-runbook

Generates a single-page HTML engineering runbook with alerts, procedures, and on-call rotation.

Updated May 20, 2026
One-click install
npx skills add https://github.com/Keimoshi/Silverloft --skill eng-runbook-keimoshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-runbook
Source: https://github.com/Keimoshi/Silverloft/tree/main/open-design-port/skills/eng-runbook
Command: npx skills add https://github.com/Keimoshi/Silverloft --skill eng-runbook-keimoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing an operations runbook from scratch is slow and inconsistent; this Skill turns a short service brief into a complete, styled single-page HTML runbook covering alerts, dashboards, procedures, on-call rotation, and incident response. ## Core Features & Use Cases - Structured Runbook Layout: Produces a header with service name, owner team, severity tier, and version, plus a service summary with dependency list. - Operational Content Blocks: Generates an alerts table (name, severity, meaning, first response), dashboards links, 3-4 copy-pasteable procedure blocks with code, an on-call rotation table, and a 5-step incident response checklist. - Self-Contained HTML Output: Delivers one semantic HTML artifact with a single inline style block and monospace code formatting, ready to preview in a browser. - Use Case: Ask for a runbook for your auth service and receive a complete ops doc with deploy, rollback, and key-rotation procedures plus an on-call schedule. ## Quick Start Ask the assistant to write a runbook for your service, for example: write a runbook for our auth service covering alerts, dashboards, common procedures, and the on-call rotation.

Frequently Asked Questions about eng-runbook

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

FAQPage Schema
How do I generate an engineering runbook for a service?

Provide a brief naming the service and its owner, and the Skill produces a complete single-page HTML runbook. It includes a service summary, alerts table, common procedures with commands, on-call rotation, and an incident response checklist.

What sections does a generated runbook include?

The runbook includes a header with service name, owner team, severity tier and version, a summary with dependencies, an alerts table, dashboards links, 3-4 procedure blocks with code, an on-call rotation table, and a 5-step incident checklist.

What output format does the runbook skill produce?

It outputs a single self-contained HTML artifact using semantic markup with one inline style block and monospace formatting for code blocks. The file can be opened directly in a browser as a desktop prototype preview.

Can I customize the procedures and alerts in the runbook?

Yes, describe your service's real alerts, deploy commands, and rotation in the brief and the Skill adapts the content. The layout structure stays fixed while the operational details reflect your input.

When should I use this runbook skill instead of a wiki page?

Use it when you need a polished, self-contained on-call reference document quickly from a short brief. It suits prototype and documentation scenarios where a styled single-page HTML deliverable is preferred over editing a wiki.