Crisis Management Platform Skill
SkillMonitoring & opsCrisis response platform integration and real-time monitoring
Use Crisis Management Platform Skill in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Crisis Management Platform Skill and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Crisis Management Platform Skill skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by a5c-ai/babysitter in library/specializations/domains/business/public-relations/skills/crisis-management-platform/SKILL.md and read by ahel’s review.
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
- Test Regularly: Conduct crisis drills at least quarterly
- Maintain Assets: Keep holding statements and templates current
- Clear Escalation: Define clear escalation paths and authority
- Document Everything: Log all actions and decisions
- Speed Matters: Reduce detection-to-response time continuously
- 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)
Signals
- GitHub stars
- 2k
- Forks
- 112
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
crisis-management-platform- Source
- github.com/a5c-ai/babysitter
Related picks
Skill · thedaviddias
The pick for JavaScriptmodern-javascript-patterns
Skill · wshobson
The pick for JavaScriptslack-gif-creator
Skill · anthropics
The pick for Slackhive.slack-notifications-setup
Skill · aden-hive
The pick for Slackservice-itsm-teams-configure
Skill · forcedotcom
The pick for Teamsms-teams-apps
Skill · alinaqi
The pick for Teams