Skip to main content
skill CX Codex

open-meteo — Claude Code skill: features and installation

This Claude Code skill builds requests for Open-Meteo weather, air-quality, and geocoding APIs. It activates when a task needs forecast data, pollution metrics, or coordinates for a place name.

MIT 100 installs ★ 23 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add itechmeat/llm-code --skill open-meteo -a claude-code
Open on GitHub

What open-meteo does

The skill helps shape requests to Open-Meteo’s forecast, air-quality, and geocoding APIs. It selects variables and units, sets the time range and timezone, and handles responses for multiple coordinate pairs. Place names can be resolved to coordinates before a data request.

Daily values require a timezone parameter. Timestamps returned as unixtime use GMT+0, so local dates need the utc_offset_seconds adjustment. HTTP failures and JSON responses marked error: true are handled separately. The skill includes API references, model notes, weather-code guidance, and request examples. Air-quality data requires CAMS attribution; geocoding requires GeoNames attribution.

What it helps with

  • resolve a place name to coordinates and a timezone
  • request hourly or daily forecast variables
  • fetch air-quality and AQI metrics
  • handle API errors and batched location responses

Example prompts for the agent

  • Get the weather forecast for Berlin for the next few days, with hourly temperature and daily values.
  • Find Tokyo’s coordinates and timezone, then fetch its current weather.
  • Request hourly pm10, pm2_5, and european_aqi values for the project coordinates.

How to install open-meteo

1Skills CLI (Vercel)

npx skills add itechmeat/llm-code --skill open-meteo -a claude-code

2Manually: put the files in place

~/.claude/skills/open-meteo/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/open-meteo/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about open-meteo

How do I install open-meteo in Claude Code?

Run npx skills add itechmeat/llm-code --skill open-meteo -a claude-code. The skill file is at ~/.claude/skills/open-meteo/SKILL.md.

What does open-meteo do?

It guides an agent in querying Open-Meteo for weather forecasts, air-quality readings, and coordinates from place names. It covers variable selection, time settings, units, and error handling.

How should open-meteo handle timestamps?

Set timezone when requesting daily values. unixtime timestamps use GMT+0 and need the utc_offset_seconds adjustment to determine local dates.

Source text

SKILL.md · MIT
---
name: open-meteo
description: "Integrate Open-Meteo Weather Forecast, Air Quality, and Geocoding APIs: query design, variable selection, timezone/timeformat/units, multi-location batching, and reliable error handling. Use when fetching weather forecasts, air quality/pollen data, or geocoding place names to coordinates via Open-Meteo. Keywords: Open-Meteo, /v1/forecast, /v1/air-quality, geocoding-api, hourly, daily, current, timezone=auto, timeformat=unixtime, models, WMO weather_code, CAMS, GeoNames, httpx, FastAPI, pytest."
metadata:
  version: "1.7.0"
  release_date: "2026-10-16"
---

# Open Meteo

## Goal

Provide a reliable, production-friendly way to call Open-Meteo APIs (Forecast, Air Quality, Geocoding), choose variables, control time/units/timezone, and parse responses consistently.

## Quick navigation

| Topic                              | Reference                                      |
| ---------------------------------- | ---------------------------------------------- |
| Weather Forecast API reference      | `references/forecast-api.md`                   |
| Air Quality API reference          | `references/air-quality-api.md`                |
| Geocoding API reference            | `references/geocoding-api.md`                  |
| Provider/model selection (`models=`) | `references/models.md`                        |
| WMO weather interpretation codes   | `references/weather-codes.md`                  |
| Worked examples (geocode → fetch)  | `references/examples.md`                       |

## Steps

1. Pick the correct API and base URL
   - Forecast: `https://api.open-meteo.com/v1/forecast`
   - Air Quality: `https://air-quality-api.open-meteo.com/v1/air-quality`
   - Geocoding: `https://geocoding-api.open-meteo.com/v1/search`

2. Resolve coordinates (if you only have a name)
   - Call Geocoding with `name` and optional `language`, `countryCode`, `count`.
   - Use the returned `latitude`, `longitude`, and `timezone` for subsequent calls.

