pilot-service-agents-weather

# pilot-service-agents-weather Weather forecasts and historical climate — Open-Meteo (forecast, archive, air quality, marine, flood), Seven Timer astronomy. All agents in this category follow the standard contract described in `pilot-service-agents`. Send `/help` to any agent to read its exact filter schema — the table below is a snapshot; the catalogue grows, so always verify with a fresh `list-agents` query. ## Agents in this category (snapshot) | Hostname | Description | |---|---| | `open-meteo-air-quality` | Global air quality forecast (PM, ozone, NO2) | | `open-meteo-archive` | Historical weather data globally since 1940 | | `open-meteo-flood` | Global river flood forecast | | `open-meteo-forecast` | Global weather forecast (hourly, daily) | | `open-meteo-marine` | Marine forecast (waves, swell, sea temp) | | `seven-timer-astro` | Astronomical weather forecast (seeing, cloud) | | `sunrise-sunset` | Sunrise, sunset, twilight by coordinates | ## What you can expect - Unauthenticated Open-Meteo access to forecast, archive, marine, flood, AQ - Latitude/longitude-keyed queries with hourly/daily granularity ## What NOT to expect - Radar imagery — JSON only - Hyper-local (<1 km) models — upstream resolution varies ## Commands (same pattern for every agent in the category) ```bash # Read an agent's filter contract pilotctl --json send-message <hostname> --data "/help" --wait # Fetch structured data pilotctl --json send-message <hostname> --data '/data {json filters}' --wait # Natural-language summary (Gemini) pilotctl --json send-message <hostname> --data '/summary {json filters}' --wait ``` ## Response shape With `--wait`, `send-message` blocks until the agent replies (up to 30 s by default) and prints one JSON document: the ACK fields (`{"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}`) plus `reply`, the agent's message. The agent's normalised envelope is the JSON string in `data.reply.data` (pilotctl v1.12.2 and older print two JSON documents instead: the send result, then the reply, whose `data.data` is the envelope). A non-zero exit means no reply arrived (the error JSON on stderr has a `code` such as `timeout`) — treat that as *no data*, never as a cue to read older messages from the inbox. A reply that lands after the wait can still be picked up by sender and time: `pilotctl --json inbox --from <hostname> --since 5m --latest`. The envelope: ```json { "source": "<hostname>", "items": [...], "count": <int>, "total": <int|null>, "page": <int|null>, "next": <cursor|null>, "truncated": <bool>, "upstream_url": "<resolved upstream URL>" } ``` `/help` returns plain text. `/summary` returns a Gemini-generated prose string. Free-text queries also return Gemini prose. ## Workflow Example ```bash # 1. Fresh discovery — the catalogue grows, never hard-code pilotctl --json send-message list-agents --data '/data {"category":"weather","limit":20}' --wait # 2. Read the contract of a specific agent pilotctl --json send-message open-meteo-forecast --data '/help' --wait # 3. Query it pilotctl --json send-message open-meteo-forecast --data '/data {"latitude":40.71,"longitude":-74.00,"hourly":"temperature_2m","forecast_days":2}' --wait ``` ## Dependencies Requires the `pilot-protocol` core skill, the `pilot-service-agents` skill (for the general discovery flow), `pilotctl` on PATH, and a running daemon registered with the backbone (Network 0 — joined automatically at registration).