Skip to content
TrustedSkillsbeta
Back to all skills

Incident Response Plan

Checked
aj-geddes·vlatest·devops·MIT

Automatically generates tailored incident response plans based on provided details and pre-defined templates.

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 aj-geddes/useful-ai-prompts --skill incident-response-plan -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

aj-geddes

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 aj-geddes/useful-ai-prompts at 3f5182cfd7.

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

Commit
3f5182cfd7
Manifest
skills/incident-response-plan/SKILL.md
Scanned
4 files, 672 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 incident-response-plan skill generates comprehensive, step-by-step recovery strategies for IT and cybersecurity breaches. It analyzes specific breach details to produce actionable plans covering containment, eradication, and post-incident review.

When to use it

  • Drafting a response protocol immediately after detecting a ransomware infection or data leak.
  • Preparing a standardized playbook for your team to handle recurring security incidents like phishing attacks.
  • Creating a custom recovery guide for a specific system architecture or cloud environment.
  • Simulating disaster scenarios to test the effectiveness of current organizational procedures.

Key capabilities

  • Generates structured incident response plans tailored to specific breach types.
  • Provides step-by-step instructions for containment and eradication phases.
  • Includes recommendations for post-incident analysis and prevention measures.
  • Adapts output based on provided details about the affected system or threat vector.

Example prompts

  • "Create an incident response plan for a suspected SQL injection attack on our customer database."
  • "Draft a step-by-step recovery guide for restoring services after a DDoS event."
  • "Generate a post-breach analysis checklist and remediation steps for a compromised employee workstation."

Tips & gotchas

  • Provide detailed context about your infrastructure, such as cloud providers or specific software versions, to get more relevant advice.
  • Always validate AI-generated security plans with qualified human experts before deploying them in production environments.