SKILLEMALL.ai

AC earth2studio-create-prognostic

Create Earth2Studio prognostic (time-stepping forecast) model wrappers. Do NOT use for diagnostic models, data sources, or installation. The user may optionally supply a URL or a local path to a reference inference script.

NVIDIA/earth2studio Agent Skills author: NVIDIA 17 files · 8 scripts body ≈ 2 464 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Create Earth2Studio prognostic (time-stepping forecast) model wrappers.

As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

GeneratorWriting and documentsData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
93
Run on models
none yet
Process rating
C
55/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
Inputs and preconditions w 11
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 55/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 30Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 11 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (python) that frontmatter does not declare
    • 100Steps. 34 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2464 tokens
    • low The response is described with custom markup (10 tags): a typed call is more reliable
    • medium 2 test cases, all positive: not one "should refuse" or "should ask first"

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 222: enough signal without eating the budget
    • +4Structure: 25 headings
    • +3Step-by-step instructions: 34 items
    • +4Has examples (10 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.