weather

Fetches current weather and forecasts via wttr.in and Open-Meteo APIs.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/qiushido/picoclaw-lite --skill weather-qiushido
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weather
Source: https://github.com/qiushido/picoclaw-lite/tree/main/workspace/skills/weather
Command: npx skills add https://github.com/qiushido/picoclaw-lite --skill weather-qiushido

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Getting accurate weather for a city is harder than it looks: geocoding services often return the wrong location for ambiguous or non-Latin city names, leading to wrong forecasts. This Skill provides verified location matching so the weather you report actually corresponds to the place the user asked about. ## Core Features & Use Cases - Verified Location Matching: Cross-checks geocoding results (country, admin region, population) before querying weather, avoiding homonym city errors. - Dual API Strategy: Uses wttr.in for direct city-name queries (including Chinese names like 成都) and Open-Meteo for structured current conditions and daily forecasts. - Use Case: A user asks "成都天气怎么样?" — the Skill queries wttr.in with the original Chinese name, restates the matched location and observation time, and returns current conditions without an API key. ## Quick Start Ask the assistant for the current weather and today's forecast in Chengdu, and it will verify the location before reporting conditions.

Frequently Asked Questions about weather

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get current weather for a city without an API key?

Use curl to query wttr.in with the city name, for example curl -s "https://wttr.in/London?format=%l:+%c+%t+%h+%w". Both wttr.in and Open-Meteo work without API keys for current conditions and forecasts.

How to get weather for Chinese city names like 成都?

Query wttr.in directly with the URL-encoded Chinese name, since it resolves native names reliably. Avoid sending Hanzi to Open-Meteo geocoding, which may return smaller homonym locations; geocode the pinyin name like Chengdu instead.

wttr.in vs Open-Meteo for weather queries?

wttr.in is best for direct city-name queries and quick formatted output, including non-Latin names. Open-Meteo is better for structured JSON current conditions and multi-day forecasts once you have verified coordinates.

Why does geocoding return the wrong city for my weather query?

Geocoding APIs rank results by population and may return homonym locations in other countries. Always check the country, admin1, admin2, and population fields, and fall back to wttr.in with the original name if results look suspicious.

Does the weather skill require any API keys or dependencies?

No API keys are required for either wttr.in or Open-Meteo. The only dependency is the curl binary, which is used to make HTTP requests to both services.