IvanCampos/agents / skills/open-meteo-weather
open-meteo-weather
VerifiedGet 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.
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=auto
Workflow
- 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |