Weather and Air Quality Lookup

Problem

A query like /weather Beijing seems simple, but returning only “clear, 25°C” is often not enough. Users may also need apparent temperature, wind speed and direction, UV index, air quality, and main pollutants. Manually stitching Open-Meteo calls, geocoding, WMO code interpretation, wind direction conversion, and AQI classification creates repeated boilerplate.

How It Works

The skill runs a fixed workflow:
- Location parsing: extract the city from input; if missing, use WebSearch or ask the user.
- Geocoding: call the Open-Meteo Geocoding API to obtain latitude, longitude, city, and country.
- Data retrieval: query free Open-Meteo endpoints for weather and wind, UV index, and air quality.
- Formatting: map WMO codes to readable conditions, convert wind angles to compass directions, and label UV and AQI levels with practical advice.
- Fallback handling: if an API fails, search for current weather and air quality; if geocoding misses, suggest an English name or broader location.

Boundaries

It is aimed at current-weather snapshots, not long-range forecasts, historical records, or minute-by-minute precipitation probabilities. Output depends on Open-Meteo data quality and location matching; missing fields are shown as unavailable when partial data succeeds.