← Back to list
crisis-response-planner ✓ Security reviewed
Use when the user asks to "build our social crisis protocol", "mentions are exploding — what do w…
⚡ Productivity By aaron-he-zhu Version v1.0.0 Updated 2026-09-03
7.3Overall rating

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "crisis-response-planner" skill by following the instructions at https://skill123.me/install/crisis-response-planner.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/crisis-response-planner.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 5 KB

About this skill

Overview

Use when the user asks to "build our social crisis protocol", "mentions are exploding — what do we do first", or "when do we pause the posting queue"; produces a 1-5 severity ladder with tunable Estimated trigger thresholds (mention-velocity multiples vs the 7-day listening baseline, sentiment flip, journalist/regulator contact, employee-conduct class), the first-mechanical-action rule — pause ALL scheduled posts AND paid amplification, with dated state markers dropped to the channels proposal protocol and reconciled post-incident — a pre-approved holding-statement library with committed update cadences, when-NOT-to-post rules, a spokesperson/approval matrix, and a post-crisis retro template; re-runs the social-quality-auditor pre-publish gate before un-pausing the queue. Not for email deliverability incidents (blocklist, spam-rate spikes) — use deliverability-qa; inside a launch window launch-day-conductor owns incident handling. 社媒危机预案/暂停队列/声明库/发言人矩阵

Source

  • Repo: https://github.com/aaron-he-zhu/aaron-marketing-skills
  • Path: social/host/crisis-response-planner

Evaluation

AI-evaluated 2026-09-03: Concrete 1-5 severity ladder with velocity triggers, pause-the-queue rule with receipts, holding-statement library, and stand-down workflow. Crisis protocol drafting is a real if occasional need; ecosystem coupling again raises prerequisites; safety is excellent with human-only actions, no silent deletions, and legal routing.

Score breakdown

Quality
8.0
Usability
6.0
Security
8.0
Popularity
7.0