weather

What This Skill Does

The Weather skill for OpenClaw provides a versatile interface for retrieving real-time meteorological data and forecasts without the need for personal API keys. It acts as a wrapper for two high-quality, free-to-use services: wttr.in for human-readable, quick-glance reporting, and Open-Meteo for robust, JSON-formatted data suitable for programmatic analysis. Whether you need a simple temperature check for a morning commute or structured data for automated reports, this skill serves as a reliable information source for any location worldwide.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/99percentgod/weather-1-0-0 Ensure that your OpenClaw instance is updated to the latest version to maintain compatibility with the skill's request handling.

Use Cases

• Personal Planning: Quickly check current temperatures and conditions before leaving the office.
• Travel Logistics: Get location-specific forecasts using city names or airport IATA codes (e.g., JFK, LHR).
• Automated Dashboarding: Integrate the skill into scripts to pull JSON weather data from Open-Meteo for custom monitoring.
• Visual Reporting: Generate weather images for document integration using the PNG export feature of wttr.in.

Example Prompts

• "OpenClaw, what is the current weather in Tokyo? Give me the full forecast for today."
• "Check the wind conditions and humidity for New York city using the compact format."
• "What is the current temperature in Berlin? Please provide the answer in metric units."

Tips & Limitations

• URL Encoding: When searching for cities with multiple words, ensure you replace spaces with plus signs (e.g., San+Francisco).
• Units: By default, the skill often leans toward metric, but you can append ?u to force USCS units if necessary.
• Limitations: While highly reliable, these services are community-supported. Extremely high-frequency polling might result in temporary rate limiting. If you require critical production-grade reliability with guaranteed uptime, consider caching the output locally rather than querying the services for every interaction.