Crisis Management Platform Integration

VerifiedCaution

Integration of crisis management platforms and real-time monitoring for coordinated response and incident documentation.

Sby Skills Guide Bot
ContentIntermediate
8/8/2026
Claude Code
#crisis-communications#public-relations#incident-response#real-time-monitoring#stakeholder-comms

Recommended for

Automated summary

This skill covers crisis management platform integration and real-time monitoring, from signal detection through coordinated response and post-crisis review.

Strengths

  • Defines tiered escalation with associated triggers and notification lists.
  • Spans the full crisis lifecycle: detection, multi-channel coordination, logging, and post-crisis analysis.
  • Includes operational assets such as holding statements, dark sites, and communication templates.

Limitations

  • Depends on external APIs (media and social monitoring, Slack/Teams, dark site) and access rights that are not detailed.
  • Provides configuration examples and illustrative objects rather than a complete implementation with endpoints or authentication.
  • Thresholds, templates, and channels must be tailored to each organization and vetted by legal and communications teams.
When to use it

Use it when an organization needs to structure or automate crisis detection and multi-channel response coordination.

When not to use it

Avoid it for routine monitoring or when the required external platforms and channels are unavailable.

Security analysis

Caution
Quality score72/100

The skill is essentially a documentation/spec file for crisis communications workflows. It includes no destructive, exfiltration, or obfuscated instructions, and the code blocks are inert illustrative objects. The risk is limited to its declared Bash and WebFetch grants, which could allow arbitrary command execution and outbound network calls if an agent applies the skill, so it is caution rather than safe.

Findings
  • •Declares Bash and WebFetch without any scoping, allowlist, or usage guidance; an agent following this skill could run arbitrary shell commands or make network requests to third-party platform APIs under minimal supervision.
  • •Contains no actual executable commands or scripts; the javascript blocks are illustrative configuration/data objects only, so execution risk comes from the tool grants rather than the content itself.
  • •No handling guidance for the sensitive data the skill traffics in (incident IDs, breach details, stakeholder/regulator notifications), which is a privacy/confidentiality gap rather than a direct attack vector.
  • •No prompt-injection or role-override attempts observed in the content.
  • •Declares Bash and WebFetch but the skill body contains no commands, network calls, or scripts that use them
  • •No destructive, exfiltration, obfuscation, or safety-disabling instructions present
How this analysis is made

Examples

Configure tiered crisis alerts
Set up a crisis monitoring dashboard with a tier-1 alert for data-breach and regulatory-action mentions that immediately notifies the CCO, CEO, legal, and the crisis team.
Activate breach response
We just detected a potential data breach. Activate the crisis response workflow: notify the crisis team, open the #crisis-war-room Slack channel, and prepare the data-breach holding statement.
Generate post-crisis report
Create a post-crisis report for INC-2026-001 with a reconstructed timeline, response-time metrics, and lessons learned.

name: crisis-management-platform description: Crisis response platform integration and real-time monitoring allowed-tools:

  • Read
  • Write
  • Glob
  • Grep
  • Bash
  • WebFetch metadata: specialization: public-relations domain: business category: Crisis Communications skill-id: SK-005 dependencies:
    • Crisis management platform APIs
    • Slack/Teams APIs graph: domains: [domain:public-relations] skillAreas: [skill-area:brand-strategy, skill-area:incident-management, skill-area:brand-positioning] roles: [role:marketing-strategist, role:marketing-manager, role:brand-manager]

Crisis Management Platform Skill

Overview

The Crisis Management Platform skill provides crisis response platform integration and real-time monitoring capabilities. This skill enables rapid crisis detection, coordinated response, and comprehensive documentation throughout crisis situations.

Capabilities

Monitoring and Detection

  • Crisis monitoring dashboard configuration
  • Real-time alert escalation
  • Multi-channel signal detection
  • Threshold-based triggering
  • Pattern recognition for emerging issues

Response Coordination

  • Stakeholder notification system integration
  • Holding statement rapid deployment
  • Multi-channel response coordination
  • Team collaboration tools integration
  • Role-based access and assignments

Digital Infrastructure

  • Dark site activation management
  • Social media response queuing
  • Website messaging updates
  • Email communication triggers
  • Hotline message coordination

Documentation and Logging

  • Incident logging and documentation
  • Response time tracking
  • Decision audit trail
  • Media inquiry tracking
  • Stakeholder communication log

Post-Crisis Analysis

  • Post-crisis report generation
  • Timeline reconstruction
  • Response effectiveness analysis
  • Lessons learned documentation
  • Plan update recommendations

Usage

Crisis Dashboard Configuration

