runbook-generator
SolidRunbook Generator
Install
Quality Score: 89/100
Skill Content
Details
- Author
- alirezarezvani
- Repository
- alirezarezvani/claude-skills
- Created
- 7 months ago
- Last Updated
- yesterday
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
runbook-generator
Guidance for generating OpenStack runbooks with dual task/symptom indexing following NASA procedure standards. Use when creating incident response procedures, operational runbooks, or troubleshooting guides that must be verified against running infrastructure.
mission-control-generate-runbook
Generate an operational runbook through Mission Control. Use when the user wants RUNBOOK.md or a chat-native runbook covering startup, tests, build, debugging, local reset, logs, and deployment notes.
devops-runbooks
Operational runbook and procedure documentation specialist. Use when creating incident response procedures, operational playbooks, or system maintenance guides.
runbook-creator
Create runbook creator operations. Auto-activating skill for Technical Documentation. Triggers on: runbook creator, runbook creator Part of the Technical Documentation skill category. Use when working with runbook creator functionality. Trigger with phrases like "runbook creator", "runbook creator", "runbook".
runbook
Create or update a runbook for an operational scenario — an incident an alert fires for, a recurring scheduled task, or a known failure mode on a live service — using a consistent template. Use when writing, drafting, authoring, or updating a runbook for an alert, incident, on-call procedure, scheduled maintenance, or operational SOP. Each invocation produces one runbook at a time. Applies a YAGNI preflight that requires the scenario to be real (an alert that has fired, a recurring task that exists, or a live failure mode on a service that receives traffic) before producing the runbook. Does not produce feature or system documentation — use project-documentation. Does not record architectural decisions — use architectural-decision-record. Does not create coding standards — use coding-standard.