SKILLEMALL.ai

BF nemo-automodel-recipe-development

Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow. Use when creating or modifying training, SFT, or eval recipes, adding new YAML config fields, debugging recipe construction or trainer issues, or understanding the recipe execution flow.

NVIDIA-NeMo/Automodel Agent Skills author: NVIDIA-NeMo 4 files body ≈ 2 864 tokens Open the sourcegithub.com↗ analyzed 8 h ago

Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.

As a process F 34/100 · No process to follow — References files that are not bundled: ../../docs/guides/mixed-precision-training.mdx

AnalyzerSoftware developmentInfrastructureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
F
34/100
No process to follow
References files that are not bundled: ../../docs/guides/mixed-precision-training.mdx
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../docs/guides/mixed-precision-training.mdx

Process rating: all ten parameters 34/100

Will not run. References files that are not bundled: ../../docs/guides/mixed-precision-training.mdx
  • 0Tools and files. 1 referenced file(s) missing: ../../docs/guides/mixed-precision-training.mdx
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 5 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 85Steps. 58 steps, 3 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2864 tokens
  • medium 3 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 308: enough signal without eating the budget
  • +4Structure: 27 headings
  • +3Step-by-step instructions: 58 items
  • +4Has examples (7 code blocks)
  • +1License stated

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