本文へ移動
cccskills
無料GitHub で公開

66-crisis-playbook-global

Use when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an escalation matrix, a do-not-do list, holding statements, and a post-mortem. Trigger on 'PR crisis', 'crisis playbook', 'a complaint is going viral', 'bad reviews are spreading', 'our content caused backlash', 'we are getting attacked online'. Also use when the user forwards an angry thread and asks what to do right now. Not for — monitoring before anything blows up, see `15-social-listening-global`; diagnosing weak performance numbers, see `03-performance-eval-global`; the routine post-campaign review, see `63-campaign-retrospective-global`.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md10.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Crisis Playbook (Global)

A crisis arrives without warning, so the playbook must exist before it is needed. Three ground rules: (1) do not react before you have facts — most crises look worse than they are in the first 30 minutes; (2) do not stay silent past 4 hours on a spreading crisis, because silence reads as admission; (3) handled well, a crisis builds trust; handled badly, it destroys it permanently.

Information gathering

Read the 15-social-listening-global report if available (early detection). Before doing anything, answer 4 questions:

  1. What type of crisis is this? Match it against the L1-L5 table below.
  2. How fast is it spreading? Ten people or ten thousand? One channel, or has it jumped channels?
  3. Where did it start? An unhappy customer, a creator or influencer, a competitor, a regulator, or the press?
  4. What is actually true? Which fact is disputed, do you have evidence, and do you have enough to respond at all?

If you do not have enough information: publish one short line confirming you are investigating and commit to a specific update time. Do not go silent, and do not respond to unverified claims.

Principles

  1. Assess first, react second. Thirty to sixty minutes of investigation beats a wrong answer in five minutes.
  2. Never silent past 4 hours on a spreading crisis.
  3. Do not delete legitimate negative comments (clear spam and hate speech excepted) — deleting escalates.
  4. Do not argue in public. Move the complainant to a private channel.
  5. Do not respond while emotional. Draft it, wait 30 minutes, reread, then send.
  6. Do not promise what you cannot deliver, and do not minimize the facts.
  7. L3 and above must go to the leader. Never self-handled.
  8. Regulated categories escalate straight to legal. In health, finance, insurance, credit, and crypto, any challenge to a claim goes directly to legal review — do not draft a public response first.

Crisis classification

LevelTypeExamplePriorityResponse window
L1Operational — campaign or system failure, severe KPI missAds not delivering, landing page down, tracking brokenHigh2-4 hours
L2Content — inaccurate or misleading content publishedMisleading caption, wrong figure, inappropriate imageHigh2-4 hours
L3Reputation — customer complaint spreadingViral one-star review, exposé threadCritical1-2 hours
L4Brand attack — coordinatedMass fake reviews, competitor smear, brigadingCriticalSame day
L5Legal / compliance / dataDeceptive-advertising or undisclosed-endorsement complaint, personal data breach, IP infringement, platform enforcement actionCritical + counselImmediate

Process by level

L1 — Operational

In the first 2 hours: pull the full data set to find where the real number sits; diagnose the root cause (run 03-performance-eval-global); notify leadership with a hypothesis and actions; deploy the emergency fix.

Report template: "Campaign [X] is at [actual] against a target of [target]. Preliminary cause: [hypothesis]. In progress: [3 actions]. Next update at [time]."

L2 — Content

Immediately: screenshot and archive the evidence BEFORE removing anything; take down the affected post (faster than apologizing on the broken post); notify the leader, do not self-handle.

Within 2-4 hours: establish what was wrong, who was affected, and the reach; draft the response and have the leader approve it before posting (run 62-marketing-review-global).

Response template: "We found that [content X] in our [date] post contained [an error / inaccurate information]. We have [removed / corrected] it and apologize for the confusion. The correct information is: [...]. Thanks to [the person who flagged it] for raising it."

L3 — Reputation

Immediately: do NOT delete comments, do NOT argue in public, archive all evidence with timestamps.

Within 1-2 hours: verify whether the complaint is legitimate.

  • If legitimate: acknowledge, apologize, fix, compensate. Template: "[Name], we're sorry about this experience. That is not the standard we intend. Could you send us a direct message so we can resolve it with you directly?"
  • If not legitimate: state the facts calmly with evidence, and do not escalate the tone.

Note: in US and EU markets, review platforms are part of the crisis surface. Respond on the platform where the complaint lives, and never incentivize or suppress reviews to offset it — that is itself an FTC issue.

L4 — Brand attack

