Skip to content
TrustedSkillsbeta
Back to all skills

Incident Runbook Templates

Listed
sickn33·vlatest·devops·MIT

This skill provides pre-built incident runbook templates for faster troubleshooting and consistent responses to common issues, boosting team efficiency.

Repository

Install on your platform

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

  1. 1

    Run this in your project

    terminal
    $ npx skills add sickn33/agentic-awesome-skills --skill incident-runbook-templates -a claude-code

  2. 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

sickn33

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

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    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 sickn33/antigravity-awesome-skills at 5a4cdd9df8.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
5a4cdd9df8
Manifest
skills/incident-runbook-templates/SKILL.md
Scanned
0 files
Copies in repo
3 — all of them scanned
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 provides pre-configured incident runbook templates designed to streamline response procedures during system outages or security breaches. It equips AI agents with structured documentation formats to ensure consistent and rapid handling of critical operational events.

When to use it

  • Automating the generation of initial response steps when a server goes down unexpectedly.
  • Standardizing communication logs for security teams investigating potential data leaks.
  • Creating quick-reference guides for on-call engineers during high-pressure maintenance windows.
  • Drafting post-incident review summaries to capture root cause analysis details efficiently.

Key capabilities

  • Pre-defined structural layouts for incident documentation.
  • Templates tailored for various types of operational failures.
  • Ready-to-use formats that reduce manual drafting time.

Example prompts

  • "Generate an incident runbook template for a database connection failure including root cause analysis sections."
  • "Create a structured response plan for a suspected ransomware attack using the available templates."
  • "Draft a post-mortem summary template based on the recent API latency spike we experienced."

Tips & gotchas

Ensure you customize the generic placeholders within the templates to reflect your specific infrastructure and escalation paths before deployment. These templates serve as foundational structures; they do not automatically detect incidents or execute remediation scripts without additional integration logic.