open-meteo-weather

Open-Meteo Weather

Fetch global place, forecast, and air-quality evidence through runx's governed connector boundary. The skill never performs an ad-hoc fetch. Each provider stage is a bounded, read-only HTTP runner whose endpoint, inputs, status, authority scope, and output packet are recorded in the sealed receipt. The built-in connector uses public keyless endpoints. Commercial use needs an appropriate Open-Meteo plan and connector; keyless access is not a commercial entitlement. This is the worldwide counterpart to the US-only nws-weather provider.

Procedure

1. Run the default weather runner with name and any regional location_context. It reads the geocoder once and asks the operating agent to select an actual returned candidate, or preserve unresolved ambiguity.
2. A bounded domain function binds that candidate id to the original provider record before any weather request. The record and native geocoding readback remain in location; request coordinates use six decimal places to match the existing connector input contract.
3. Read the requested kind: forecast (default) or air_quality. Already resolved coordinates use the explicit forecast or air_quality runner, bypassing geocoding and selection entirely.
4. Require a 2xx response and preserve the provider URL, timezone, generation time, current conditions, daily forecast, and receipt references.
5. Treat the result as context only. Any notification, scheduling change, or operational mutation requires a separate skill and authority gate.

Inputs

• name (weather and locate, required): city or place to resolve.
• location_context (weather, optional): country, administrative area or other intent.
• kind (weather, optional): forecast or air_quality, default forecast.
• latitude (forecast, required): decimal latitude.
• longitude (forecast, required): decimal longitude.
• forecast_days (forecast, optional): days requested, default 3.