Skip to main content
skill CX Codex

earth2studio-create-prognostic — Claude Code skill for model wrappers

Guides an agent through building an Earth2Studio wrapper for a weather model that forecasts future states over successive time steps.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add NVIDIA/skills --skill earth2studio-create-prognostic -a claude-code
Open on GitHub

What earth2studio-create-prognostic does

This skill walks an agent through a Python wrapper for a prognostic weather model. Provide a URL or local path to an inference script; the agent inspects its packages, architecture, input and output shapes, time step, and resolution, then asks you to approve the proposed dependencies.

The workflow covers the model class, coordinate handling, forward pass, model loading, tests, and project documentation. It includes mock tests and a test that loads real weights, and directs Python commands through uv run. Its scope is prognostic models; it does not cover diagnostic models, data sources, or installation.

What it helps with

  • wrap a third-party weather forecasting model for Earth2Studio
  • inspect a model's dependencies and input and output shapes
  • test a forward pass, iterator, and invalid coordinate handling
  • add a model's optional dependencies and documentation

Example prompts for the agent

  • Build an Earth2Studio wrapper from the inference script at inference.py.
  • Inspect this inference script URL, propose dependencies, and wait for my approval.
  • Add a prognostic model under earth2studio/models/px/ and prepare its tests.

How to install earth2studio-create-prognostic

1Skills CLI (Vercel)

npx skills add NVIDIA/skills --skill earth2studio-create-prognostic -a claude-code

2Manually: put the files in place

~/.claude/skills/earth2studio-create-prognostic/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/earth2studio-create-prognostic/

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

Questions about earth2studio-create-prognostic

How do I install earth2studio-create-prognostic in Claude Code?

Run npx skills add NVIDIA/skills --skill earth2studio-create-prognostic -a claude-code. The skill file is placed at ~/.claude/skills/earth2studio-create-prognostic/SKILL.md.

What does earth2studio-create-prognostic do?

It guides an agent in building an Earth2Studio wrapper for a prognostic weather model, including dependency review, tests, and documentation updates.

What should I provide to use the skill?

Give it a URL or local path to an inference script. If you provide no argument, it asks you for one.

Source text

SKILL.md · Apache-2.0
---
name: earth2studio-create-prognostic
version: 0.16.0
license: Apache-2.0
metadata:
  author: NVIDIA Earth-2 Team <[email protected]>
  tags: [earth2studio, prognostic-model, python]
description: >
  Create Earth2Studio prognostic (time-stepping forecast) model wrappers.
  Do NOT use for diagnostic models, data sources, or installation.
argument-hint: URL or local path to reference inference script (optional)
---

## Quick Start Checklist

**Do these steps IN ORDER. Do not skip any step.**

- [ ] Read this SKILL.md completely first
- [ ] Get reference script (Step 0)
- [ ] Create `earth2studio/models/px/<name>.py` with triple inheritance
- [ ] Create `test/models/px/test_<name>.py` with mock tests
- [ ] Run: `uv run pytest test/models/px/test_<name>.py -v`
- [ ] Add/update model extra, install docs, API docs, and changelog (Steps 1-2, 9)
- [ ] Run: `make format && make lint`

