Real-Time Weather Lookup

Problem

When a script or automation task needs current weather for a city or airport, an API Key and vendor quota can be unnecessary friction. weather-shenzhen targets this use case by using two free data sources: wttr.in for human-readable compact output, and Open-Meteo for structured JSON fallback.

How It Works and Limits

By default, the skill queries wttr.in first, returning current conditions, a short forecast, or a full forecast. Useful format tokens include %c condition, %t temperature, %h humidity, %w wind, %l location, and %m moon. Spaces in city names should be URL-encoded, such as New+York; airport codes like JFK also work. ?m selects metric units, ?u selects USCS units, ?1 limits output to today, and ?0 limits it to current conditions. PNG output can be saved locally.

For programmatic parsing, the skill can switch to Open-Meteo. Resolve the city coordinates first, then query JSON containing fields such as temp, windspeed, and weathercode, which are easier to inspect or log. The boundary is clear: it mainly solves free, keyless, immediate weather lookup. If city-name resolution is unstable, prefer airport codes or coordinates.