open-meteo-weather
Skill5 starsChanged 9 months agoMITView on GitHub
Get current weather using the Open-Meteo API. Use for requests like “current weather in Boston,” “get weather for Medford, MA,” or any task that needs a quick current_weather lookup via Open-Meteo (by location name or lat/lon). Use when the user wants a direct API call or a tiny CLI flow to fetch current conditions.
In this repository13 other files it gives its agents.
- apple-music-playerSkill
- apple-notesSkill
- applescript-open-appSkill
- confettiSkill
- ffmpeg-video-editor-h265Skill
- githubSkill
- git-searchSkill
- launchd-non-apple-jobsSkill
- mailapp-send-emailSkill
- opml-readerSkill
- playwright-cliSkill
- saySkill
- screen-recorderSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use the script for location names:
- Distinctive: line 18
Use the script for explicit coordinates:
- Distinctive: line 32
If location name is provided, geocode first (use the Open-Meteo geocoding API).
- Very specific: line 33
Call the forecast endpoint with current_weather=true and timezone=auto.
- Very specific: line 36
Use keys: windspeed_kmh, winddirection_deg, weathercode, is_day, time, interval.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Open-Meteo Weather
Overview
Fetch current weather from Open-Meteo with a tiny, deterministic flow. Prefer the script for repeatable calls; fall back to raw URL construction when asked for a direct API call.
Quick Start
- Use the script for location names:
/Users/ivancampos/.codex/skills/open-meteo-weather/scripts/open_meteo_current.py --location "Boston, MA"- Use the script for explicit coordinates:
/Users/ivancampos/.codex/skills/open-meteo-weather/scripts/open_meteo_current.py --lat 42.3601 --lon -71.0589- Provide a direct API call when the user requests a raw URL:
https://api.open-meteo.com/v1/forecast?latitude=42.3601&longitude=-71.0589¤t_weather=true&timezone=autoWorkflow
- Determine input type: location name or lat/lon.
- If location name is provided, geocode first (use the Open-Meteo geocoding API).
- Call the forecast endpoint with
current_weather=trueandtimezone=auto. - Return JSON with
locationand a normalizedcurrent_weatherobject.- Include both
temperature_candtemperature_f. - Use keys:
windspeed_kmh,winddirection_deg,weathercode,is_day,time,interval.
- Include both
Examples
- “Get current weather in Boston” → geocode, then call forecast.
- “Use this URL for Medford, MA” → provide direct forecast URL with given lat/lon.
Resources
scripts/
open_meteo_current.py: CLI for location or lat/lon; prints JSON withlocationandcurrent_weather.
references/
open_meteo.md: endpoint and parameter quick reference.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

