Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Crisis Response

ASecurity

Manage PR crises. Use when: reputational threat emerges, need stakeholder messaging, or communication timeline.

847 stars
0 votes
0 copies
1 views
Added 6/9/2026
ai-agentsrustgogitapi

Works with

api

Security Analysis

A100/100

Scanned 6/9/2026

$npx -y skills add indranilbanerjee/digital-marketing-pro --skill crisis-response --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Crisis Response?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Crisis Response
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/indranilbanerjee-crisis-response/badge)](https://www.skillsdirectory.com/skills/indranilbanerjee-crisis-response)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: crisis-response
description: "Manage PR crises. Use when: reputational threat emerges, need stakeholder messaging, or communication timeline."
argument-hint: "[situation-description]"
---

# /digital-marketing-pro:crisis-response

## Purpose

Provide rapid crisis assessment and a structured response plan. Classifies severity, identifies stakeholders, drafts messaging for each audience, and builds a communication timeline to contain damage and rebuild trust.

## Input Required

The user must provide (or will be prompted for):

- **What happened**: Description of the crisis or incident
- **When it started**: Timeline of events so far
- **Current exposure**: How widely known is it (internal only, social media, press coverage)
- **Stakeholders affected**: Customers, employees, investors, partners, public
- **Actions taken so far**: Any statements, fixes, or responses already issued
- **Spokesperson**: Who will speak for the brand

## Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. **Also check for guidelines** at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions and relevant category files. Check for custom templates at `~/.claude-marketing/brands/{slug}/templates/`. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
2. **Severity classification**: Level 1 (monitor), Level 2 (respond), Level 3 (full mobilization) based on reach, impact, and trajectory
3. Assess the narrative: What is being said? What is the public sentiment? What is the worst-case escalation?
4. Identify all stakeholder groups and prioritize communication order
5. Draft holding statement for immediate release (within first hour)
6. Draft tailored messaging per stakeholder: customers, employees, media, partners, social media
7. Build communication timeline: first hour, first 24 hours, first week, ongoing
8. Define channel strategy: which messages go where (social, email, press, internal comms)
9. Outline recovery plan: corrective actions, transparency updates, trust-rebuilding initiatives
10. Set monitoring cadence and escalation triggers

## Output

A structured crisis response plan containing:

- Severity classification with rationale
- Situation assessment and narrative analysis
- Holding statement (ready to publish)
- Stakeholder-specific messaging (customers, media, employees, partners)
- Communication timeline with milestones and decision points
- Channel deployment plan
- Social media response guidelines (what to reply, what to ignore, when to escalate)
- Recovery and trust-rebuilding roadmap
- Monitoring plan with escalation triggers

## Agents Used

- **brand-guardian** — Brand protection, messaging consistency, stakeholder communication, compliance
- **pr-outreach** — Media relations, press statement, journalist engagement strategy

Attribution

indranilbanerjeeindranilbanerjee
View sourceSee grades on GitHubMore from indranilbanerjee →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →