Weather Query

What problem it solves

When a user asks about the current weather or asks whether a location will get colder in the coming days, the answer should not rely on stale model memory. Weather Query turns this common life-service question into a concrete workflow: identify the location, run the bundled script to fetch live data, and summarize the result in the user's language.

How the skill works

The skill is built around Open-Meteo geocoding and forecast APIs and does not require an API key:
- Location resolution: extract the city, region, or coordinates from the message; if no location is provided, ask for one first.
- Script lookup: run the bundled script to resolve the place and retrieve weather data, with optional forecast days when requested.
- Result summary: return the resolved location, current temperature, apparent temperature, weather condition, humidity, and wind speed, plus a short forecast if asked.

Boundaries and notes

• If geocoding returns multiple matches, the script uses the first result and prints the resolved location, so ambiguous place names need attention.
• Weather changes quickly, so this is best used for live lookups rather than treating old answers as durable facts.
• The skill targets single-location weather questions and does not cover radar maps, historical climate, severe-weather alerts, or advanced meteorological analysis.