Archive evidence with timestamps; notify leadership immediately; weigh staying silent (a small-scale attack is amplified by responding) against speaking up (if it is spreading); never respond emotionally; report coordinated inauthentic behavior through the platform's own reporting flow; consult counsel if there are signs of defamation.

L5 — Legal, compliance, and data

Stop every related campaign IMMEDIATELY. Notify leadership. Consult counsel before doing anything else, and make no public statement before legal input. Route by trigger:

TriggerFirst move
Claim challenged as deceptive, or an endorsement ran without disclosurePause the asset, pull the substantiation file and the creator contract, route to counsel. FTC exposure attaches to the advertiser, not only the creator
Personal data exposed or accessed without authorizationNotify your data protection lead or counsel the moment you become aware. Under GDPR a controller has a 72-hour duty to report a qualifying breach to the supervisory authority, and affected individuals must be told without undue delay where the risk is high. Do not wait for full facts to start the clock
California or other US state privacy complaint (CCPA/CPRA and equivalents)Route to counsel; preserve the request and response record, do not respond ad hoc
Platform policy enforcement (account restricted, ads disapproved at scale, page unpublished)Do not spin up backup accounts. File the platform appeal, document the disputed asset, and fix the underlying policy issue
Regulated category (health, finance, insurance, credit, crypto)Any claim issue escalates straight to legal review before any response is drafted

This playbook coordinates the response. It does not give legal advice, and it does not replace counsel on any of the triggers above.

Escalation matrix

LevelHandled byWho must knowTimeline
L1Media buyer + leaderLeadership same day2-4 hours
L2Content + leaderLeadership if reach > 10K2-4 hours
L3LeaderLeadership immediately1-2 hours
L4Leadership + leaderBoard or executive team if neededSame day
L5Leadership + counselBoard or executive team, plus the data protection lead for any data incidentImmediate

Do-not-do list

  • Delete legitimate negative comments.
  • Argue or trade emotional replies with an angry person.
  • Respond before verifying the facts.
  • Promise compensation or a fix you may not be able to deliver.
  • Lie, or downplay the severity.
  • Stay silent past 4 hours while a crisis spreads.
  • Let a junior decide the response at L2 or above.
  • Buy, incentivize, or suppress reviews to offset negative sentiment.
  • Open replacement ad accounts to work around a platform enforcement action.
  • Make a public statement on a legal or data matter before counsel has seen it.

Output structure

# Crisis Response — [Incident name] — [Date/time]

## 1. Initial assessment
| Item | Content |
|------|---------|
| Classification | L[1-5] — [type] |
| Origin | |
| Current scale | [estimated reach, number of channels] |
| Verified facts | |
| Unverified claims | |

## 2. Hour-by-hour response plan
| Time window | Action | Owner | Status |
|-------------|--------|-------|--------|
| 0-1h | | | |
| 1-4h | | | |
| 4-24h | | | |
| Day 2-7 | | | |

## 3. Messaging
Approved to say: [...]
Not to say: [...]
Single spokesperson: [...]
Channels used: [...]

## 4. Internal actions
| Task | Owner | Deadline |
|------|-------|----------|

## 5. Monitoring
| Metric | Before | After 24h | After 7 days |
|--------|--------|-----------|--------------|
| Sentiment | | | |
| Mention volume | | | |
| Inbox / complaints | | | |

After the crisis

After one week: write the post-mortem (what happened, how it was handled, the outcome), update this playbook with the new lessons, and run a team session so it does not repeat. If the crisis was campaign-related, fold it into 63-campaign-retrospective-global.

Related skills

  • 15-social-listening-global: early detection before it becomes a crisis, and sentiment tracking during and after.
  • 03-performance-eval-global: root-cause diagnosis for L1 operational crises.
  • 62-marketing-review-global: approve the response content before publishing.
  • 63-campaign-retrospective-global: extract systemic lessons once it is resolved.
  • 07-marketing-report-global: report the impact on monthly KPIs.

Quality checklist

  • Classified to the correct level before responding
  • Evidence archived with timestamps before anything was removed
  • Facts in the response verified
  • Response approved by the leader (mandatory at L2 and above)
  • Single spokesperson — not several people answering differently
  • Nothing on the do-not-do list was done
  • Legal, data, and platform-enforcement triggers routed to counsel before any public statement
  • Sentiment monitoring scheduled at 24 hours and 7 days
  • Post-mortem scheduled within one week

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Dung khi can ke hoach marketing tong the cho mot ky — muc tieu, phan khuc, kenh, ngan sach, timeline, KPI va ma tran rui ro. Co ca che do ban day du va che do ke hoach 1 trang cho chu doanh nghiep nho. Kich hoat khi user nhac 'lap ke hoach marketing', 'ke hoach MKT', 'marketing plan', 'chien luoc marketing nam', 'plan quy toi', 'ke hoach 1 trang'. Khong dung cho — tinh nguoc ngan sach tu doanh thu thi dung skill 10-tinh-kpi-nguoc; phan bo ngan sach chi tiet theo kenh thi dung skill 61-budget-planning; brief mot chien dich cu the thi dung skill 02-brief-chien-dich.