const crisisDashboardConfig = {
  monitoringSources: {
    media: ['cision', 'meltwater'],
    social: ['sprinklr', 'talkwalker'],
    internal: ['employee-hotline', 'customer-service'],
    regulatory: ['sec-filings', 'fda-alerts']
  },
  alertTiers: {
    tier1: {
      triggers: ['executive-mention-negative', 'regulatory-action', 'data-breach'],
      escalation: 'immediate',
      notification: ['cco', 'ceo', 'legal', 'crisis-team']
    },
    tier2: {
      triggers: ['product-issue', 'employee-incident', 'competitor-attack'],
      escalation: '15min',
      notification: ['comms-director', 'pr-manager']
    },
    tier3: {
      triggers: ['negative-review-spike', 'social-complaint-surge'],
      escalation: '1hr',
      notification: ['social-team', 'customer-service']
    }
  },
  collaboration: {
    platform: 'slack',
    channels: {
      warRoom: '#crisis-war-room',
      mediaInquiries: '#media-inquiries',
      socialResponse: '#social-response'
    }
  },
  assets: {
    holdingStatements: ['data-breach', 'product-recall', 'executive-departure'],
    darkSites: ['incident-response.company.com'],
    templates: ['employee-comm', 'customer-comm', 'media-statement']
  }
};

Crisis Response Execution

const crisisResponse = {
  incident: {
    id: 'INC-2026-001',
    type: 'data-breach',
    detectedAt: '2026-02-15T14:30:00Z',
    severity: 'tier1',
    status: 'active'
  },
  actions: [
    { time: '14:30', action: 'Alert triggered', owner: 'system' },
    { time: '14:32', action: 'Crisis team notified', owner: 'system' },
    { time: '14:45', action: 'War room activated', owner: 'CCO' },
    { time: '15:00', action: 'Holding statement approved', owner: 'Legal' },
    { time: '15:15', action: 'Dark site activated', owner: 'Digital' },
    { time: '15:30', action: 'Employee communication sent', owner: 'Internal Comms' },
    { time: '16:00', action: 'Press statement released', owner: 'Media Relations' }
  ],
  metrics: {
    detectionToNotification: '2min',
    notificationToActivation: '13min',
    activationToStatement: '45min',
    mediaInquiriesReceived: 15,
    socialMentions: 450,
    employeeQuestions: 89
  },
  stakeholders: {
    media: { contacted: 15, responded: 12 },
    employees: { notified: 'all', questions: 89 },
    customers: { notified: 'affected', inquiries: 234 },
    regulators: { notified: true, filingRequired: true }
  }
};

Process Integration

This skill integrates with the following PR processes:

| Process | Integration Points | |---------|-------------------| | crisis-communications-plan.js | Plan activation | | crisis-response-execution.js | Response coordination | | crisis-simulation-training.js | Training scenarios | | post-crisis-analysis.js | Analysis and reporting |

Best Practices

  1. Test Regularly: Conduct crisis drills at least quarterly
  2. Maintain Assets: Keep holding statements and templates current
  3. Clear Escalation: Define clear escalation paths and authority
  4. Document Everything: Log all actions and decisions
  5. Speed Matters: Reduce detection-to-response time continuously
  6. Post-Mortem: Always conduct thorough post-crisis analysis

Metrics and KPIs

| Metric | Description | Target | |--------|-------------|--------| | Detection Time | Time to detect crisis | <15 minutes | | Response Time | Detection to first response | <1 hour | | Stakeholder Notification | Time to notify key stakeholders | <30 minutes | | Message Consistency | Alignment across channels | 100% | | Resolution Time | Time to crisis resolution | Minimized |

Related Skills

  • SK-001: Media Monitoring (detection)
  • SK-002: Social Listening (social detection)
  • SK-013: Media Training Simulation (preparation)

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/crisis-management-platform-integration-msjwk4uy/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/crisis-management-platform-integration-msjwk4uy' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/crisis-management-platform-integration-msjwk4uy/download' --output '.skill-downloads/crisis-management-platform-integration-msjwk4uy/SKILL.md.part' && mv '.skill-downloads/crisis-management-platform-integration-msjwk4uy/SKILL.md.part' '.skill-downloads/crisis-management-platform-integration-msjwk4uy/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/crisis-management-platform-integration-msjwk4uy/SKILL.md' && test -s '.skill-downloads/crisis-management-platform-integration-msjwk4uy/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/crisis-management-platform' && cp -R '.skill-downloads/crisis-management-platform-integration-msjwk4uy' '.claude/skills/crisis-management-platform'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/crisis-management-platform-integration-msjwk4uy'

openskills read 'crisis-management-platform-integration-msjwk4uy'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/crisis-management-platform-integration-msjwk4uy/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills