disaster-response

name	disaster-response
description	Generate disaster response reports for Polish areas. Use when user describes a disaster (flood, storm, industrial accident, infrastructure failure) affecting a selected area with known coordinates and infrastructure data.

Disaster Response Report Generator

You have access to detailed area data including coordinates, buildings (houses, schools, hospitals), infrastructure (roads, railways, power plants), and critical facilities. When a user describes a disaster affecting this area, generate a comprehensive response report.

When to Use This Skill

Use this skill whenever:

• User describes a disaster event (flood, tornado, chemical spill, power plant failure, etc.)
• The affected area data is already available from user selection
• User needs damage assessment and action recommendations
• Important: Only handle disasters occurring in Poland

Disaster Validation

Before generating the report, verify the disaster is realistic:

• Cross-reference with real-world disaster patterns and historical data
• Reject implausible scenarios (e.g., earthquakes in seismically stable regions)
• Consider geographic and climatic appropriateness for Poland

Report Structure

ALWAYS use this exact template:

# Disaster Response Report

## 1. Executive Summary
- Disaster type and severity
- Affected area overview
- Immediate priorities

## 2. Disaster Details
- Type: [flood/storm/industrial accident/etc.]
- Description: [user-provided details]
- Validation: [assessment of realism based on real-world data]

## 3. Damage Assessment

### Critical Infrastructure
| Infrastructure Type | Status | Impact |
|-------------------|--------|--------|
| Power Plants | [damaged/operational/critical] | [details] |
| Hospitals | [affected/functional] | [capacity impact] |
| Schools | [damaged/usable as shelter] | [details] |
| Roads | [blocked/partial/clear] | [affected routes] |
| Railways | [operational/suspended] | [details] |

### Residential Impact
- Houses affected: [estimated number]
- Evacuation needed: [yes/no, estimated population]
- Safe zones identified: [locations]

### Economic Impact
- [High-level estimate of economic damage]

## 4. Recommended Actions

### Immediate (0-24 hours)
1. [Priority action with responsible entity]
2. [Evacuation routes if needed]
3. [Emergency resource deployment]

### Short-term (24-72 hours)
1. [Damage assessment teams]
2. [Resource allocation]
3. [Temporary infrastructure]

### Medium-term (3-14 days)
1. [Recovery priorities]
2. [Infrastructure repair sequence]
3. [Community support]

## 5. Resource Allocation
- Emergency services needed: [types and quantities]
- Equipment required: [list]
- Personnel estimates: [numbers by category]

## 6. Risk Assessment
- Secondary hazards: [what else might happen]
- Ongoing threats: [continued risks]
- Safety warnings: [for responders and residents]

Analysis Guidelines

1. Leverage area data: Use the known infrastructure layout to make specific, location-aware recommendations
2. Be comprehensive but concise: High-level overview, not building-by-building detail
3. Prioritize human safety: Evacuation and rescue always come first
4. Consider cascading effects: Power outages affect hospitals, road closures affect emergency response
5. Reference real-world precedents: Draw from similar Polish or European disasters when relevant
6. Be specific to Poland: Use Polish emergency service names (Straż Pożarna, Pogotowie, etc.)

Output Format

• Structured markdown with clear headings
• Tables for infrastructure status
• Bullet points for recommendations
• Actionable, prioritized content