日本語の概要は準備中です。原文の説明を表示しています。

minhnv0807/ai-business-skills6132026年9月12日 更新

Use when the user needs an overall marketing plan for a period — objectives, segments, positioning, channel mix, content direction, budget, timeline, KPIs, and a risk matrix, adapted to US, EU, SEA, or LATAM. Trigger on 'marketing plan', 'marketing strategy for next year', 'go-to-market roadmap', 'plan for Q3', 'we have no marketing plan', 'where should we spend next quarter'. Also use when a founder only says the business needs to grow and has no idea which channel to start with. Not for — one specific campaign, see `02-campaign-brief-global`; working backward from a revenue goal to spend, see `10-reverse-kpi-global`; splitting a budget across channels and months, see `61-budget-planning-global`; taking a brand new product to market, see `59-go-to-market-global`.

日本語の概要は準備中です。原文の説明を表示しています。

minhnv0807/ai-business-skills6132026年9月12日 更新

Use when the user needs a monthly or weekly content calendar — posting schedule per channel, funnel ratio, content pillars, repurposing matrix, and an owner per slot. Trigger on 'content calendar', 'posting schedule', 'what should we post this month', 'editorial calendar', 'social media plan', 'we post randomly with no plan'. Also use when the user only says the team keeps running out of things to post. Not for — the brief for one specific post, see `36-content-brief-global`; the caption text itself, see `37-social-caption-global`; deciding next period content from last period data, see `40-next-content-plan-global`; a paid campaign timeline, see `02-campaign-brief-global`.

日本語の概要は準備中です。原文の説明を表示しています。

minhnv0807/ai-business-skills6132026年9月12日 更新

Dung khi can lich dang bai cho ca thang — chot content pillar va ti le, xep bai theo ngay va khung gio, ma tran tai su dung noi dung, va gan muc tieu cho tung tru cot. Kich hoat khi user nhac 'lich noi dung', 'content calendar', 'thang nay dang gi', 'len lich dang bai', 'ke hoach content thang', 'phan bo noi dung'. Khong dung cho — brief tung bai truoc khi viet thi dung skill 36-content-brief; viet caption thanh pham thi dung skill 37-caption-social; lap plan ky sau tu data thi dung skill 40-next-content-plan.

日本語の概要は準備中です。原文の説明を表示しています。

minhnv0807/ai-business-skills6132026年9月12日 更新

Dung khi can brief mot chien dich cu the cho ca team thuc thi — muc tieu, thong diep, deliverable, timeline phan cong theo tuan, gate duyet va ma tran rui ro. Kich hoat khi user nhac 'brief chien dich', 'ke hoach campaign', 'len brief cho team', 'chien dich thang toi', 'phan cong campaign', 'timeline chien dich'. Khong dung cho — ke hoach marketing ca ky thi dung skill 00-ke-hoach-mkt; danh sach asset can thiet ke thi dung skill 41-campaign-asset-list; giao viec cho tung nguoi thi dung skill 64-team-brief.

日本語の概要は準備中です。原文の説明を表示しています。

minhnv0807/ai-business-skills6132026年9月12日 更新

Use when a specific campaign needs a brief the whole team can execute from — context, objective, audience, core message, creative direction, channels, deliverables, week-by-week timeline, approval gates, and risks. Trigger on 'campaign brief', 'creative brief', 'launch brief', 'brief the team on this campaign', 'we are running a promo next month', 'what is the plan for this campaign'. Also use when the user describes a promotion out loud and asks for something the team can actually run. Not for — the whole period plan, see `00-marketing-plan-global`; the list of design files needed, see `41-campaign-asset-list-global`; assigning work to one person, see `64-team-brief-global`; a new product launch sequence, see `59-go-to-market-global`.

日本語の概要は準備中です。原文の説明を表示しています。

minhnv0807/ai-business-skills6132026年9月12日 更新

minhnv0807 のスキルをすべて見る

このスキルの問題を報告する