skills/pr-crisis-response/SKILL.md
Build a crisis communications plan to respond fast and credibly when something goes wrong. Use when asked to handle a PR crisis, draft a crisis comms plan, respond to a public backlash/scandal/incident, or prepare holding statements. Produces a crisis comms plan — situation assessment, stakeholder map, a message house, channel-by-channel statements, a holding statement, an internal brief, and a follow-up timeline.
npx skillsauth add mohitagw15856/pm-claude-skills pr-crisis-responseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
In a crisis, silence reads as guilt and a clumsy statement makes it worse. The first hour decides the narrative. This skill produces a coordinated response — what you say, to whom, on which channel, and in what order — anchored in one consistent message so the company speaks with a single voice while the facts are still moving.
You'll often get the situation in a sentence ("a customer's data was exposed and it's trending"). Produce the full plan anyway — infer the likely stakeholders, channels, and questions, label assumptions, and clearly flag where facts must be confirmed before publishing. Never stall for complete information; a crisis plan with labelled unknowns beats no plan. Mark anything legally sensitive for review.
Ask for these only if they aren't already provided (else infer and label):
1. Situation assessment — the facts (confirmed / unconfirmed / unknown), severity, and the likely trajectory.
2. Guiding principles — be fast, honest, human, and consistent; lead with the people affected, not the company.
3. Stakeholder map — who needs to hear from you, in priority order, and what each one needs:
| Audience | What they care about | Channel | Priority | |---|---|---|---| | Affected customers | am I harmed, what now | direct email / in-app | 1 | | Employees | what do I tell people | internal note | 1 | | Press / public | what happened, accountability | statement / social | 2 | | Regulators / partners | obligations, next steps | direct, formal | as required |
4. Message house — the single core message (one sentence), three supporting pillars (accountability, action, prevention), and the facts that back each. Everything else stays consistent with this.
5. Holding statement — a short, publishable-now statement that acknowledges, shows you're acting, and commits to an update by a stated time — without speculating or admitting unverified fault.
6. Channel statements — tailored versions for the priority channels (customer email, social post, press statement, internal brief), each on-message.
7. Q&A prep — the hardest questions you'll be asked and honest, on-message answers (incl. "what we don't yet know").
8. Follow-up timeline — when the next update comes, who owns it, and the criteria for standing down.
Crisis communications practice — single-source-of-truth messaging, stakeholder prioritisation, holding statements, and accountable, people-first response.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.