Get current weather and forecasts via wttr.in or Open-Meteo. Use when: user asks about weather, temperature, or forecasts for any location. NOT for: historical weather data, severe weather alerts, or detailed meteorological analysis. No API key needed.
97
Does it follow best practices?
Validation for skill structure
Quick weather response formats
Uses curl
100%
100%
Uses wttr.in
100%
100%
City in URL
100%
100%
Current weather format
0%
100%
Current weather location code
0%
100%
Rain format uses %p
100%
100%
Rain format uses %c
100%
100%
Weekend uses format=v2
100%
100%
Three commands documented
100%
100%
No API key
100%
100%
Without context: $0.1167 · 29s · 8 turns · 13 in / 1,402 out tokens
With context: $0.2983 · 53s · 19 turns · 24 in / 2,926 out tokens
Custom format codes and JSON output
Uses curl
100%
100%
Uses wttr.in
100%
100%
City name in URL
100%
100%
Temperature code used
0%
100%
Feels-like code used
0%
100%
Wind code used
0%
100%
Humidity code used
0%
100%
Condition code used
0%
100%
JSON fetch uses format=j1
100%
100%
JSON fetched once only
0%
100%
No API key
100%
100%
Without context: $0.3109 · 1m 15s · 21 turns · 26 in / 3,757 out tokens
With context: $0.2249 · 54s · 16 turns · 20 in / 2,503 out tokens
Specific day forecast and airport codes
Uses curl
100%
100%
Uses wttr.in
100%
100%
Airport code in URL path
100%
100%
Day offset as URL param
0%
0%
Offset 1 fetches tomorrow
0%
0%
No API key
100%
100%
No external packages
75%
100%
Output written to file
100%
100%
Example output produced
100%
100%
Without context: $0.2798 · 1m 20s · 16 turns · 23 in / 4,252 out tokens
With context: $0.2961 · 1m 17s · 15 turns · 21 in / 4,434 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.