Earth2studio Discover
NVIDIAOfficialCreated by NVIDIA Earth-2 Team
- Skill
- Research and analysis
- Data and AI
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The Earth2Studio Discover skill acts as a research assistant for users navigating the Earth2Studio ecosystem. It helps identify appropriate prognostic and diagnostic models, compatible data sources, and relevant gallery examples based on specific weather or climate use cases. By leveraging live documentation and the lexicon system, the skill ensures that recommendations are aligned with current model capabilities, hardware constraints, and variable requirements.
What it does
- Filters models based on task type, region, and hardware VRAM requirements.
- Verifies compatibility between data sources and models using the lexicon system.
- Maps user requirements to specific examples from the Earth2Studio gallery.
- Provides structured recommendations including model metadata and documentation links.
- Assists in selecting between deterministic and ensemble forecasting approaches.
When to use it
- When you need to identify which Earth2Studio model fits your specific climate or weather task.
- When you are unsure if a specific data source provides the variables required by a chosen model.
- When you want to find existing examples for workflows like downscaling or data assimilation.
- When you need to compare models based on GPU memory constraints or forecast range.
Advantages
- Ensures recommendations are based on live documentation rather than static, outdated information.
- Reduces technical friction by verifying variable compatibility via the lexicon system.
- Provides clear, structured guidance on model selection based on hardware and task constraints.
- Connects users directly to relevant, verified examples for rapid prototyping.
Usage examples
- “I need a medium-range global forecasting model that runs on 40GB of VRAM. What are my options?”
- The agent fetches the prognostic model documentation, filters for MR (medium-range) class models compatible with global regions and 40GB VRAM, and presents a shortlist with rationale.
- “Can I use GFS data with the GraphCastOperational model?”
- The agent checks the model's input_coords against the GFS lexicon VOCAB to confirm if all required variables are present and reports the compatibility status.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/earth2studio-discover/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip earth2studio-discover.zip -d .agents/skills
Documentation by NVIDIA Earth-2 Team
Earth2Studio Discoverability Skill
Purpose
Help users identify the right Earth2Studio models, data sources, and examples for their weather/climate task. Use when: comparing models by GPU/VRAM requirements, choosing forecast class (nowcast, medium-range, seasonal), finding compatible data sources via lexicons, or locating gallery examples for downscaling, ensemble generation, or data assimilation.
Prerequisites
Internet access to fetch live documentation pages from nvidia.github.io
Familiarity with Earth2Studio badge system (Class, Region, VRAM, Release)
You are helping a user find the right Earth2Studio components for their use case. Your job is to understand what they want to do, then point them at the models, data sources, and examples that fit — verified against live documentation.
Core principle: discover from live docs, don't memorize
Earth2Studio adds models, data sources, and examples every release. Model classes get new badges, new data sources appear, examples get reorganized. Any static list in this skill will rot.
Rules:
Always fetch the relevant live doc pages before recommending components.
Use badge metadata (Region, Class, VRAM, Release) from the docs to filter candidates.
Verify data-source ↔ model compatibility using the lexicon system (see Step 4).
Cite doc URLs so the user can explore further.
Live doc references
Fetch these pages as needed (not all at once — only what the user's question requires):
| Category | URL |
|---|---|
| Prognostic models | https://nvidia.github.io/earth2studio/modules/models_px.html |
| Diagnostic models | https://nvidia.github.io/earth2studio/modules/models_dx.html |
| Data assimilation | https://nvidia.github.io/earth2studio/modules/models_da.html |
| Data sources (analysis) | https://nvidia.github.io/earth2studio/modules/datasources_analysis.html |
| Data sources (forecast) | https://nvidia.github.io/earth2studio/modules/datasources_forecast.html |
| Data sources (dataframe) | https://nvidia.github.io/earth2studio/modules/datasources_dataframe.html |
| Examples gallery | https://nvidia.github.io/earth2studio/examples/index.html |
| Lexicon source | https://github.com/NVIDIA/earth2studio/tree/main/earth2studio/lexicon |
Interaction protocol
Step 1. Understand the user's problem
Extract from what the user has said (ask follow-ups if needed, cap at 3 questions):
Task type — medium-range forecasting, nowcasting, downscaling/super-resolution, seasonal/subseasonal, data assimilation, climate projection, ensemble generation, derived diagnostics
Region — global, North America, Europe, Asia, specific country/area
Temporal scale — hours ahead (nowcast), days ahead (medium-range), weeks/months (seasonal), climate
Variables of interest — temperature, precipitation, wind, pressure, radiation, specific levels, etc.
Hardware constraints — GPU type, available VRAM (40GB, 48GB, 80GB, 96GB)
Deterministic vs. ensemble — single forecast or probabilistic
Good follow-up phrasing: "Are you looking for a single best-estimate forecast or an ensemble with uncertainty?" — not "what's your use case?"
Step 2. Fetch relevant model docs
Based on the user's task type, fetch the appropriate model page(s):
Forecasting → prognostic models (px)
Post-processing / downscaling / derived variables → diagnostic models (dx)
Observation integration → data assimilation (da)
Often a workflow chains px → dx, so check both
From the doc pages, extract for each candidate model:
Class badge — NWC, DS, MR, S2S, DA, CM
Region badge — Global, NA, EU, AS, etc.
Rec VRAM badge — minimum GPU memory
Release year — newer models generally supersede older ones in the same class
Filter to models matching the user's task type, region, and hardware. Present a short-list (not the full catalog) with badge metadata.
Step 3. Fetch relevant data source docs
Based on the user's data needs, fetch the appropriate data source page:
Historical reanalysis → analysis data sources
Real-time or operational → forecast data sources
Observations / station data → dataframe data sources
Note which data sources cover the user's region and variables.
Step 4. Verify compatibility via lexicon
This is the key technical step. Earth2Studio models declare their required input variables via input_coords(). Data sources expose available variables through their lexicon VOCAB. If a data source's lexicon VOCAB keys contain all variables in a model's input_coords (the "variable" dimension), they are compatible.
To verify:
Check the model's doc page or source for its
input_coords— specifically the variable listCheck the data source's lexicon file at
earth2studio/lexicon/<source>.pyfor its VOCAB keysConfirm the data source VOCAB covers all variables the model needs
If checking source code directly (e.g. user has a local clone), the lexicon files are at:
earth2studio/lexicon/gfs.py
earth2studio/lexicon/hrrr.py
earth2studio/lexicon/cds.py
earth2studio/lexicon/arco.py
earth2studio/lexicon/wb2.py
... (one per data source)Each defines a VOCAB: dict[str, str | tuple] mapping Earth2Studio variable names to source-specific identifiers.
Surface compatibility results clearly: "GraphCastOperational needs [list of variables] — GFS and ERA5 (via ARCO/CDS) both provide these, but HRRR does not cover pressure levels above X."
Step 5. Suggest examples
Fetch the examples gallery and identify examples that demonstrate the user's workflow pattern. Examples are organized by category:
01_getting_started— basic deterministic, diagnostic, ensemble pipelines02_medium_range— ensemble extension, perturbation, cyclone tracking03_downscaling— CorrDiff, CBottle, ensemble downscaling04_nowcasting— StormCast, StormScope05_data_assimilation— StormCast SDA, HealDA06_seasonal— DLESyM, statistical methods07_misc— distributed inference, IO, custom data, generation08_extend— building custom models, diagnostics, data sources
Point the user at the most relevant 1–3 examples as starting points. Explain what each demonstrates and how it relates to their problem.
Step 6. Return recommendations
Output structure (omit empty sections):
## Your use case
[1-2 sentence restatement of what the user wants to do]
## Recommended models
| Model | Class | Region | VRAM | Why |
|-------|-------|--------|------|-----|
[Short-list with rationale per row]
## Compatible data sources
| Data Source | Coverage | Compatible with |
|-------------|----------|-----------------|
[Verified via lexicon]
## Relevant examples
- [Example name](link) — what it demonstrates
## Next steps
[What to install, what to read next]Keep recommendations to 2–4 models maximum. If multiple options exist, explain the tradeoff (accuracy vs. speed, deterministic vs. ensemble, VRAM, etc.) rather than listing everything.
Limitations
Recommendations are only as current as the live docs; unreleased models are not discoverable.
Badge metadata may be incomplete for newly added models.
Lexicon compatibility checks require source code access for full accuracy; doc-only checks are approximate.
Troubleshooting
| Error | Cause | Solution |
|---|---|---|
| Model page returns 404 | URL changed after a release | Check https://nvidia.github.io/earth2studio/ for updated navigation |
| Lexicon file not found | Data source is new or renamed | Search earth2studio/lexicon/ directory for current filenames |
| Badge missing from model | Model docs not yet updated | Fall back to the model's source code __init__ or README for specs |
Ownership and out-of-scope
Owns: component discovery, model/data-source compatibility checking, badge-based filtering, example recommendation, hardware-fit assessment.
Does not own: installation (use earth2studio-install skill), writing inference code, model training, custom model development, runtime debugging, PhysicsNeMo model discovery.
Files
- ATTRIBUTION.mdAdded by AutoGineer934 B
- BENCHMARK.md3.9 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md8.3 KiB
- evals/evals.json4.8 KiB
- skill-card.md4.0 KiB
- skill.oms.sig4.5 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- NVIDIA Earth-2 Team
- Publisher
- NVIDIA (Official)
- Source
- NVIDIA/skills · skills/earth2studio-discover · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by NVIDIA Earth-2 Team or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download earth2studio-discover.zip