crisis-detector
Identify early warning signals of potential PR crises through pattern recognition, escalation triggers, and risk assessment
What this skill does
# Crisis Detector > Identify early warning signs of potential crises before they escalate through pattern recognition, signal monitoring, and risk assessment. ## When to Use This Skill - Setting up early warning systems - Assessing crisis probability - Training teams on signals - Building escalation criteria - Post-crisis prevention planning ## Methodology Foundation Based on **Institute for Crisis Management research** and **Burson crisis frameworks**, combining: - Signal identification - Pattern recognition - Risk assessment matrices - Escalation protocols ## What Claude Does vs What You Decide | Claude Does | You Decide | |-------------|------------| | Identifies warning signals | Risk tolerance | | Assesses crisis probability | Response resources | | Creates detection criteria | Escalation authority | | Designs monitoring systems | Communication strategy | | Suggests response triggers | Final action calls | ## Instructions ### Step 1: Map Crisis Types **Crisis Categories:** | Category | Examples | Warning Time | |----------|----------|--------------| | **Operational** | Outage, product failure | Hours to days | | **Reputational** | Executive scandal, viral complaint | Minutes to hours | | **Legal/Regulatory** | Lawsuit, investigation | Days to weeks | | **Financial** | Earnings miss, fraud | Hours to days | | **Human** | Workplace incident, harassment | Hours to days | | **External** | Natural disaster, market crash | Variable | ### Step 2: Identify Early Signals **Signal Types:** | Signal Type | Examples | Monitoring | |-------------|----------|------------| | **Internal** | Employee complaints, support tickets | HR, Support data | | **Customer** | Review patterns, churn spikes | CX metrics | | **Social** | Mention volume, sentiment shift | Social tools | | **Media** | Press inquiries, journalist interest | PR inbox | | **Regulatory** | Compliance notices, audit findings | Legal | | **Financial** | Payment disputes, refund requests | Finance | ### Step 3: Build Detection Matrix **Signal Strength Assessment:** | Signal | Weak | Moderate | Strong | Critical | |--------|------|----------|--------|----------| | Volume spike | +25% | +50% | +100% | +300% | | Sentiment shift | -10% | -20% | -30% | -50% | | Media inquiries | 1 | 2-3 | 4-5 | 6+ | | Support tickets | +10% | +25% | +50% | +100% | | Social influencer | 10K | 50K | 100K | 500K+ | ### Step 4: Create Escalation Triggers **Trigger Framework:** | Level | Signals Present | Action | |-------|-----------------|--------| | Watch | 1 moderate signal | Monitor closely | | Alert | 2+ moderate or 1 strong | Notify team | | Warning | Multiple strong signals | Assemble team | | Crisis | Any critical signal | Activate protocol | ### Step 5: Document and Improve **Post-Detection Review:** - How early did we detect? - What signals did we miss? - How accurate was assessment? - What should we add to monitoring? ## Examples ### Example 1: Crisis Detection System Design **Input:** ``` Design a crisis detection system for: - E-commerce company (clothing) - 500K customers - Active on Instagram, TikTok, Twitter - Past issue: Shipping delays during holiday ``` **Output:** ``` ## Crisis Detection System: E-Commerce Fashion ### Crisis Risk Map | Crisis Type | Probability | Impact | Priority | |-------------|-------------|--------|----------| | Shipping delays | High | High | P1 | | Product quality issue | Medium | High | P1 | | Social media backlash | Medium | High | P1 | | Data breach | Low | Critical | P1 | | Influencer controversy | Medium | Medium | P2 | | Supply chain disruption | Medium | High | P2 | | Payment fraud | Low | Medium | P3 | --- ### Early Warning Signals #### P1: Shipping Delays **Leading Indicators (3-5 days before crisis):** | Signal | Source | Threshold | |--------|--------|-----------| | Carrier delay reports | Logistics API | >10% delayed | | Warehouse backlog | WMS data | >24hr processing | | Weather events | News/weather | Storm in hub | | "Where's my order" tickets | Support | +50% daily | **Lagging Indicators (crisis starting):** | Signal | Source | Threshold | |--------|--------|-----------| | Social mentions | Social listening | "shipping" +100% | | Review mentions | Trustpilot/G2 | Shipping 3/5 stars | | Refund requests | Payment system | +30% | | Chargeback rate | Payment processor | >1% | --- #### P1: Product Quality Issue **Leading Indicators:** | Signal | Source | Threshold | |--------|--------|-----------| | Return rate spike | Returns data | >10% on SKU | | Quality complaints | Support tickets | 3+ same issue | | Photo complaints | Social | "damaged", "wrong color" | | Batch-specific issues | QC data | Same lot number | **Lagging Indicators:** | Signal | Source | Threshold | |--------|--------|-----------| | Viral unboxing | TikTok/Instagram | >10K views negative | | Review bomb | Product pages | Multiple 1-stars | | Media inquiry | PR inbox | Journalist question | --- #### P1: Social Media Backlash **Leading Indicators:** | Signal | Source | Threshold | |--------|--------|-----------| | Sentiment shift | Social tools | -20% in 24hr | | Controversial post | Your social | Negative comments >10% | | Influencer complaint | Social | >50K follower post | | Screenshot spreading | Twitter/Reddit | Same image 5+ times | **Lagging Indicators:** | Signal | Source | Threshold | |--------|--------|-----------| | Viral negative | Any platform | >50K engagements | | Hashtag trending | Twitter | Brand + negative | | Media pickup | News sites | Article published | | Competitor amplification | Social | Competitor sharing | --- ### Detection Dashboard ``` ┌──────────────────────────────────────────────────────────┐ │ CRISIS DETECTION DASHBOARD 🟢 NORMAL │ ├──────────────────────────────────────────────────────────┤ │ │ │ SHIPPING STATUS 🟢 Normal │ │ ├─ Carrier delays: 3% (threshold: 10%) │ │ ├─ Backlog: 4 hours (threshold: 24hr) │ │ └─ "Where's my order": 45 (baseline: 50) │ │ │ │ PRODUCT QUALITY 🟢 Normal │ │ ├─ Return rate: 5.2% (threshold: 10%) │ │ ├─ Quality tickets: 2 (threshold: 3+ same) │ │ └─ Photo complaints: 1 (threshold: 5) │ │ │ │ SOCIAL SENTIMENT 🟡 Watch │ │ ├─ Sentiment: -15% (threshold: -20%) │ │ ├─ Volume: +40% (threshold: +50%) │ │ └─ Influencer: None flagged │ │ │ │ SECURITY 🟢 Normal │ │ ├─ Login anomalies: Normal │ │ └─ Payment fraud: 0.3% │ │ │ └──────────────────────────────────────────────────────────┘ ``` --- ### Escalation Matrix | Level | Criteria | Notification | Response | |-------|----------|--------------|----------| | 🟢 Normal | All metrics in range | None | Standard ops | | 🟡 Watch | 1 metric at threshold | Slack alert | Increased monitoring | | 🟠 Alert | 2+ metrics or 1 exceeded | Team notification | Standby team | | 🔴 Crisis | Critical threshold breached | All-hands alert | Activate protocol | --- ### Alert Routing | Signal Type | Primary | Backup | Escalation | |-------------|---------|--------|------------| | Shipping | Operations | COO | CEO | | Product quality | Product | VP Ops | CEO | | Social media | Marketing | CMO | CEO | | Security | IT | CTO | CEO + Legal | | Legal/PR | Legal | CEO | Board | --- ### Holiday Season Adjustments During high-volume periods (Nov 15 - Dec 31): | Metric | Normal Threshold | Holiday Threshold | |--------|---------
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.