disruption-response-coordinator
Supply chain disruption rapid response skill with impact assessment and mitigation activation
Best use case
disruption-response-coordinator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Supply chain disruption rapid response skill with impact assessment and mitigation activation
Teams using disruption-response-coordinator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/disruption-response-coordinator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How disruption-response-coordinator Compares
| Feature / Agent | disruption-response-coordinator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Supply chain disruption rapid response skill with impact assessment and mitigation activation
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Disruption Response Coordinator
## Overview
The Disruption Response Coordinator manages rapid response to supply chain disruptions. It provides structured incident classification, impact assessment, mitigation activation, stakeholder communication, and recovery tracking to minimize disruption impact.
## Capabilities
- **Incident Classification and Escalation**: Severity-based incident categorization
- **Impact Assessment**: Supply, demand, and financial impact analysis
- **War Room Coordination**: Cross-functional response team orchestration
- **Mitigation Option Activation**: Contingency plan execution
- **Stakeholder Communication**: Internal and external communication management
- **Recovery Tracking**: Progress monitoring toward normal operations
- **Lessons Learned Capture**: Post-incident documentation
- **Post-Incident Analysis**: Root cause and improvement identification
## Input Schema
```yaml
disruption_response_request:
incident:
incident_id: string
type: string # supplier, logistics, demand, natural disaster
description: string
affected_entities: array
detection_time: datetime
reported_by: string
initial_assessment:
estimated_duration: string
affected_products: array
affected_customers: array
financial_exposure: float
available_mitigations:
alternative_suppliers: array
buffer_inventory: object
demand_management: array
communication_requirements:
internal_stakeholders: array
external_stakeholders: array
regulatory_notifications: array
```
## Output Schema
```yaml
disruption_response_output:
incident_classification:
severity: string # Minor, Moderate, Major, Critical
escalation_level: string
incident_commander: string
impact_assessment:
supply_impact:
affected_skus: array
shortage_forecast: object
demand_impact:
affected_customers: array
revenue_at_risk: float
financial_impact:
total_exposure: float
breakdown: object
response_plan:
activated_mitigations: array
action_items: array
- action: string
owner: string
due_date: datetime
status: string
war_room_schedule: object
communication_log:
internal_updates: array
external_communications: array
regulatory_notifications: array
recovery_tracking:
current_status: string
milestones: array
estimated_recovery_date: date
progress_percentage: float
lessons_learned:
root_cause: string
what_worked: array
improvement_opportunities: array
action_items: array
```
## Usage
### Incident Classification
```
Input: Disruption event details, affected scope
Process: Classify severity, determine escalation
Output: Incident classification with response level
```
### Impact Assessment
```
Input: Affected suppliers/products, demand data
Process: Model supply shortage, customer impact
Output: Quantified impact assessment
```
### Mitigation Activation
```
Input: Available alternatives, contingency plans
Process: Select and activate appropriate mitigations
Output: Active mitigation plan with assignments
```
## Integration Points
- **Incident Management Systems**: Ticketing, escalation
- **Communication Platforms**: Notification, collaboration
- **Supply Chain Systems**: Inventory, order management
- **Tools/Libraries**: Incident management, communication tools
## Process Dependencies
- Supply Chain Disruption Response
- Business Continuity and Contingency Planning
- Supplier Risk Monitoring and Early Warning
## Best Practices
1. Establish clear severity criteria upfront
2. Pre-define escalation paths and thresholds
3. Maintain updated contact lists
4. Practice response through simulations
5. Communicate early and often during incidents
6. Conduct thorough post-incident reviewsRelated Skills
dock-scheduling-coordinator
Automated dock appointment scheduling skill with inbound flow optimization and receiving efficiency management
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.