Agent Skillsmohitagw15856/pm-claude-skills › pr-crisis-response

pr-crisis-response

GitHub

用于快速构建可信的公关危机应对计划。涵盖局势评估、利益相关者地图、核心信息屋、多渠道声明(含即时声明)、问答准备及后续时间表,确保在事实未明时统一发声并明确责任。

exports/openclaw/pr-crisis-response/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

处理公关危机 起草危机沟通计划 回应公众抵制或丑闻事件 准备临时声明

Install

npx skills add mohitagw15856/pm-claude-skills --skill pr-crisis-response -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/exports/openclaw/pr-crisis-response -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@pr-crisis-response

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill pr-crisis-response -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "pr-crisis-response",
    "homepage": "https:\/\/mohitagw15856.github.io\/pm-claude-skills\/skill\/pr-crisis-response.html",
    "metadata": {
        "openclaw": {
            "emoji": "🚨"
        }
    },
    "description": "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."
}

PR Crisis Response Skill

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.

Working from a brief

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.

Required Inputs

Ask for these only if they aren't already provided (else infer and label):

  • What happened — the incident, when, who's affected, and what's confirmed vs. still unknown.
  • Severity & exposure — how serious, who knows, and where it's spreading (press, social, regulators).
  • Organisation — what you do, who your audiences are, and your voice.
  • Constraints — legal/regulatory limits, what you can't say yet, and who must approve.

Output Format

Crisis Response Plan: [situation]

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.

Quality Checks

  • Leads with the people affected and clear accountability, not corporate defensiveness
  • Separates confirmed facts from unknowns — no speculation presented as fact
  • Every channel statement is consistent with the one core message
  • A holding statement is ready to publish now, with a committed time for the next update
  • Internal audience is briefed before/with the external statement, not after
  • Legally sensitive claims are flagged for review, not asserted

Anti-Patterns

  • Do not go silent or delay — issue a holding statement, then update; absence writes the story for you
  • Do not speculate, guess at cause, or admit unverified fault — acknowledge and commit to updates instead
  • Do not let channels drift off-message — one core message, tailored, not contradictory versions
  • Do not forget employees — they're your first responders and they'll hear it anyway
  • Do not over-spin — minimising or blaming others erodes the trust you're trying to keep

Based On

Crisis communications practice — single-source-of-truth messaging, stakeholder prioritisation, holding statements, and accountable, people-first response.

Version History

  • 54fad50 Current 2026-07-19 12:27

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
64fe798e
Indexed
2026-07-19 12:27

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 14:05
浙ICP备14020137号-1 $방문자$