Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
Passed 21 of 21 test cases with the skill, and 10 of 21 without it.
and 12 more in the full report
12 fixed10 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
What default port number is used for distributed rendezvous by NeMo AutoModel's Slurm launcher when master_port is omitted?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies 13742 as the default master port | Missed | Passed |
The instructions your model reads when the skill loads.
NeMo AutoModel supports three launch methods: interactive (torchrun), Slurm (HPC clusters), and SkyPilot (cloud-agnostic).
For launcher questions, answer directly from this skill without inspecting the repository unless the user asks you to edit files. Keep the answer focused on the relevant launch YAML, required fields, and the expected runtime behavior.
Use these compact answer patterns for common questions:
slurm: YAML block with job_name, nodes,
ntasks_per_node, time, account or partition, container_image,
hf_home, optional extra_mounts, env_vars, and master_port; explain
that the launcher derives WORLD_SIZE = nodes * ntasks_per_node and sets
MASTER_ADDR and MASTER_PORT.skypilot: YAML block with cloud, accelerators,
num_nodes, use_spot: true, disk_size, region, setup, and
env_vars; warn that spot instances can be preempted, set a short
step_scheduler.checkpoint_interval, and resume with restore_from.path.slurm.nsys_enabled: true alongside normal
Slurm fields, say the launcher wraps the training command with
nsys profile, and state that it produces a .nsys-rep report file.
Treat profiling as diagnostic-only: use short profiling runs and disable it
for normal production training because it adds overhead and large artifacts.For Slurm answers, start with this minimal template and then adjust only the fields the user asked about:
slurm:
job_name: llm_finetune
nodes: 2
ntasks_per_node: 8
time: "04:00:00"
account: my_account
partition: batch
container_image: nvcr.io/nvidia/nemo:dev
hf_home: ~/.cache/huggingface
test cases passed, vs 10 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.