← Back to Skills Marketplace
harrylabsj

Cb Crisis Communication Protocol

by haidong · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
63
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install cb-crisis-communication-protocol
Description
A response framework for overseas brand, product, service, cultural, or compliance crises across multiple markets and channels.
README (SKILL.md)

Cross-border Crisis Communication Protocol

Overview

A response framework for overseas brand, product, service, cultural, or compliance crises across multiple markets and channels.

This is a pure descriptive OpenClaw skill for overseas expansion planning. It provides frameworks, templates, checklists, decision criteria, and risk reminders. It does not execute code, call APIs, access the network, scrape websites, submit forms, make purchases, send messages, or perform any external action.

When to Use

Use this skill when the user needs structured help with cross-border crisis communication protocol in a cross-border or international expansion context.

Typical trigger phrases include:

  • overseas PR crisis
  • cross-border crisis communication
  • international brand backlash
  • foreign customer complaint crisis
  • global reputation response

Target Users

Founders, PR teams, customer support leads, legal/compliance coordinators, and market managers.

Inputs to Collect

Ask for or infer the following context before producing the final framework:

  • Target market or list of candidate markets
  • Product, service, category, or business model
  • Current business stage and domestic traction, if any
  • Target customer segment and purchase context
  • Expansion goal, timeline, budget range, and constraints
  • Existing assets such as brand story, content, team, channels, customer data, or partners
  • Known risks, assumptions, compliance concerns, and decision deadlines

If important inputs are missing, state the assumptions clearly and provide a version that can be refined later.

Workflow

  1. Classify the issue by severity, market scope, stakeholder harm, legal exposure, misinformation risk, and speed of escalation.
  2. Map affected stakeholders and channels, including customers, creators, partners, regulators, employees, media, communities, and platform audiences.
  3. Create the first-response holding statement with empathy, facts known, facts not yet known, action underway, and next-update timing.
  4. Design localization, approval, and escalation workflow so the response does not contradict local law, cultural expectations, or operational reality.
  5. Plan monitoring, correction, customer support, and post-crisis learning actions that reduce recurrence rather than only closing the PR cycle.

Output Modules

Crisis classification matrix

  • Purpose: turn the user's market context into a structured planning component.
  • Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
  • Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

Stakeholder and channel map

  • Purpose: turn the user's market context into a structured planning component.
  • Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
  • Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

First-response statement template

  • Purpose: turn the user's market context into a structured planning component.
  • Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
  • Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

Localization and approval workflow

  • Purpose: turn the user's market context into a structured planning component.
  • Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
  • Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

Escalation and monitoring plan

  • Purpose: turn the user's market context into a structured planning component.
  • Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
  • Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

Post-crisis learning review

  • Purpose: turn the user's market context into a structured planning component.
  • Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
  • Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

Output Format

Return a structured response with these sections:

  1. Input Summary — what the user provided and what assumptions are being made.
  2. Strategic Diagnosis — key opportunity, constraint, and uncertainty analysis for the overseas context.
  3. Framework Output — the main tables, matrices, checklists, templates, or playbooks generated by this skill.
  4. Market Adaptation Notes — what should change by region, language, channel, customer expectation, or operating model.
  5. Risks and Validation Tasks — assumptions to test, professional review needs, and red flags.
  6. Next Actions — 5–10 practical steps the user can take manually.

Example Prompts

  • Use Cross-border Crisis Communication Protocol for a consumer brand entering Germany and Japan with a limited launch budget.
  • Build a practical overseas expansion framework for our SaaS product using this context: target market, audience, product category, budget, and timeline.
  • Create a cross-border crisis communication protocol for a team that has domestic traction but no local overseas team yet.
  • Help me compare two markets and produce a checklist, decision matrix, and risk notes for overseas PR crisis.

Safety and Limitations

Crisis guidance is strategic communication support only; legal, regulatory, safety, or liability matters require qualified professional counsel.

