Runbook Creation

Name: Runbook Creation
Author: bagelhole

Checked

bagelhole·vlatest·devops·MIT

Automatically generates detailed runbooks from incident reports, knowledge bases, and system documentation for faster remediation.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add bagelhole/devops-security-agent-skills --skill runbook-creation -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

bagelhole

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 30 Sept 2026

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned bagelhole/devops-security-agent-skills at 0365f57a07.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 0365f57a07
Manifest: compliance/continuity/runbook-creation/SKILL.md
Scanned: 1 file, 466 lines

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

This skill generates runbooks, which are documented procedures for responding to incidents or performing specific tasks. It can create these runbooks from scratch based on a description of the process or adapt existing documentation into a standardized runbook format. The resulting runbooks provide clear, step-by-step instructions for operators and engineers.

When to use it

When onboarding new team members who need documented procedures for common tasks.
To standardize incident response processes across different teams or environments.
To convert existing, unstructured documentation (like emails or chat logs) into formal runbooks.
For automating repetitive operational tasks with clear instructions for human intervention if needed.

Key capabilities

Runbook generation from descriptions
Adaptation of existing documentation to runbook format
Standardized runbook structure

Example prompts

"Create a runbook for restarting the database server after a failure."
"Generate a runbook based on this email thread describing how we handle network outages."
“Write a runbook detailing steps to investigate and remediate high CPU utilization on web servers.”

Tips & gotchas

The quality of the generated runbook depends heavily on the clarity and detail provided in the initial description or source documentation. Providing context about the environment and potential failure modes will improve results.