War Intelligence Monitor

Real-time war intelligence monitoring and emergency alert system for conflict zones. Use when user needs to track military conflicts, receive emergency alert...

Security Scan

The skill's high-level purpose (real-time conflict monitoring) matches its instructions, but the runtime guidance is vague about external endpoints, persistent cron installation, and required credentials — creating risk of unintentionally transmitting sensitive location/contact data or installing persistent jobs without clear safeguards.

Purpose & Capability

Name/description align with the instructions: it legitimately needs a user location, known targets, and periodic monitoring. However, the skill also instructs sending alerts to third-party channels (Discord/Telegram/etc.) and querying services (FlightRadar24, flight prices) without declaring the credentials or APIs required — a mismatch between claimed needs and declared requirements.

Instruction Scope

SKILL.md tells the agent to read a local config with precise user coordinates and emergency contacts, create system cron jobs, search news and external services, and 'send alerts to [Discord/Telegram/etc.]'. These instructions are broad and underspecified: they permit network requests to arbitrary endpoints and transmission of sensitive personal data, and they instruct persistent system changes (cron) without constraints or explicit user-approval steps.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest install risk. Nothing will be written to disk by an install process. The remaining risk comes from the runtime instructions (creating cron jobs and contacting external services), not from installation.

Credentials

No environment variables, credentials, or API keys are declared, yet the instructions expect posting alerts to external platforms and querying commercial services. That mismatch is problematic: posting to Discord/Telegram or FlightRadar24 typically requires webhooks or API keys. The skill also asks for exact user coordinates and emergency contacts (sensitive data) with no explanation of how they are protected or where alerts are sent.

Persistence & Privilege

The skill tells the agent to create cron jobs (urgent monitoring every 30 min and repeated daily briefings). Creating scheduled jobs is a persistent system change that can run autonomously and transmit data periodically; this capability is not reflected in metadata and should be explicitly authorized by the user and constrained to safe endpoints.

What to consider before installing

This skill can collect and repeatedly transmit sensitive data (exact location, emergency contacts) and instructs the agent to create cron jobs that run autonomously and may post to external channels. Before installing or running: (1) Confirm exactly which endpoints the agent will use to send alerts; prefer single-purpose inbound webhooks or channels you control and require tokens. (2) Do not provide precise home coordinates or unneeded personal phone numbers until you trust the destination. (3) Require explicit, interactive confirmation before creating any cron jobs; review the actual crontab entries the agent will add. (4) If posting to Discord/Telegram, create minimal-scope webhooks/bots and rotate tokens after testing. (5) Consider running the skill in a sandboxed environment or on a disposable account until you confirm its behavior. If the publisher can provide a concrete list of APIs/endpoints and an explicit auth model (what keys/hooks are needed and where data will be sent), reassess — that information would raise confidence toward benign.

Real-time conflict monitoring system with location-based threat assessment.

Setup

Before using, configure user profile in config.json:

{
  "user_location": {
    "name": "Your Location Name",
    "coordinates": [latitude, longitude],
    "shelter_primary": "Nearest shelter location",
    "shelter_secondary": "Backup shelter location"
  },
  "evacuation_target": "Target city/country",
  "known_targets": [
    {"name": "Military Base A", "distance_km": 20, "type": "military"},
    {"name": "Airport", "distance_km": 15, "type": "infrastructure"},
    {"name": "Port", "distance_km": 25, "type": "infrastructure"}
  ],
  "emergency_contacts": {
    "police": "emergency number",
    "ambulance": "emergency number",
    "embassy": "embassy number"
  }
}

Monitoring Workflow

1. Set Up Cron Jobs

Create two monitoring jobs:

Urgent Monitoring (every 30 min)

Execute war intel monitoring:
1. Search latest news: [conflict keywords]
2. Check for red alert keywords (airspace closed, missile launch, air raid, explosion)
3. If emergency detected, send alert immediately
4. Include distance from user location for each target mentioned

Alert format:
🚨 [RED ALERT] {event}
📍 Distance from you: ~{X}km
⚡ Immediate actions: {actions}
📊 Next 24-72h forecast: {prediction}

Daily Briefing (3x daily)

Generate daily briefing:
1. Search past 6 hours news
2. Check airspace status
3. Query flight prices and availability to evacuation target
4. Provide risk assessment and recommendations

2. Alert Levels

Level	Trigger	Response
🔴 Red	Airspace closed, missile launch, direct attack	Immediate shelter, action instructions
🟡 Yellow	Military buildup, diplomatic breakdown, oil spike >10%	Prepare, monitor signals
🟢 Green	Routine monitoring	Daily briefing

3. Alert Template

🚨 [ALERT LEVEL] {Event Type}

📍 Location: {target_name}
📏 Distance from you: ~{distance}km

⚡ Immediate Actions:
1. {action_1}
2. {action_2}
3. {action_3}

📊 Situation Assessment:
{brief_analysis}

🔗 Source: {source}

4. Briefing Template

📋 Daily Briefing - {date}

🎯 Situation Summary:
{overview}

📍 Recent Incidents (with distances):
| Target | Distance | Status |
|--------|----------|--------|
| {name} | {km}km | {status} |

✈️ Evacuation Options:
- Flight availability: {status}
- Prices: {price_range}
- Recommendation: {recommendation}

🛡️ Risk Assessment: {level}
{reasoning}

Safety Guidelines

Shelter Priorities

1. Underground parking / basement
2. Bathroom (no windows, reinforced walls)
3. Interior corridor (away from exterior walls)
4. Lowest floor, interior room

Go Bag Checklist

• Passport + copies
• Cash (local + USD)
• Phone + charger + power bank
• Water bottles
• High-calorie snacks
• Work gloves (for debris)
• Flashlight
• First aid basics
• Important documents

During Attack

1. Move away from windows immediately
2. Drop to floor if explosion heard
3. Cover head and neck
4. Wait 10-15 seconds before moving
5. Check for injuries, then assess surroundings

Information Sources

Official Sources (Priority)

• National emergency management agency
• Ministry of Defense statements
• Embassy alerts
• Civil aviation authority

OSINT Sources

• FlightRadar24 (airspace status)
• MarineTraffic (shipping lanes)
• Verified news agencies
• Official government social media

Financial Indicators

• Oil prices (Brent/WTI)
• Currency fluctuations
• Prediction markets (Polymarket)
• Flight price trends

Customization

Edit config.json to customize:

• Your location and coordinates
• Known military/infrastructure targets with distances
• Evacuation destination
• Emergency contacts
• Alert keywords in local language