Additional limitations:

  • No professional legal, tax, financial, medical, employment, investment, or compliance advice.
  • No guarantee of market success, conversion improvement, legal compliance, or platform acceptance.
  • Verify local laws, platform policies, consumer expectations, and current market facts with qualified professionals and reliable sources.
  • Avoid stereotyping cultures or users; treat all cultural observations as hypotheses requiring local validation.

Acceptance Criteria

  • Classifies crisis severity and stakeholder impact
  • Provides first-response templates with adaptation notes
  • Defines approval and escalation roles
  • Includes channel-specific response guidance
  • Adds a post-crisis review checklist
  • Provides structured, market-aware outputs rather than generic overseas expansion advice.
  • Includes explicit assumptions, evidence gaps, and validation steps.
  • Stays pure descriptive with no code execution, API calls, browsing, network access, or external side effects.

Publishing Notes

  • Version: 1.0.0
  • Language: English
  • Type: descriptive
  • Runtime requirements: none
  • External permissions: none
Usage Guidance
This skill appears coherent and descriptive only — it won't run code or call external services. Before using it, avoid pasting customer PII, confidential contracts, privileged legal notes, or secrets into prompts; redact or summarize sensitive material. Remember outputs are strategic guidance, not legal or regulatory advice — consult qualified counsel for compliance or liability questions. If you prefer to prevent the agent from invoking skills autonomously, adjust your agent/skill invocation settings in your platform before enabling the skill.
Capability Tags
cryptocan-make-purchases
Capability Assessment
Purpose & Capability
Name, description, and skill.json all describe a descriptive cross-border crisis-communication framework. There are no required binaries, env vars, config paths, or install steps — which is proportionate for a playbook/template skill.
Instruction Scope
SKILL.md stays within scope and explicitly states it will not execute code or access the network. It asks the agent to 'ask for or infer' context such as market, product, customer data, and risks — that is reasonable for producing tailored frameworks, but 'infer' is vague and could lead the agent to use any conversational context available. The skill does not instruct the agent to read files, environment variables, or external endpoints.
Install Mechanism
No install spec or code files — lowest-risk format. Nothing is downloaded or written to disk by the skill package itself.
Credentials
The skill requests contextual inputs (market, customer segment, existing assets, known risks) but does not request credentials or secrets. Users should avoid pasting sensitive PII, proprietary documents, or legal/confidential material into prompts; the skill's need for contextual business information is legitimate but can overlap with sensitive data if not redacted.
Persistence & Privilege
Flags are default (always: false). The skill does not request permanent presence or elevated privileges and does not modify other skills or system settings. Autonomous invocation is permitted by platform default but is not combined with other risky behaviors.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install cb-crisis-communication-protocol
  3. After installation, invoke the skill by name or use /cb-crisis-communication-protocol
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the Cross-border Crisis Communication Protocol skill: - Provides a structured, descriptive framework for overseas crisis communication across multiple markets and channels. - Includes modules for crisis classification, stakeholder mapping, first-response templates, localization/approval workflow, escalation/monitoring, and post-crisis learning. - Guides users to collect and summarize key market, product, and risk inputs, with clear assumptions if context is missing. - Outputs practical tables, matrices, checklists, and templates tailored for founders, PR teams, compliance, and market managers. - Delivers explicit risk notes, validation steps, and actionable next steps—purely descriptive with no external actions or code execution. - Emphasizes market adaptation, compliance reminders, and the need for local professional review.
Metadata
Slug cb-crisis-communication-protocol
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Cb Crisis Communication Protocol?

A response framework for overseas brand, product, service, cultural, or compliance crises across multiple markets and channels. It is an AI Agent Skill for Claude Code / OpenClaw, with 63 downloads so far.

How do I install Cb Crisis Communication Protocol?

Run "/install cb-crisis-communication-protocol" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Cb Crisis Communication Protocol free?

Yes, Cb Crisis Communication Protocol is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Cb Crisis Communication Protocol support?

Cb Crisis Communication Protocol is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Cb Crisis Communication Protocol?

It is built and maintained by haidong (@harrylabsj); the current version is v1.0.0.

💬 Comments