No API Key Weather Lookup

Problem Being Solved

Many weather scripts are blocked by API keys, quotas, or auth setup. weather-plus-plus targets a simpler need: fetching current conditions and short forecasts without third-party keys, with outputs that can be parsed by scripts. It is more direct for temporary lookups or adding a weather field to a script when key configuration feels unnecessary.

How It Works

The skill uses two free services: wttr.in as the primary source and Open-Meteo as the structured fallback.

• Quick weather: use curl to request wttr.in for one-line or full forecasts.
• Format controls: ?0 for current only, ?1 for today only, ?m metric, ?u USCS units.
• Location formats: city names, URL-encoded multi-word locations such as New+York, and airport codes such as JFK.
• Output shapes: text responses for humans or terminals, and image output such as wttr.in/Berlin.png.
• JSON fallback: resolve city coordinates first, then query Open-Meteo for fields like temp, windspeed, and weathercode.

Boundaries and Notes

It is not aimed at high-throughput production SLAs or complex meteorological datasets; the focus is keyless, lightweight weather lookup. wttr.in is better for human-readable terminal output, while Open-Meteo is better for programmatic parsing. Watch unit parameters, location encoding, airport-code coverage, and the usual variability of free public endpoints. More complex weather fields or historical data would need separate extension.