aiskillstore/marketplace / skills/89jobrien/devops-runbooks
devops-runbooks
VerifiedOperational runbook and procedure documentation specialist. Use when creating incident response procedures, operational playbooks, or system maintenance guides.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.4 KB |
| references/RUNBOOK.template.md | markdown | 3.4 KB |
| skill-report.json | config | 11.8 KB |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-07-05T12:03:30.222Z",
"slug": "89jobrien-devops-runbooks",
"source_url": "https://github.com/89jobrien/steve/tree/main/steve/skills/devops-runbooks",
"source_ref": "main",
"model": "codex",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "539056e0852f9706fe8f9b2a48b3d95dd151f4cb8bb0988c3ede2f8d2e2419c7",
"tree_hash": "6dc922cb1bd12962f55845628dfee94b7a767f0c1d3e55348c2241c8664c1b2b",
"provenance": {
"model_effective": "codex",
"fallback_chain": [
{
"agent": "codex",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
}
},
"skill": {
"name": "devops-runbooks",
"description": "Operational runbook and procedure documentation specialist. Use when creating incident response procedures, operational playbooks, or system maintenance guides.",
"summary": "Creates structured runbooks for incident response, maintenance, rollback, troubleshooting, and escalation.",
"icon": "π¦",
"version": "1.0.2",
"author": "Joseph OBrien",
"license": "MIT",
"category": "devops",
"tags": [
"runbooks",
"incident-response",
"operations",
"on-call",
"documentation"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"external_commands"
]
},
"security_audit": {
"risk_level": "safe",
"is_blocked": false,
"safe_to_publish": true,
"analysis_status": "ok",
"summary": "The flagged RUNBOOK.template.md entries are benign placeholders for operational systems, not attempts to target the model system prompt. The SKILL.md backtick finding is inline Markdown around a reference path, not Ruby or shell execution. No semantic prompt injection, data exfiltration intent, or hidden command execution was found.",
"remediation": [],
"risk_factor_evidence": [
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 37,
"line_end": 37
}
]
}
],
"static_findings": [
{
"id": "blocker:references/RUNBOOK.template.md:32:template-injection-targeting-system-prompt",
"category": "blocker",
"severity": "medium",
"pattern": "Template injection targeting system prompt",
"file": "references/RUNBOOK.template.md",
"line_start": 32,
"line_end": 32,
"snippet": "- [ ] Access to {{SYSTEM_1}}"
},
{
"id": "blocker:references/RUNBOOK.template.md:33:template-injection-targeting-system-prompt",
"category": "blocker",
"severity": "medium",
"pattern": "Template injection targeting system prompt",
"file": "references/RUNBOOK.template.md",
"line_start": 33,
"line_end": 33,
"snippet": "- [ ] Access to {{SYSTEM_2}}"
},
{
"id": "blocker:references/RUNBOOK.template.md:41:template-injection-targeting-system-prompt",
"category": "blocker",
"severity": "medium",
"pattern": "Template injection targeting system prompt",
"file": "references/RUNBOOK.template.md",
"line_start": 41,
"line_end": 41,
"snippet": "| {{SYSTEM}} | {{VAULT_PATH_OR_LOCATION}} |"
},
{
"id": "external_commands:SKILL.md:37:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 37,
"line_end": 37,
"snippet": "- `references/RUNBOOK.template.md` - Comprehensive operational runbook format"
}
],
"finding_verdicts": [
{
"id": "blocker:references/RUNBOOK.template.md:32:template-injection-targeting-system-prompt",
"verdict": "false_positive",
"confidence": 0.95,
"reason": "The placeholder refers to access for an operational system in a runbook prerequisites checklist. It is not framed as a system prompt or an instruction to the assistant."
},
{
"id": "blocker:references/RUNBOOK.template.md:33:template-injection-targeting-system-prompt",
"verdict": "false_positive",
"confidence": 0.95,
"reason": "The placeholder appears beside another operational access requirement and represents a service or platform name. No prompt override language or assistant-directed instruction is present."
},
{
"id": "blocker:references/RUNBOOK.template.md:41:template-injection-targeting-system-prompt",
"verdict": "false_positive",
"confidence": 0.94,
"reason": "The table labels a credential location for a runbook target system. This is normal documentation templating and does not target the model system prompt."
},
{
"id": "external_commands:SKILL.md:37:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.98,
"reason": "The backticks are Markdown formatting around the reference file path. There is no Ruby code, shell interpolation, or executable command at this location."
}
],
"semantic_findings": [],
"critical_findings": [],
"high_findings": [],
"medium_findings": [],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 2,
"total_lines": 327,
"audit_model": "codex",
"audited_at": "2026-07-05T12:03:30.222Z",
"agent_auto_install_policy": "allowed",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Create Reliable DevOps Runbooks",
"value_statement": "Operational knowledge often lives in tickets, chat, and memory. This skill turns procedures into structured runbooks for incidents, maintenance, rollback, and escalation.",
"seo_keywords": [
"Claude",
"Codex",
"Claude Code",
"devops runbooks",
"incident response",
"operational playbooks",
"on-call documentation",
"rollback procedures",
"troubleshooting guides",
"maintenance procedures"
],
"actual_capabilities": [
"Creates runbooks with overview, prerequisites, quick reference, procedure, verification, rollback, troubleshooting, and escalation sections.",
"Defines access needs, required tools, credentials locations, key commands, URLs, and contacts.",
"Documents step-by-step procedures with expected output and verification checks.",
"Adds rollback steps and rollback verification for failed changes.",
"Captures troubleshooting scenarios, symptoms, causes, and resolutions.",
"Builds escalation paths and incident handoff templates."
],
"limitations": [
"It does not execute commands or validate live infrastructure state.",
"It needs accurate service names, contacts, access paths, and command examples from the user.",
"It cannot verify credentials, permissions, or dashboard URLs.",
"Generated procedures require review and testing before production use."
],
"use_cases": [
{
"title": "Prepare On-Call Procedures",
"description": "Create a clear incident response runbook for alerts, triage, verification, rollback, and escalation.",
"target_user": "SRE or on-call engineer"
},
{
"title": "Document Maintenance Tasks",
"description": "Turn recurring maintenance work into repeatable steps with prerequisites, commands, expected output, and checks.",
"target_user": "DevOps engineer"
},
{
"title": "Capture Team Knowledge",
"description": "Convert informal operational knowledge into a shared runbook for handoffs, training, and service ownership.",
"target_user": "Engineering manager"
}
],
"prompt_templates": [
{
"title": "Create a Basic Runbook",
"scenario": "Beginner request for a first draft.",
"prompt": "Create a runbook for restarting SERVICE_NAME. Include prerequisites, commands, expected output, verification, rollback, and escalation."
},
{
"title": "Build an Incident Playbook",
"scenario": "Intermediate incident response workflow.",
"prompt": "Create a P1 incident runbook for API latency. Include triage steps, dashboards, log checks, customer impact, decision points, and escalation."
},
{
"title": "Add Rollback and Validation",
"scenario": "Advanced procedure hardening.",
"prompt": "Improve this deployment procedure with rollback steps, verification commands, success criteria, failure handling, and expected outputs for each step."
},
{
"title": "Standardize Multiple Runbooks",
"scenario": "Advanced documentation cleanup.",
"prompt": "Review these runbook notes and convert them into a consistent operational format. Identify missing prerequisites, contacts, commands, and test evidence."
}
],
"output_examples": [
{
"input": "A user asks for a runbook to rotate database credentials.",
"output": "A structured procedure with prerequisites, credential storage notes, rotation steps, verification checks, rollback actions, and escalation contacts."
},
{
"input": "A team provides notes for a cache outage response.",
"output": "An incident playbook covering alert meaning, dashboards, log checks, remediation choices, success criteria, and handoff details."
},
{
"input": "An engineer shares a maintenance checklist for service restarts.",
"output": "A repeatable runbook with access requirements, quick commands, step-by-step actions, expected results, and post-change validation."
}
],
"best_practices": [
"Provide real service names, ownership details, and trusted command examples.",
"Test every procedure in a safe environment before production use.",
"Keep rollback, verification, and escalation sections updated after incidents."
],
"anti_patterns": [
"Do not publish commands that nobody has reviewed or tested.",
"Do not store secrets directly in a runbook.",
"Do not leave escalation contacts, dashboards, or credential paths as vague placeholders."
],
"faq": [
{
"question": "Does this skill execute operational commands?",
"answer": "No. It creates documentation and templates. Users must review and run commands themselves."
},
{
"question": "Can it create incident response runbooks?",
"answer": "Yes. It supports triage, verification, remediation, rollback, escalation, and handoff sections."
},
{
"question": "What information should I provide?",
"answer": "Provide service names, triggers, dashboards, commands, expected output, contacts, rollback steps, and known failure modes."
},
{
"question": "Can it document maintenance procedures?",
"answer": "Yes. It can turn recurring maintenance tasks into repeatable steps with checks and expected results."
},
{
"question": "Does it validate production access?",
"answer": "No. It can list required access, but it cannot test permissions or credentials."
},
{
"question": "Should generated runbooks be reviewed?",
"answer": "Yes. Teams should review, test, and update runbooks before relying on them during incidents."
}
]
},
"file_structure": [
{
"name": "references",
"type": "dir",
"path": "references",
"children": [
{
"name": "RUNBOOK.template.md",
"type": "file",
"path": "references/RUNBOOK.template.md",
"lines": 270
}
]
},
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 57
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product β it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product β not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial β a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK β model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER β read BEFORE opening the target file; don't skip because it "looks like a one-liner" β whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) β never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named β don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |