Weather 2.0

v1.0.1

Weather and forecasts (no API key). One wttr.in fetch by default; Open-Meteo if that fails. Chat-style answers — see “How to answer”.

0· 105·0 current·0 all-time
byMaxim Edogawa@maximedogawa

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for maximedogawa/weather-2-0.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Weather 2.0" (maximedogawa/weather-2-0) from ClawHub.
Skill page: https://clawhub.ai/maximedogawa/weather-2-0
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: curl
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install weather-2-0

ClawHub CLI

Package manager switcher

npx clawhub@latest install weather-2-0
Security Scan
Capability signals
Requires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (weather forecasts via wttr.in/Open‑Meteo) match the declared needs: only 'curl' is required and no credentials or installs are requested.
Instruction Scope
SKILL.md limits behavior to making wttr.in requests and, only on failure/need, up to two geocoding calls plus one Open‑Meteo forecast call. It does not instruct the agent to read local files, secrets, or unrelated system data.
Install Mechanism
No install spec or code files are present (instruction-only). Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill requests no environment variables or credentials; external network requests to public weather APIs are appropriate for its stated function.
Persistence & Privilege
The skill is not always-enabled and does not request elevated or persistent privileges; autonomous invocation is allowed by default on the platform but is not excessive here.
Assessment
This skill is coherent and only performs network requests to public weather services (wttr.in and Open‑Meteo). Before installing, consider that any location queries you ask the skill to fetch will be sent to those external services (they may log requests). There are no secrets requested and no local file access, so the main privacy consideration is the external exposure of user-provided place names. If that is acceptable, the skill is reasonable to use.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🌤️ Clawdis
Binscurl
latestvk97bz2sqpq17renvvm5hkps6fh852w4w
105downloads
0stars
2versions
Updated 1w ago
v1.0.1
MIT-0

Weather

Free: wttr.in (text) and Open-Meteo (JSON). No keys.

Default: one small request

Prefer a short forecast to save tokens and latency:

  • 1–2 days (typical “today / tomorrow / morgen”): https://wttr.in/PLACE?2&m — spaces → +. 2 = two-day forecast, m = metric.
  • Full multi-day table only if the user asks for the week, several days, or ?2 is not enough: https://wttr.in/PLACE?T&m (T = full terminal layout).

If the body looks like a real forecast → summarize and stop. No Open-Meteo unless wttr failed, error page, or you need JSON.

How to answer

Chat, not a datasheet: short intro on how it feels, then compact day lines (date, °C, rain when it matters). No lat/long, WMO codes, or bold datasheet headings unless the user asked for technical detail.

wttr.in (curl / fetch)

GoalExample
Short (default), 1–2 dayscurl -s "wttr.in/London?2&m"
Full week-style tablecurl -s "wttr.in/London?T&m"
One line nowcurl -s "wttr.in/London?format=3"
Custom one-linercurl -s "wttr.in/London?format=%l:+%c+%t+%h+%w"

Tips: + for spaces; ?m / ?u units; ?1 today only; ?0 now only; airports wttr.in/JFK; PNG wttr.in/Berlin.png.

Open-Meteo (fallback)

Hosts: geocoding-api.open-meteo.com, api.open-meteo.com only — not open-meteo.com HTML.

Flow (max 2 geocode + 1 forecast):

  1. https://geocoding-api.open-meteo.com/v1/search?name=PLACE&count=10 (spaces as +)
  2. If results missing/empty: one retry — shorter name + countryCode Pick the row whose admin3/admin2/admin1 matches the user phrase.
  3. https://api.open-meteo.com/v1/forecast?latitude=LAT&longitude=LON&daily=temperature_2m_max,temperature_2m_min,precipitation_probability_max,weathercode&forecast_days=7&timezone=auto — extend forecast_days to 7–16 if they asked for more days.

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

JSON: daily.time, temperature_2m_max / _min, precipitation_probability_max, weathercode — translate codes to plain words (see weather codes); never paste codes to the user unless asked.

When to use

Named place — current weather or forecast.

Comments

Loading comments...