Skip to content
TrustedSkillsbeta
Back to all skills

Security Incident Playbook Generator

Checked
patricio0312rev·vlatest·security·MIT

Automatically generates tailored incident response playbooks based on provided threat data and organizational context.

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 patricio0312rev/skills --skill security-incident-playbook-generator -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

patricio0312rev

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 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 patricio0312rev/skills at 79ea6af485.

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

Commit
79ea6af485
Manifest
security/security-incident-playbook-generator/SKILL.md
Scanned
1 file, 75 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

The security-incident-playbook-generator skill enables AI agents to automatically create structured, step-by-step response guides for specific cybersecurity events. It transforms raw incident data into actionable playbooks that align with standard operational procedures.

When to use it

  • Rapidly drafting containment strategies during active breach scenarios.
  • Generating recovery checklists after a successful system restoration.
  • Creating documentation templates for post-incident reviews and lessons learned.
  • Standardizing response protocols across different departments or threat types.

Key capabilities

  • Generates structured incident response playbooks from provided context.
  • Adapts output to specific security event types (e.g., malware, phishing, DDoS).
  • Produces clear, sequential action items for security teams.
  • Formats content suitable for immediate operational use or documentation archives.

Example prompts

  • "Create a containment playbook for a suspected ransomware infection on the internal file server."
  • "Generate a step-by-step recovery guide following a successful phishing email takedown."
  • "Draft a post-incident review template based on the details of last week's DDoS attack."

Tips & gotchas

Ensure you provide detailed context about the specific incident type and your organization's existing tools to maximize playbook relevance. Always verify generated steps against current internal policies before deployment, as AI outputs may not reflect unique local constraints or compliance requirements.