Agent skill

Incident Response Planner

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Configure incident response planner operations. An agent skill from jeremylongshore/tons-of-skills-marketplace.

MITAuto-check passedDevOps & Cloud

Install Incident Response Planner

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill incident-response-planner -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace incident-response-planner --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/04-security-advanced/incident-response-planner .claude/skills/incident-response-planner && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
incident-response-planner
GitHub stars
2.8k
Token cost
~589 tokens
SKILL.md length
196 words
Files
1
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Configure incident response planner operations. An agent skill from jeremylongshore/tons-of-skills-marketplace.

  • Works in 4 steps: Provides step-by-step guidance for… → Follows industry best practices and… → Generates production-ready code and… → …
  • : incident response planner
  • SKILL.md covers Overview, When to Use, Instructions and Examples, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Incident Response Planner is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure incident response planner operations. Auto-activating skill for Security Advanced. Triggers on: incident response planner, incident response planner Part of the Security Advanced skill category. Use when working with incident response planner functionality. Trigger with phrases like "incident response planner", "incident planner", "incident".

Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering Incident response. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • : incident response planner
  • Incident response planner Part of the Security Advanced skill category
  • Working with incident response planner functionality
  • With phrases like incident response planner

Example prompts

  • “incident response planner”
  • “incident planner”
  • “incident”
  • “/incident-response-planner”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(cmd:*), Grep

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Provides step-by-step guidance for incident response planner
  2. Follows industry best practices and patterns
  3. Generates production-ready code and configurations
  4. Validates outputs against common standards

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(cmd:*)
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Incident Response Planner loads about 589 tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 196 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~95
When it runs · the whole SKILL.md, loaded when a task matches
~589

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 196 words, ~589 tokens.

Download SKILL.mdSave it as .claude/skills/incident-response-planner/SKILL.md (or your agent's skills folder).
name
incident-response-planner
description
Configure incident response planner operations. Auto-activating skill for Security Advanced. Triggers on: incident response planner, incident response planner Part of the Security Advanced skill category. Use when working with incident response planner functionality. Trigger with phrases like "incident response planner", "incident planner", "incident".
allowed-tools
Read, Write, Edit, Bash(cmd:*), Grep
compatibility
Designed for Claude Code
version
1.0.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
security, compliance

Incident Response Planner

Overview

This skill provides automated assistance for incident response planner tasks within the Security Advanced domain.

When to Use

This skill activates automatically when you:

  • Mention "incident response planner" in your request
  • Ask about incident response planner patterns or best practices
  • Need help with advanced security skills covering penetration testing, compliance frameworks, threat modeling, and enterprise security.

Instructions

  1. Provides step-by-step guidance for incident response planner
  2. Follows industry best practices and patterns
  3. Generates production-ready code and configurations
  4. Validates outputs against common standards

Examples

Example: Basic Usage Request: "Help me with incident response planner" Result: Provides step-by-step guidance and generates appropriate configurations

Prerequisites

  • Relevant development environment configured
  • Access to necessary tools and services
  • Basic understanding of security advanced concepts

Output

  • Generated configurations and code
  • Best practice recommendations
  • Validation results

Error Handling

ErrorCauseSolution
Configuration invalidMissing required fieldsCheck documentation for required parameters
Tool not foundDependency not installedInstall required tools per prerequisites
Permission deniedInsufficient accessVerify credentials and permissions

Resources

  • Official documentation for related tools
  • Best practices guides
  • Community examples and tutorials

Part of the Security Advanced skill category. Tags: pentesting, compliance, soc2, gdpr, threat-modeling

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/04-security-advanced/incident-response-planner of jeremylongshore/tons-of-skills-marketplace.

Open the folder on GitHubat commit cfae287

Compare with similar skills

Incident Response Planner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Incident Response Planner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Incident Response Planner this skilljeremylongshore/tons-of-skills-marketplace2.8k—~589Automated safety check: PassMIT
Kubernetes Network Root Cause Analysiskubeshark/kubeshark12k—~5.3kAutomated safety check: PassApache-2.0
UModel Root Cause Analysisalibaba/UnifiedModel415—~1.9kAutomated safety check: PassCustom licence
Learningskortix-ai/suna20k—~1.1kAutomated safety check: PassCustom licence
Nix Config Debugryan4yin/nix-config2.1k—~1.2kAutomated safety check: PassMIT
Oncallpigweed-project/pigweed548—~963Automated safety check: PassApache-2.0

Similar skills

  • Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.

    12k GitHub stars~5.3k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • UModel Root Cause Analysis

    alibaba/UnifiedModel

    Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.

    415 GitHub stars~1.9k tokensUpdated 17 days ago
    DevOps & CloudAuto-check passed
  • Learnings

    kortix-ai/suna

    The project's episodic memory: a timestamped ledger of rules paid for with real outages and near-misses, one entry per incident.

    20k GitHub stars~1.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Nix Config Debug

    ryan4yin/nix-config

    A skill your agent uses when something here is broken or stops working: an eval or build error, a failed activation, a dead or restarting unit, a mihomo or DNS outage, an unreachable host or MicroVM…

    2.1k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Oncall

    pigweed-project/pigweed

    Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).

    548 GitHub stars~963 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Axiom SRE Investigator

    openclaw/clawhub

    Investigates incidents and production problems with hypothesis-driven debugging, queries Axiom observability data when available, and keeps secrets out of commands and output.

    9.5k GitHub stars~7.1k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Incident Response Planner

What does Incident Response Planner do?

Configure incident response planner operations. An agent skill from jeremylongshore/tons-of-skills-marketplace. Incident Response Planner is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure incident response planner operations.

When should I use Incident Response Planner?

Incident Response Planner fits situations like: : incident response planner; incident response planner Part of the Security Advanced skill category; working with incident response planner functionality; with phrases like incident response planner.

How do I install Incident Response Planner in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill incident-response-planner -a claude-code`. Or copy the skill folder (skills/04-security-advanced/incident-response-planner in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/incident-response-planner in your project. Claude Code loads it when a task matches its description.

How do I install Incident Response Planner in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill incident-response-planner -a codex`. Or copy the skill folder (skills/04-security-advanced/incident-response-planner in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/incident-response-planner in your project. Codex loads it when a task matches its description.

Can I use Incident Response Planner in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill incident-response-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/incident-response-planner, .gemini/skills/incident-response-planner, .github/skills/incident-response-planner and .opencode/skills/incident-response-planner in your project.

What does Incident Response Planner need to run?

SKILL.md names no scripts, command-line tools or credentials: Incident Response Planner is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(cmd:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.

Does Incident Response Planner access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Incident Response Planner safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Incident Response Planner use?

Incident Response Planner is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Incident Response Planner use?

About 589 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Incident Response Planner?

Skills that share tags, products or a category with Incident Response Planner: Kubernetes Network Root Cause Analysis (kubeshark/kubeshark, 12k stars), UModel Root Cause Analysis (alibaba/UnifiedModel, 415 stars), Learnings (kortix-ai/suna, 20k stars) and Nix Config Debug (ryan4yin/nix-config, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Incident Response Planner?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.