
earth2studio-create-prognostic
Create Earth2Studio prognostic (time-stepping forecast) model wrappers. Do NOT use for diagnostic models, data sources, or installation.
- Installs
- 575
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/nvidia/skills --skill earth2studio-create-prognostic- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads earth2studio-create-prognostic automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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>.pywith triple inheritance - Create
test/models/px/test_<name>.pywith 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 runfor 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 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:
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):
class ModelName(torch.nn.Module, AutoModelMixin, PrognosticMixin):
Required imports:
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):
# SPDX-FileCopyrightText: Copyright (c) 2024-2025 NVIDIA CORPORATION & AFFILIATES.
# SPDX-License-Identifier: Apache-2.0
Canonical method order:
__init__2.input_coords3.output_coords(@batch_coords)load_default_package5.load_model6.to(optional)- Private methods 8.
__call__(@batch_func) 9._default_generator create_iterator
Step 4 — Implement Coordinates
input_coords rules:
batch:np.empty(0)time:np.empty(0)(dynamic)lead_time: starts atnp.timedelta64(0, "h")lat: 90 to -90 (north to south); this is the public Earth2Studio convention even if the source model uses the opposite orderlon: 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_coordsoroutput_coords - Map variables to
E2STUDIO_VOCAB(282 entries inearth2studio/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:
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 bothpip install earth2studio[model-name]anduv add earth2studio --extra model-nameinstructions. - Update
CHANGELOG.mdunder### Added. This is required for every new prognostic model.
Format and lint:
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.mdreferences/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
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)
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
@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
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 pythonfor ALL Python commands - Use
loguru.logger, neverprint() - 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/
FAQ
What does the earth2studio-create-prognostic skill do?
Create Earth2Studio prognostic (time-stepping forecast) model wrappers. Do NOT use for diagnostic models, data sources, or installation.
How do I install earth2studio-create-prognostic?
Run npx skills add https://github.com/nvidia/skills --skill earth2studio-create-prognostic in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/earth2studio-create-prognostic/ (personal) or .claude/skills/earth2studio-create-prognostic/ (project).
Which AI agents can use earth2studio-create-prognostic?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is earth2studio-create-prognostic safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains earth2studio-create-prognostic?
It is published by nvidia in nvidia/skills, and it is an official skill from the maker of the technology it covers. It has 575 recorded installs.
More from nvidia/skills
rag-blueprint
nvidia/skills
NVIDIA RAG Blueprint — deploy, configure, troubleshoot, and manage. Handles any RAG action: deploy, install, start, enable, disable, toggle, change, configure, troubleshoot, debug, fix, shutdown, stop, or tear down any RAG feature or service (Agentic RAG, VLM, guardrails, query rewriting, models, search, ingestion, observability, summarization, reasoning, and more).
accelerated-computing-cudf
nvidia/skills
Official NVIDIA-authored guidance for NVIDIA cuDF GPU DataFrames, pandas acceleration, dask-cuDF, ETL, joins, groupby, CSV/Parquet I/O, nullable semantics, and multi-GPU DataFrame workloads.
aiq-research
nvidia/skills
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
cuopt-developer
nvidia/skills
Modify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions.
aiq-deploy
nvidia/skills
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
cuopt-install
nvidia/skills
Install cuOpt for Python, C, or server via pip, conda, or Docker; verify the install. For building cuOpt from source, see cuopt-developer.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.