> **⚠️ CRITICAL:** Always use `uv run` for Python commands:
> - ✅ `uv run pytest ...` / `uv run python ...`
> - ❌ `pytest ...` / `python ...` (missing dependencies)
>
> **Stuck or wrong output:** Do not keep retrying the same fix. Follow
> [Self-Improvement](#self-improvement) to patch this skill before continuing.

## Purpose

Implement a prognostic model wrapper connecting third-party ML weather models
to Earth2Studio. Prognostic models time-integrate forward—given initial state,
they predict future states by stepping through time (e.g., 6-hour increments).

## Workspace

| Context | Location |
|---------|----------|
| Harbor eval | Write to `/workspace/output/earth2studio/models/px/...` |
| Harbor + `--copy-repo` | Full checkout at `/workspace/repo` |
| Local clone | Directory with `pyproject.toml` |

**Never read `evals/targets/`** — grader references only.

### Reference Files

Load on demand during the matching step:

| File | Content | Load at |
|------|---------|---------|
| `references/skeleton-template.py` | Full model skeleton with FILL comments | Steps 3–6 |
| `references/method-templates.py` | Canonical method implementations | Steps 4–6 |
| `references/testing-guide.py` | Test skeleton and mock patterns | Step 7 |
| `references/validation-guide.md` | Comparison scripts, PR, code review | Steps 10–11 |

---

## Workflow Steps

### Step 0 — Get Reference Script

If `$ARGUMENTS` provided, use it. Otherwise ask:
> Please provide a reference inference script URL/path.

### Step 1 — Analyze & Propose Dependencies

Analyze: packages, architecture, I/O shapes, time step, resolution, checkpoint.

Propose `pyproject.toml` group (alphabetical, add to `all`). Every
prognostic model must have an optional dependency extra, even when no packages
are required:
```toml
model-name = ["package1>=version", "package2"]
# or, when no additional packages are required:
model-name = []
```

**[CONFIRM]** Present dependencies and ask user to approve.

### Step 2 — Add Dependencies

Edit `pyproject.toml`: add the model extra alphabetically, even if it is
empty, and update the `all` aggregate.

### Step 3 — Create Model File

**File:** `earth2studio/models/px/<lowercase>.py`

**Required inheritance (all three):**
```python
class ModelName(torch.nn.Module, AutoModelMixin, PrognosticMixin):
```

**Required imports:**
```python
import numpy as np
import torch
from earth2studio.models.auto import AutoModelMixin, Package
from earth2studio.models.batch import batch_coords, batch_func
from earth2studio.models.px.base import PrognosticMixin
from earth2studio.models.utils import create_coords_from_lat_lon, handshake_dim
from earth2studio.lexicon import E2STUDIO_VOCAB
from earth2studio.utils import check_optional_dependencies
from loguru import logger
```

**SPDX header (required at top of every .py file):**
```python
# SPDX-FileCopyrightText: Copyright (c) 2024-2025 NVIDIA CORPORATION & AFFILIATES.
# SPDX-License-Identifier: Apache-2.0
```

**Canonical method order:**
1. `__init__` 2. `input_coords` 3. `output_coords` (@batch_coords)
4. `load_default_package` 5. `load_model` 6. `to` (optional)
7. Private methods 8. `__call__` (@batch_func) 9. `_default_generator`
10. `create_iterator`

### Step 4 — Implement Coordinates

**input_coords rules:**
- `batch`: `np.empty(0)`
- `time`: `np.empty(0)` (dynamic)
- `lead_time`: starts at `np.timedelta64(0, "h")`
- `lat`: 90 to -90 (north to south); this is the public Earth2Studio convention even if the source model uses the opposite order
- `lon`: 0 to 360
- If a checkpoint/model core expects south-to-north latitude, flip tensors internally before/after the core model; do not expose flipped latitude in `input_coords` or `output_coords`
- Map variables to `E2STUDIO_VOCAB` (282 entries in `earth2studio/lexicon/base.py`)

**output_coords:** Use `handshake_dim`/`handshake_coords` for input validation, then increment `lead_time`. Prefer a shared coordinate-check helper and call it from `output_coords`, `__call__`, and iterator setup before model execution.

### Step 5 — Implement Forward Pass

**`__call__`:** @batch_func decorated, shape (batch, time, lead_time, var, lat, lon).
Reshape to model format → call model → reshape back.

**`create_iterator`:** MUST yield initial condition first (step 0).
Use `front_hook`/`rear_hook` for perturbation injection.

### Step 6 — Implement Model Loading

**`load_default_package`:** Lock HuggingFace URLs: `hf://org/repo@commit`

**`load_model`:** Use `package.resolve()`, `map_location="cpu"`, `eval()` mode,
decorate with `@check_optional_dependencies()`.

### Step 7 — Write Tests

**File:** `test/models/px/test_<name>.py`

**Required tests:**
| Function | Purpose |
|----------|---------|
| `test_<model>_call` | Single forward pass (parametrize device/time) |
| `test_<model>_iter` | Iterator produces sequence |
| `test_<model>_exceptions` | Invalid coords raise errors |
| `test_<model>_package` | Real weights (`@pytest.mark.package`) |

Create `PhooModelName` dummy matching interface for mock tests.

**Run tests:**
```bash
uv run pytest test/models/px/test_<name>.py -m "not package" -v
uv run pytest test/models/px/test_<name>.py::test_<model>_package --package -v
```

Do not omit the package test. If arbitrary random inputs are not physically
valid for the real checkpoint, use a stable model-appropriate synthetic input
while still loading real weights and running a forward pass.

### Step 8 — Register Model (if requested)

- Add to `earth2studio/models/px/__init__.py` (alphabetical)
- Verify deps in pyproject.toml

### Step 9 — Documentation

- Add to `docs/modules/models_px.rst` (alphabetical). This is required for
  every new prognostic model so the API docs include the generated page.
- Add to `docs/userguide/about/install.md` (alphabetical tab) for the
  model extra, even when the extra is empty. Include model-specific notes plus
  both `pip install earth2studio[model-name]` and
  `uv add earth2studio --extra model-name` instructions.
- Update `CHANGELOG.md` under `### Added`. This is required for every new
  prognostic model.

**Format and lint:**
```bash
make format && make lint && make license
```

### Step 10 - Validation (if requested)

Follow `references/validation-guide.md`. Create uncommitted vanilla, E2S,
comparison, and sanity-check scripts; do not commit generated outputs or images.
Use PR-safe placeholders for plots so the user can upload images manually.

**[CONFIRM]** User must visually inspect plots before proceeding.

### Step 11 - PR (if requested)

Follow `references/validation-guide.md` and use:
- `references/pr-body-template.md`
- `references/pr-comment-template.md`

Before creating the PR, verify `pyproject.toml` has the model extra, the
`all` extra includes it, install docs include both pip and uv commands, and
`docs/modules/models_px.rst` plus `CHANGELOG.md` are updated.

Do not include machine names, absolute paths, device inventory, or uploaded image
links in PR text. Use plot placeholders instead.

---

## Examples

### Simple Identity Model
```text
User: Create IdentityModel - returns input unchanged, 6h step, 181x360, vars: t2m, u10m, v10m, msl

Agent: [reads SKILL.md, creates identity.py with triple inheritance,
        creates test_identity.py, runs pytest, runs make format && lint]
```

### External Model (Pangu)
```text
User: Add Pangu-Weather wrapper
      GitHub: https://github.com/198808xc/Pangu-Weather

Agent: [reads SKILL.md, fetches inference.py, creates pangu.py,
        creates test_pangu.py, runs pytest]
```

---

## Key Patterns

### Coordinate Template
```python
@property
def input_coords(self) -> CoordSystem:
    return CoordSystem({
        "batch": np.empty(0),
        "time": np.empty(0),
        "lead_time": np.array([np.timedelta64(0, "h")]),
        "variable": np.array(["t2m", "u10m", ...]),
        # Public Earth2Studio convention is north-to-south latitude.
        "lat": np.linspace(90, -90, 181),
        "lon": np.linspace(0, 359, 360),
    })

@batch_coords()
def output_coords(self, input_coords: CoordSystem) -> CoordSystem:
    output = input_coords.copy()
    output["lead_time"] = input_coords["lead_time"] + np.timedelta64(6, "h")
    return output
```

### Iterator Template
```python
def create_iterator(self, x, coords):
    yield x, coords  # Initial condition (step 0)
    while True:
        x, coords = self.front_hook(x, coords)
        x, coords = self(x, coords)
        x, coords = self.rear_hook(x, coords)
        yield x, coords
```

---

## Troubleshooting

| Error | Solution |
|-------|----------|
| `OptionalDependencyFailure` | `uv add --optional <group> <pkg>` |
| Coordinate handshake fails | Check `handshake_dim` indices match dim position |
| Iterator wrong shapes | Debug reshape logic with random input |
| `ModuleNotFoundError: pytest` | Use `uv run pytest` not `pytest` |

---

## Reminders

**DO:**
- Use `uv run python` for ALL Python commands
- Use `loguru.logger`, never `print()`
- Inherit `torch.nn.Module + AutoModelMixin + PrognosticMixin`
- Yield initial condition first in `create_iterator`
- Use `front_hook()`/`rear_hook()` in `_default_generator`
- Include SPDX header in every .py file

**DON'T:**
- Create general base classes for reuse
- Commit API keys or comparison scripts
- Read from `evals/targets/`

© NVIDIA Earth-2 Team · Apache-2.0 · NVIDIA/skills

Similar skills

SKILL.md skills catalog →

From the same set194

deepstream-generate-pipeline Builds gst-launch-1.0 commands for DeepStream from a described task. Use it for video or image inference, tracking, streaming, and output handling. CX Codex +1 771installs deepstream-profile-pipeline Profiles DeepStream pipelines with Nsight Systems to tune configs from benchmark data. Helps optimize batch sizes and locate bottlenecks without guessing. CX Codex +1 750installs deepstream-sop Gives the agent the layout of NVIDIA's DeepStream SOP microservice, so it can build, debug and time a service that verifies the order of assembly steps. CX Codex +1 694installs amc-run-video-calibration Runs pre-recorded multi-camera MP4 files through the AutoMagicCalib REST API: creates a project, uploads videos, calibrates and evaluates. CX Codex +1 654installs amc-setup-calibration-stack Launches the AutoMagicCalib microservice and web UI from NGC containers using Docker Compose. It requires an NGC API key and a configured NVIDIA Docker Runtime. CX Codex +1 640installs amc-run-sample-calibration Runs end-to-end calibration on a bundled warehouse sample dataset against a running AutoMagicCalib service. It helps verify your AMC microservice before feeding real video streams. CX Codex +1 639installs earth2studio-create-datasource End-to-end skill for building and validating Earth2Studio remote data source wrappers. Connects cloud storage or HTTP datasets to Earth2Studio async fetching. CX Codex +1 581installs earth2studio-create-diagnostic Builds Earth2Studio diagnostic model wrappers for single-step ML transforms. Useful when integrating derived, AutoModel, or generative diagnostics without time-stepping. CX Codex +1 576installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor