neekware/artifacts/bundle/skills/engineering/runbook-generator
artifacts/bundle/skills/engineering/runbook-generator/SKILL.md
# Runbook Generator **Tier:** POWERFUL **Category:** Engineering **Domain:** DevOps / Site Reliability Engineering --- ## Overview Generate operational runbooks quickly from a service name, then customize for deployment, incident response, maintenance, and rollback workflows. ## Core Capabilities - Runbook skeleton generation from a CLI - Standard sections for start/stop/health/rollback - Structured escalation and incident handling placeholders - Reference templates for deployment and
tools
Updated Apr 24, 2026
$ install --global
skillsauthnpx skillsauth add neekware/ehayeskills artifacts/bundle/skills/engineering/runbook-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 4:02 PM14.2s1 file scanned
SKILL.md
Runbook Generator
Tier: POWERFUL
Category: Engineering
Domain: DevOps / Site Reliability Engineering
Overview
Generate operational runbooks quickly from a service name, then customize for deployment, incident response, maintenance, and rollback workflows.
Core Capabilities
- Runbook skeleton generation from a CLI
- Standard sections for start/stop/health/rollback
- Structured escalation and incident handling placeholders
- Reference templates for deployment and incident playbooks
When to Use
- A service has no runbook and needs a baseline immediately
- Existing runbooks are inconsistent across teams
- On-call onboarding requires standardized operations docs
- You need repeatable runbook scaffolding for new services
Quick Start
# Print runbook to stdout
python3 scripts/runbook_generator.py payments-api
# Write runbook file
python3 scripts/runbook_generator.py payments-api --owner platform --output docs/runbooks/payments-api.md
Recommended Workflow
- Generate the initial skeleton with
scripts/runbook_generator.py. - Fill in service-specific commands and URLs.
- Add verification checks and rollback triggers.
- Dry-run in staging.
- Store runbook in version control near service code.
Reference Docs
references/runbook-templates.md
Common Pitfalls
- Missing rollback triggers or rollback commands
- Steps without expected output checks
- Stale ownership/escalation contacts
- Runbooks never tested outside of incidents
Best Practices
- Keep every command copy-pasteable.
- Include health checks after every critical step.
- Validate runbooks on a fixed review cadence.
- Update runbook content after incidents and postmortems.
Creator: Engineering License: MIT Source Repo:
neekware/ehaye-skillsSource Bucket:engineeringOriginal Path:engineering/runbook-generator
Related Skills
neekware/stress-test
testing
VerifiedTrustedCommunity
/em -stress-test — Business Assumption Stress Testing
SKILL.mdUpdated Jul 1, 2026
neekware/postmortem
research
VerifiedTrustedCommunity
/em -postmortem — Honest Analysis of What Went Wrong
SKILL.mdUpdated Jul 1, 2026
neekware/hard-call
development
VerifiedTrustedCommunity
/em -hard-call — Framework for Decisions With No Good Options
SKILL.mdUpdated Jul 1, 2026
neekware/challenge
research
VerifiedTrustedCommunity
/em -challenge — Pre-Mortem Plan Analysis
SKILL.mdUpdated Jul 1, 2026