Weather Pollen

**Quick judgment:** Solid, focused skill for getting combined weather and pollen data for a configured location, with minimal setup and a single tool. Most appropriate for assistants or workflows that repeatedly query the same geographic area. **Key behaviors & limitations:** - Uses Open-Meteo for weather and Pollen.com for pollen; both are free and require no API keys. - Location is effectively fixed by environment variables (lat/lon); the `location` argument is primarily a display name, not true per-call geocoding. This means it’s best for a “home base” location rather than arbitrary, per-query locations. - Returns current conditions and forecast plus pollen data when `includePollen` is true. **Risks & caveats:** - **Data reliability:** Depends entirely on third-party, free APIs with no uptime guarantees; service changes, outages, or rate limiting can break or degrade the skill. - **Pollen data fragility:** Pollen.com has historically changed formats; if the skill relies on scraping or unofficial endpoints, pollen results may silently fail or become inaccurate. - **Location semantics:** Because the actual coordinates are configured via environment variables, a calling agent might assume that passing a new `location` string changes the actual geographic target when it may not. This can lead to misleading answers if not documented and enforced at the system level. - **Regional differences:** Weather and pollen forecasts may differ from local national services; should not be used where regulatory-grade or mission-critical meteorological data is required. **Recommended scenarios:** - Chat or voice assistants that need quick, non-critical weather + pollen updates for a fixed primary location (e.g., user’s home city). - Allergy or health-focused experiences where approximate pollen and forecast information is sufficient for guidance and awareness. - Lightweight automations and notifications ("send me a message if pollen is high tomorrow") rather than safety-critical decision systems. - Prototyping or low-volume applications where dependence on free, no-key APIs is acceptable and easier than managing paid weather APIs.