OpenWeather#

Operate OpenWeather through your OOMOL-connected account. This skill calls the openweather_api connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action#

Assume the user has already installed the oo CLI, signed in, and connected OpenWeather. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

bash

oo connector schema "openweather_api" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

bash

oo connector run "openweather_api" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions#

• add_weather_station — Create one OpenWeather weather station under the current account. [write]
• delete_weather_station — Delete one OpenWeather weather station by identifier. [destructive]
• get_5_day_forecast — Retrieve the OpenWeather 5-day forecast in 3-hour steps for exactly one location selector.
• get_air_pollution_current — Retrieve the current air-pollution snapshot for one latitude and longitude.
• get_air_pollution_forecast — Retrieve the air-pollution forecast for one latitude and longitude.
• get_air_pollution_history — Retrieve historical air-pollution data for one latitude and longitude over a time range.
• get_circle_city_weather — Retrieve current weather for nearby cities around one latitude and longitude by using OpenWeather's compatibility city-search endpoint.
• get_current_weather — Retrieve the current weather for exactly one OpenWeather location selector.
• get_geocoding_by_zip — Resolve one ZIP or postal code into a named OpenWeather location.
• get_geocoding_direct — Resolve one place name into one or more OpenWeather geocoding matches.
• get_geocoding_reverse — Resolve one latitude and longitude pair into one or more named places.
• get_station_measurements — List aggregated historical measurements for one OpenWeather weather station.
• get_uv_index — Return the current UV index by sampling OpenWeather One Call 3.0, because the legacy UV Index API is retired.
• get_uv_index_forecast — Return daily UV forecast points by sampling OpenWeather One Call 3.0, because the legacy UV Index API is retired.
• get_uv_index_history — Return sampled historical UV index points by querying OpenWeather One Call 3.0 timemachine once per day in the requested range, because the legacy UV Index API is retired.
• get_weather_map_tile — Fetch one OpenWeather weather-map tile and return it as Base64 PNG bytes.
• get_weather_station — Retrieve one OpenWeather weather station by identifier.
• get_weather_triggers — Compatibility action for the retired OpenWeather Weather Triggers API. Execution always returns a deprecation error.
• list_weather_stations — List all OpenWeather weather stations available to the current account.
• submit_station_measurements — Submit one or more measurements for existing OpenWeather weather stations. [write]
• update_weather_station — Update one existing OpenWeather weather station. [write]

Safety#

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change OpenWeather state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup#

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md): bash

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  
  

  powershell

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  
  

• Not signed in / authentication error — sign in to your OOMOL account once: bash

  oo auth login
  
  

• scope_missing / credential_expired / app_not_ready / app_not_found — OpenWeather is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at: text

  https://console.oomol.com/app-connections?provider=openweather_api
  
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources#

• OpenWeather homepage: https://openweathermap.org