playbooks

home / skills / openclaw / skills / virus-monitor

virus-monitor skill

/skills/pasogott/virus-monitor

This skill aggregates Vienna virus monitoring data from wastewater, sentinel, and AGES sources, providing a unified JSON summary.

npx playbooks add skill openclaw/skills --skill virus-monitor

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
1.6 KB
---
name: virus-monitor
version: 0.1.0
description: Virus-Monitoring für Wien (Abwasser + Sentinel)
author: ClaudeBot
tags: [health, vienna, monitoring, covid, influenza, rsv]
---

# virus-monitor

Kombiniert mehrere österreichische Datenquellen für Virus-Monitoring:

## Datenquellen

1. **Nationales Abwassermonitoring** (abwassermonitoring.at)
   - SARS-CoV-2 Genkopien pro Einwohner/Tag
   - Bundesländer-Daten inkl. Wien
   
2. **MedUni Wien Sentinel System** (viro.meduniwien.ac.at)
   - Positivitätsraten für respiratorische Viren
   - DINÖ (Diagnostisches Influenza Netzwerk Österreich)
   - Wöchentliche Berichte

3. **AGES Abwasser Dashboard** (abwasser.ages.at)
   - SARS-CoV-2, Influenza, RSV
   - Österreichweit

## Usage

```bash
# Alle Daten als JSON
virus-monitor

# Nur bestimmte Quelle
virus-monitor --source abwasser
virus-monitor --source sentinel
virus-monitor --source ages
```

## Output

```json
{
  "timestamp": "2026-01-09T00:37:00Z",
  "status": "erhöht",
  "sources": {
    "abwasser": { ... },
    "sentinel": { ... },
    "ages": { ... }
  },
  "summary": {
    "wien": {
      "sars_cov_2": "...",
      "influenza": "...",
      "rsv": "..."
    }
  }
}
```

## Status-Levels

- `niedrig` - Normale saisonale Aktivität
- `moderat` - Erhöhte Aktivität, Aufmerksamkeit empfohlen  
- `erhöht` - Deutlich erhöhte Aktivität
- `hoch` - Starke Virus-Zirkulation

## Dependencies

- `curl` - HTTP requests
- `jq` - JSON processing
- Standard Unix tools (awk, grep, sed)

## Notes

- Abwasserdaten haben ~1-2 Wochen Verzögerung
- Sentinel-Daten werden wöchentlich aktualisiert (Freitags)
- AGES Dashboard ist eine Shiny-App (dynamisch)

Overview

This skill aggregates multiple Austrian virus-monitoring sources to provide a unified JSON snapshot focused on Vienna. It combines wastewater monitoring, the MedUni Vienna sentinel reports, and the AGES wastewater dashboard to produce a concise status and per-source payload. The output includes a timestamp, a unified status level, and Vienna-specific summaries for SARS-CoV-2, influenza, and RSV.

How this skill works

The skill fetches data from three sources: national wastewater monitoring, the MedUni Wien sentinel system (weekly reports), and the AGES wastewater dashboard. It normalizes metrics (e.g., genome copies per capita, positivity rates) and merges them into a single JSON payload with a derived status level. The tool depends on curl and jq and uses simple Unix text tools to parse dynamic or delayed sources.

When to use it

  • Routine public-health monitoring for Vienna and Austria-wide trends
  • Integrating local wastewater and sentinel indicators into dashboards
  • Automated alerts or scripts that require a single status payload
  • Research or retrospective analysis where combined indicators are useful
  • Quick checks before public messaging or operational decisions

Best practices

  • Run the skill regularly but account for data lags (wastewater ~1–2 weeks, sentinel weekly)
  • Use the --source flag to pull individual sources when troubleshooting
  • Validate derived status levels against raw source values before high-consequence decisions
  • Cache results and track timestamps to avoid repeated scraping of dynamic dashboards
  • Combine outputs with local clinical or hospital data for context

Example use cases

  • Daily cron job that writes the combined JSON to a monitoring S3 bucket
  • Dashboard widget showing current Vienna status and recent trends
  • Automated email or Slack alert when status changes to 'erhöht' or 'hoch'
  • Research pipeline that correlates wastewater genome copies with sentinel positivity rates
  • Local health office pulling the Vienna summary for situational reports

FAQ

Why do wastewater numbers lag behind sentinel reports?

Wastewater sampling and lab processing typically introduce a 1–2 week delay, while sentinel reporting is updated weekly.

Can I request only one data source?

Yes. Use the --source option with values 'abwasser', 'sentinel', or 'ages' to fetch a single source as JSON.