multiAI Summary Pending
devops-runbooks
Operational runbook and procedure documentation specialist. Use when creating incident response procedures, operational playbooks, or system maintenance guides.
231 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/devops-runbooks/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/89jobrien/devops-runbooks/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/devops-runbooks/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How devops-runbooks Compares
| Feature / Agent | devops-runbooks | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Operational runbook and procedure documentation specialist. Use when creating incident response procedures, operational playbooks, or system maintenance guides.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# DevOps Runbooks Skill Creates actionable runbooks for operational procedures, incident response, and system maintenance. ## What This Skill Does - Creates operational runbooks - Documents incident procedures - Defines escalation paths - Provides troubleshooting guides - Documents rollback procedures - Captures operational knowledge ## When to Use - Incident response planning - On-call documentation - System maintenance procedures - Disaster recovery planning - Knowledge transfer ## Reference Files - `references/RUNBOOK.template.md` - Comprehensive operational runbook format ## Runbook Structure 1. **Overview** - Purpose and when to use 2. **Prerequisites** - Access and tools needed 3. **Quick Reference** - Key commands and URLs 4. **Procedure** - Step-by-step with verification 5. **Rollback** - How to revert changes 6. **Troubleshooting** - Common issues 7. **Escalation** - When and how to escalate ## Best Practices - Commands must be copy-pasteable - Include expected output for each step - Document decision points clearly - Define rollback at each step - Keep procedures current (test regularly) - Include escalation contacts