Crisis Management & Communications Playbook
v1.0.0Helps organizations detect crises early, assess severity and type, activate response teams, and communicate effectively to manage reputation and operational...
⭐ 0· 470·2 current·2 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The SKILL.md and README provide crisis detection, severity matrices, team activation checklists, templates, and recovery plans that align with the skill's stated purpose. There are no unrelated environment variables, binaries, or install steps requested that would be inconsistent with a crisis playbook.
Instruction Scope
The instructions are largely procedural and template-driven (assessments, checklists, templates). They recommend continuous monitoring of external sources (Twitter, LinkedIn, Reddit, Glassdoor, Google Alerts, etc.), but the skill does not include connectors, API calls, or commands to fetch that data. Because monitoring is described at a conceptual level, an agent following this playbook might later request credentials or integration access to implement monitoring — the SKILL.md itself does not instruct reading local files, secrets, or transmitting data to unknown endpoints.
Install Mechanism
No install spec and no code files are present; this is instruction-only. That reduces the risk of arbitrary code being written or executed on the host.
Credentials
The skill declares no required environment variables, credentials, or config paths, which is proportionate for a playbook. However, practical use (automated monitoring, posting statements, or notifying regulators) would require external service credentials or integrations that are not declared here — be prepared to provide those deliberately and review any future permission requests before granting access.
Persistence & Privilege
always is false and the skill does not request system-level persistence or modification of other skills. Autonomous invocation is allowed (platform default), so ensure human review for any externally visible communications generated by the agent.
Assessment
This playbook is coherent and appears to be a content/template skill rather than executable code — it won't access anything by itself. Before installing or using it: (1) understand it gives procedural advice but does not implement monitoring or communications; to automate those you will need to connect third-party services and provide API keys or accounts — only grant those deliberately and to trusted integrations, (2) do not allow the agent to publish statements or contact journalists/regulators without human approval (the templates it drafts are helpful but legally sensitive), (3) verify the publisher/source before purchasing any paid context packs or following regulatory guidance (source/homepage are minimal), and (4) if you plan to use it for regulated incidents (HIPAA, GDPR, SEC), have your legal/compliance team review its advice and any outputs before you act.Like a lobster shell, security has layers — review code before you run it.
communicationsvk97e82y4v0x8yncq0hpg38cwbh81s7wvcrisisvk97e82y4v0x8yncq0hpg38cwbh81s7wvincident-responsevk97e82y4v0x8yncq0hpg38cwbh81s7wvlatestvk97e82y4v0x8yncq0hpg38cwbh81s7wvlegalvk97e82y4v0x8yncq0hpg38cwbh81s7wvmediavk97e82y4v0x8yncq0hpg38cwbh81s7wvprvk97e82y4v0x8yncq0hpg38cwbh81s7wvreputationvk97e82y4v0x8yncq0hpg38cwbh81s7wv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.