event-day-lightning-watch — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited event-day-lightning-watch (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Goal: keep people safe at a fixed outdoor venue by polling lightning proximity and issuing clear continue / suspend / shelter / resume calls using standard lightning-safety thresholds.
Reminder: this supports an on-site safety officer; it does not replace one. The venue's emergency plan and official warnings take precedence.
lat, lon (CONUS).get_threat_brief(lat, lon)threat_level, the attention_window, and anylightning_summary. If the brief is already elevated+ for storms/lightning, brief the safety officer before doors open.
get_lightning(lat, lon, radius_km=16, minutes=15)
data.flash_count, data.flashes_per_min, anddata.nearest_strike.distance_km / time_utc.
get_threat_brief(lat, lon) to see whether severe weather (not just lightning) is developing — hail/wind/tornado may warrant evacuation beyond a lightning hold.
get_lightning shows no strikes within 16 km for a continuous30 minutes, clear the suspension.
[<time_utc>] Lightning watch — <venue>
Nearest strike: <dist> km <dir> at <time_utc> (flashes <n>, <rate>/min within 16 km)
CALL: <CONTINUE | HEIGHTENED WATCH | SUSPEND | SHELTER NOW | CLEARED>
Resume eligible at: <last-strike-time + 30 min, or "n/a">
Notes: <e.g. "rate increasing, cell approaching from SW">~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.