home / skills / openclaw / skills / weather-2

weather-2 skill

safe

This skill provides current weather and forecasts without keys, using wttr.in and Open-Meteo for quick, code-friendly weather insights.

npx playbooks add skill openclaw/skills --skill weather-2

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

1.2 KB

---
name: weather
description: Get current weather and forecasts (no API key required).
homepage: https://wttr.in/:help
metadata: { "openclaw": { "emoji": "🌤️", "requires": { "bins": ["curl"] } } }
---

# Weather

Two free services, no API keys needed.

## wttr.in (primary)

Quick one-liner:

```bash
curl -s "wttr.in/London?format=3"
# Output: London: ⛅️ +8°C
```

Compact format:

```bash
curl -s "wttr.in/London?format=%l:+%c+%t+%h+%w"
# Output: London: ⛅️ +8°C 71% ↙5km/h
```

Full forecast:

```bash
curl -s "wttr.in/London?T"
```

Format codes: `%c` condition · `%t` temp · `%h` humidity · `%w` wind · `%l` location · `%m` moon

Tips:

- URL-encode spaces: `wttr.in/New+York`
- Airport codes: `wttr.in/JFK`
- Units: `?m` (metric) `?u` (USCS)
- Today only: `?1` · Current only: `?0`
- PNG: `curl -s "wttr.in/Berlin.png" -o /tmp/weather.png`

## Open-Meteo (fallback, JSON)

Free, no key, good for programmatic use:

```bash
curl -s "https://api.open-meteo.com/v1/forecast?latitude=51.5&longitude=-0.12&current_weather=true"
```

Find coordinates for a city, then query. Returns JSON with temp, windspeed, weathercode.

Docs: https://open-meteo.com/en/docs

Overview

This skill fetches current weather and forecasts without requiring an API key. It uses wttr.in for human-friendly and image outputs and Open-Meteo for reliable JSON data for programmatic use. The skill is lightweight and designed for quick command-line or integration queries. It supports location names, airport codes, and coordinate-based requests.

How this skill works

For human-readable results the skill queries wttr.in endpoints, which return compact text lines, full forecasts, or PNG images. For machine-readable responses it falls back to Open-Meteo, which returns structured JSON including temperature, wind speed, and weather codes. The skill URL-encodes locations and supports units, current-only or daily views, and optional format strings for custom output.

When to use it

Quick terminal checks of current conditions or short forecasts.
Embedding a small weather image (PNG) for dashboards or messages.
Programmatic retrieval of structured weather data via JSON.
Simple scripts that must avoid API keys or rate-limited services.
Testing or archiving weather queries for different locations.

Best practices

Use wttr.in format codes to customize concise output (condition, temp, humidity, wind).
URL-encode spaces in locations (e.g., New+York) or use airport codes for precision.
Use Open-Meteo with latitude/longitude for consistent JSON responses in scripts.
Specify units explicitly (?m for metric, ?u for USCS) to avoid ambiguity.
Request ?0 for current-only or ?1 for today-only when you need minimal output.

Example use cases

One-liner terminal check: get a single-line summary for London using wttr.in format output.
Dashboard image: request wttr.in/City.png to embed a weather graphic into a status page.
Automation script: call Open-Meteo with coordinates and parse current_weather for alerts or logging.
Chatbot reply: generate a compact human-friendly summary with wttr.in format codes before sending to users.
Data collection: schedule Open-Meteo queries to build a lightweight local weather dataset without API keys.

FAQ

Do I need an API key?

No. Both wttr.in and Open-Meteo are free and do not require API keys.

How do I get machine-friendly output?

Use Open-Meteo with latitude and longitude; it returns JSON including current_weather fields like temperature and windspeed.

Can I get images or compact text?

Yes. wttr.in can return PNG images (City.png) or compact formatted text using format codes for condition, temp, humidity, wind.