3. Design your time axis (timezone, timeformat, and range)
   - Prefer `timezone=auto` when results must align to local midnight.
   - If you request `daily=...`, set `timezone` (docs: daily requires timezone).
   - Choose `timeformat=iso8601` for readability, or `timeformat=unixtime` for compactness.
     - If using `unixtime`, remember timestamps are GMT+0 and you must apply `utc_offset_seconds` for correct local dates.
   - Choose range controls:
     - `forecast_days` and optional `past_days`, or
     - explicit `start_date`/`end_date` (YYYY-MM-DD), and for sub-daily `start_hour`/`end_hour`.

4. Choose variables minimally (avoid "download everything")
   - Forecast: request only the variables you need via `hourly=...`, `daily=...`, `current=...`.
   - Air Quality: request only the variables you need via `hourly=...`, `current=...`.
   - Keep variable names exact; typos return a JSON error with `error: true`.

5. Choose units and model selection deliberately
   - Forecast units:
     - `temperature_unit` (`celsius` / `fahrenheit`)
     - `wind_speed_unit` (`kmh` / `ms` / `mph` / `kn`)
     - `precipitation_unit` (`mm` / `inch`)
   - Forecast model selection:
     - default `models=auto` / “Best match” combines the best models.
     - you can explicitly request models via `models=...`.
     - provider-specific forecast endpoints also exist (provider implied by path). See `references/models.md` (section "Endpoints vs `models=`") for examples and doc links.
     - for provider/model-specific selection tradeoffs, see `references/models.md`.
   - Air Quality domain selection:
     - `domains=auto` (default) or `cams_europe` / `cams_global`.

6. Implement robust request/response handling
   - Treat HTTP errors and JSON-level errors separately.
   - JSON error format is:
     - `{"error": true, "reason": "..."}`
   - When requesting multiple locations (comma-separated coordinates), expect the JSON output shape to change to a list of structures.
   - Optionally use `format=csv` or `format=xlsx` when you need data export.

7. Validate correctness with a “known city” check
   - Geocode “Berlin” → Forecast `hourly=temperature_2m` for 1–2 days → verify timezone and array lengths.
   - Air Quality `hourly=pm10,pm2_5,european_aqi` → verify units and presence of `hourly_units`.

## Critical prohibitions

- Do not include out-of-scope APIs in this skill’s implementation guidance: Historical Weather, Ensemble Models, Seasonal Forecast, Climate Change, Marine, Satellite Radiation, Elevation, Flood.
- Do not omit `timezone` when requesting `daily` variables (per docs).
- Do not assume `unixtime` timestamps are local time; they are GMT+0 and require `utc_offset_seconds` adjustment.
- Do not silently ignore `{"error": true}` responses; fail fast with the provided `reason`.
- Do not request huge variable sets by default; keep queries minimal to reduce payload and avoid accidental overuse.

## Definition of done

- You can geocode a place name and obtain coordinates/timezone.
- You can fetch Forecast data with at least one `hourly`, one `daily` (with timezone), and one `current` variable.
- You can fetch Air Quality data for at least one pollutant and one AQI metric.
- Your client code handles both HTTP-level failures and JSON-level `error: true` with clear messages.
- Attribution requirements from the docs are captured for Air Quality (CAMS) and Geocoding (GeoNames).

## Release Notes

- `1.7.0` (2026-10-16) changes the server side, not the request contract of `/v1/forecast`, `/v1/air-quality`, and the geocoding API: DWD ICON, ECMWF, KMA, and CMC providers moved to a shared internal structure, the DMI migration finished, and the icon API moved to v1 URLs with an EPS resolution switch (native icon grid domains added). A new environment variable limits the atomic block cache to pressure-level files.
- Fixes in the same release: HRRR and NAM wind direction is now relative to true north, ECMWF daily maximum/minimum temperatures are correct, missing temperature extrema are derived and daily interval aggregations aligned, and bounding-box requests account for model elevation.

## Links

- [Documentation](https://open-meteo.com/en/docs)
- [Releases](https://github.com/open-meteo/open-meteo/releases)
- [GitHub](https://github.com/open-meteo/open-meteo)

© itechmeat · MIT · itechmeat/llm-code

Similar skills

All skills for Backend and APIs →

From the same set16

The whole set →

Project sponsors

Companies that keep this analytics open