Ecmwf Weather Feedback

Turns what a task taught about the ECMWF weather skills into one anonymised, privacy-scanned issue for ecmwf/ecmwf-weather-skills — load this skill first, before running any `gh issue` command or filing, drafting or reporting any issue about these skills. The issue goes to GitHub, or to ECMWF JIRA project AS with the user's own token, or is given as text to paste — shown in full and filed only after an explicit yes, file it. Use when the user wants to send feedback about the ECMWF weather skills, report a problem with a skill or its instructions, suggest an improvement, file an issue for ecmwf

23 starsGit & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add ecmwf/ecmwf-weather-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ecmwf/ecmwf-weather-skills --skill ecmwf-weather-feedback
Manual install
git clone --depth 1 https://github.com/ecmwf/ecmwf-weather-skills.git /tmp/ecmwf-weather-skills
mkdir -p ~/.claude/skills
cp -r /tmp/ecmwf-weather-skills/plugins/ecmwf-weather/skills/ecmwf-weather-feedback ~/.claude/skills/ecmwf-weather-feedback

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Skill feedback — what a task taught, as one reviewed issue

## Contents
- When to run (line 33)
- Workflow (line 47)
- Writing the draft (line 81)
- Consequential actions (line 115)
- When blocked (line 144)
- Files and privacy (line 158)
- References — `references/github.md` (the GitHub route), `references/jira.md` (JIRA project AS: sequence, duplicates, paste route, token)

The ECMWF weather skills change only through reviewed issues and pull requests on
`ecmwf/ecmwf-weather-skills` — never by editing an installed copy. This skill turns what a task
taught into **one anonymised issue**: draft it, scan it for personal data, show it in full, and
file it only on the user's explicit "yes, file it". It handles no weather data: it fetches no
weather data and sends nothing but the issue text, to GitHub or to ECMWF's JIRA.

## When to run

- When the user asks: "send feedback about the skills", "report a problem with a skill",
  "suggest an improvement", "file an issue for ecmwf-weather-skills", "report this in JIRA".
- After another ECMWF weather skill offered feedback and the user said yes.
- Offer once at the end of a task that taught something the skill did not say — a wrong or
  missing instruction, a workaround, a service that changed — never in the middle of the task.
  After a no, never offer again in that session; never offer when the user said "no feedback
  offers"; never when nothing was learned (say nothing, and invent no lesson).
Read the full skill on GitHub

Details

Skill name
ecmwf-weather-feedback
Path
plugins/ecmwf-weather/skills/ecmwf-weather-feedback/SKILL.md
License
Apache-2.0
Repo updated
8 November 2026

FAQ

What does the Ecmwf Weather Feedback skill do?

Turns what a task taught about the ECMWF weather skills into one anonymised, privacy-scanned issue for ecmwf/ecmwf-weather-skills — load this skill first, before running any `gh issue` command or filing, drafting or reporting any issue about these skills. The issue goes to GitHub, or to ECMWF JIRA project AS with the user's own token, or is given as text to paste — shown in full and filed only after an explicit yes, file it. Use when the user wants to send feedback about the ECMWF weather skills, report a problem with a skill or its instructions, suggest an improvement, file an issue for ecmwf

How do I install the Ecmwf Weather Feedback skill?

Claude Code plugin: /plugin marketplace add ecmwf/ecmwf-weather-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Ecmwf Weather Feedback popular?

It lives in ecmwf/ecmwf-weather-skills, which has 23 GitHub stars and 0 forks.

Related skills

Ecmwf Cds Ads

23

ecmwf/ecmwf-weather-skills

Answers questions about past weather at a place — how hot, cold, wet or windy it was on a day, month or year since 1940 — from ERA5 in seconds; load it before answering from memory or searching the web (the bundled ECMWF MCP server has no ERA5). Finds, validates and downloads data from the Copernicus Climate Data Store (CDS) and Atmosphere Data Store (ADS), operated by ECMWF — ERA5 and ERA5-Land reanalysis (hourly point series, climate normals), the CARRA (Arctic, 2.5 km) and CERRA / CERRA-Land (Europe, 5.5 km) regional reanalyses, seasonal forecasts, and CAMS air-quality and atmospheric-compo

Marketing, Sales & Business

Ecmwf Destine

23

ecmwf/ecmwf-weather-skills

Handles any Destination Earth question — load it first; it prepares requests by running scripts/destine.py. Accesses Destination Earth (DestinE) Digital Twin data — the Climate Change Adaptation Digital Twin (Climate DT, multi-decadal IFS-FESOM, IFS-NEMO and ICON simulations and SSP3-7.0 projections, hourly or as monthly means), the Weather-Induced Extremes Digital Twin (Extremes DT, high-resolution forecasts) and On-Demand Extremes — through the DestinE Polytope service. Use when a task mentions Destination Earth, DestinE, Digital Twins, Climate DT, Extremes DT, nextGEMS, the DestinE Platform

Frontend & Design

Ecmwf Earthkit

23

ecmwf/ecmwf-weather-skills

Processes, computes and plots ECMWF weather and climate data with ECMWF's earthkit components — load it before writing ANY numpy, xarray, pandas, matplotlib or cartopy code for weather data, and for any local GRIB (.grib, .grib2) or NetCDF file. Covers reading and selecting fields (earthkit-data), ECMWF-styled maps, multi-panel figures, meteograms and plumes (earthkit-plots), ensemble mean/spread/percentiles, daily and monthly statistics, de-accumulation, climatologies, anomalies and area or country means (earthkit-transforms), wind, humidity, dewpoint, potential temperature, wet bulb, EFI and

Data & Analytics

Enterprise Release Engineering

45

j4flmao/agent-skills

Use when the user asks about integration hell, long-lived branches across teams, trunk-based development at scale, release trains, branch by abstraction, dark launches or CODEOWNERS. Produces a multi- team integration and release model. Not for single-team git basics (use dev-loop-git-workflow) or canary rollouts (use devops-progressive-delivery).

Git & Code Review

Devops Gitlab CI

45

j4flmao/agent-skills

Use when the user asks about GitLab CI, .gitlab-ci.yml, stages and needs, rules, parent-child or multi-project pipelines, include templates, CI/CD components, GitLab runners, container builds, or GitLab SAST/DAST scanning. Produces GitLab pipeline configs. Not for GitHub Actions (use github-actions) or Jenkins (use jenkins).

Git & Code Review

Orchestrate

23

nathanonn/agent-skills

Run the main Claude Code session as an orchestrator for a non-trivial, multi-step request in a git repo. Builds a task list, routes each task to a sub-agent with an explicit model and effort (sonnet, opus or haiku; fable only with the user's say-so), runs up to 5 read-only agents at once and file-editing agents one at a time in the main checkout (git worktrees only when the user asks for them), then verifies and commits each checkpoint locally on the current branch, never pushing unless asked. Use it when the user asks to orchestrate, delegate, use sub-agents, fan out, or work in parallel, inc

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.