[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PQE8MJHDJ36XC9CCSV6Y7H":3,"skill-same:01M6PQE8MJHDJ36XC9CCSV6Y7H":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6PQE8MJHDJ36XC9CCSV6Y7H","nemo-automodel-recipe-development",null,"Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.","headmktlucca-ui\u002Fneuroads-lp","headmktlucca-ui","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F247379838?v=4","01M6PDVAV6M1W96D1SR1PDF8CS","NeuroAds","01M6PDVAZ4P281GNDKD45CYTF5",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fnemo-automodel-recipe-development\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"nemo automodel recipe development","development","recipe development","recipe","NeMo","flow","fields","SFT","recipes","structure","eval","execution","config","NVIDIA","Evaluation","yaml","issues","create","debugging","training","2026-11-10 10:12:30",false,"---\nname: nemo-automodel-recipe-development\ndescription: Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.\nwhen_to_use: 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.\nlicense: Apache-2.0\nmetadata:\n  author: NVIDIA\n  tags:\n    - nemo-automodel\n    - recipe-development\n---\n\n# NeMo AutoModel Recipe Development\n\n## Instructions\n\nFor recipe questions, answer with the smallest complete path to action:\n\n1. Name the relevant recipe file or YAML section.\n2. List the builder functions or config keys involved.\n3. Include a minimal YAML or command example when the question asks how to\n   configure something.\n4. End with a local validation command or tiny CPU-compatible test.\n\nFor conceptual recipe questions, answer from this skill without inspecting the\nrepository or loading other AutoModel skills unless the user asks you to edit\nfiles. Keep the response focused on recipe YAML, builders, CLI routing, tests,\nand local validation.\n\nUse these compact answer patterns for common questions:\n\n- New finetuning recipe variant: start from the closest file under\n  `nemo_automodel\u002Frecipes\u002F`, update the model, dataset or dataloader,\n  optimizer, loss, LR scheduler, step scheduler, and checkpoint builders,\n  register a CLI route only if adding a command or domain alias, add example\n  YAML under `examples\u002F`, then add a tiny CPU-compatible unit test and run\n  `automodel finetune llm -c \u003Cconfig.yaml>`.\n- `_target_` fields: describe `_target_` as the fully qualified Python callable,\n  explain that sibling keys become keyword arguments, show optimizer and dataset\n  examples, and mention nested CLI overrides such as `--optimizer.lr`.\n- Validation and checkpointing: name `step_scheduler.val_check_interval`,\n  `step_scheduler.checkpoint_interval`, `validation_dataset`,\n  `restore_from.path`, and consolidated safetensors; include the minimal YAML\n  snippet from this skill.\n\nFor validation and checkpointing, always name:\n\n- `step_scheduler.val_check_interval` for validation cadence.\n- `step_scheduler.checkpoint_interval` for save cadence.\n- `validation_dataset` as the validation dataloader source.\n- `restore_from.path` for resume.\n- Consolidated safetensors as the default checkpoint format for HF ecosystem\n  compatibility.\n\n## Routing Boundary\n\nUse this skill for recipe construction and execution-flow questions: YAML\nstructure, `_target_` callables, builder functions, validation datasets,\ncheckpoint configuration, CLI route registration, and recipe-specific tests.\n\nDo not use this skill for standalone distributed strategy selection, cluster\nlauncher configuration, or model architecture onboarding unless the user is\nasking how those choices appear inside an AutoModel recipe YAML.\n\n## Recipe Architecture\n\n### Execution Flow\n\n```\nCLI (automodel finetune llm -c config.yaml)\n  -> app.py parses command + domain + config\n    -> recipe script (e.g. train_ft.py) main(config_path)\n      -> Recipe class .setup() builds all components\n        -> .run_train_validation_loop() executes training\n```\n\n### Recipe Class\n\nRecipes inherit from `BaseRecipe` and implement two methods:\n\n- `setup()` -- builds model, optimizer, dataloader, loss, LR scheduler, step scheduler, and checkpoint config via builder functions.\n- `run_train_validation_loop()` -- executes the training and validation loop.\n\n### Builder Pattern\n\nAll components are constructed through dedicated builder functions:\n\n- `build_model()` -- instantiates the model from config\n- `build_optimizer()` -- creates optimizer (AdamW, etc.)\n- `build_dataloader()` -- sets up train and validation dataloaders\n- `build_loss_fn()` -- creates the loss function\n- `build_lr_scheduler()` -- creates the learning rate scheduler\n- `build_step_scheduler()` -- creates the step scheduler controlling training progression\n- `build_checkpoint_config()` -- configures checkpointing\n\n### Infrastructure Application Order\n\nComponents are applied in this strict order after building:\n\n1. PEFT (LoRA, etc.)\n2. FP8 quantization\n3. QAT (quantization-aware training)\n4. Checkpoint load \u002F restore\n5. Parameter freezing\n6. Sharding (FSDP2, Megatron-FSDP, DDP)\n7. Device placement\n8. `torch.compile`\n9. Context parallelism hooks\n\n## YAML Config Anatomy\n\nA complete recipe config follows this structure:\n\n```yaml\nstep_scheduler:\n  max_steps: 1000\n  num_epochs: 1\n  grad_accumulation_steps: 4\n  val_check_interval: 100\n  checkpoint_interval: 500\n  log_interval: 10\n\ndist_env:\n  master_addr: localhost\n  master_port: 29500\n\nrng:\n  seed: 42\n\nmodel:\n  _target_: nemo_automodel.models.llm.NemotronHForCausalLM\n  name_or_path: meta-llama\u002FLlama-3.2-1B\n  # additional model kwargs passed to the constructor\n\ncompile:\n  enabled: false\n  backend: inductor\n\nclip_grad_norm:\n  max_norm: 1.0\n\ndistributed:\n  strategy: fsdp2       # fsdp2 | megatron_fsdp | ddp\n  dp_size: auto\n  tp_size: 1\n  cp_size: 1\n\nloss_fn:\n  _target_: torch.nn.CrossEntropyLoss\n\ndataset:\n  _target_: nemo_automodel.datasets.squad.SquadDataset\n  tokenizer_name_or_path: meta-llama\u002FLlama-3.2-1B\n  max_seq_length: 2048\n\nvalidation_dataset:\n  _target_: nemo_automodel.datasets.squad.SquadDataset\n  split: validation\n\npacked_sequence:\n  enabled: false\n\ndataloader:\n  batch_size: 4\n  num_workers: 4\n  pin_memory: true\n\noptimizer:\n  _target_: torch.optim.AdamW\n  lr: 2.0e-5\n  weight_decay: 0.01\n\nlr_scheduler:\n  _target_: nemo_automodel.schedulers.CosineAnnealingWarmup\n  warmup_steps: 50\n  min_lr: 1.0e-6\n```\n\n### The `_target_` Pattern\n\nThe `_target_` key specifies a fully qualified Python callable. All remaining keys in that section are passed as keyword arguments:\n\n```yaml\noptimizer:\n  _target_: torch.optim.AdamW   # callable\n  lr: 2.0e-5                    # kwarg\n  weight_decay: 0.01            # kwarg\n```\n\nThis is equivalent to: `torch.optim.AdamW(lr=2e-5, weight_decay=0.01)`.\n\n### CLI Overrides\n\nAny config value can be overridden from the command line:\n\n```bash\nautomodel finetune llm -c config.yaml \\\n  --optimizer.lr 1e-4 \\\n  --step_scheduler.max_steps 500 \\\n  --distributed.tp_size 2\n```\n\n## Examples\n\nValidation and checkpointing:\n\n```yaml\nstep_scheduler:\n  val_check_interval: 100\n  checkpoint_interval: 500\n\nvalidation_dataset:\n  _target_: nemo_automodel.datasets.squad.SquadDataset\n  split: validation\n\nrestore_from:\n  path: \u002Fcheckpoints\u002Fstep-500\n```\n\n## Domain-Specific Notes\n\n### LLM\n\n- `nemo_automodel\u002Frecipes\u002Fllm\u002Ftrain_ft.py` handles both finetuning and pretraining. The distinction is in the config (dataset, learning rate, etc.).\n- `nemo_automodel\u002Frecipes\u002Fllm\u002Fkd.py` implements knowledge distillation with a teacher and student model.\n- `nemo_automodel\u002Frecipes\u002Fllm\u002Fbenchmark.py` runs throughput and latency benchmarks.\n\n### VLM\n\n- Uses `NeMoAutoModelForImageTextToText` instead of causal LM classes.\n- Config includes a `processor` section instead of a standalone tokenizer.\n- Recipe lives in `nemo_automodel\u002Frecipes\u002Fvlm\u002Ffinetune.py`.\n\n### Diffusion\n\n- Uses `NeMoAutoDiffusionPipeline`.\n- Requires a `parallel_scheme` dict in config to define parallelism.\n- Only supports DDP and FSDP2 strategies (no Megatron-FSDP).\n- Recipe lives in `nemo_automodel\u002Frecipes\u002Fdiffusion\u002Ftrain.py`.\n\n### Retrieval\n\n- Two encoder patterns:\n  - **Bi-encoder** (`nemo_automodel\u002Frecipes\u002Fretrieval\u002Ftrain_bi_encoder.py`): separate query and document encoders, contrastive loss.\n  - **Cross-encoder** (`nemo_automodel\u002Frecipes\u002Fretrieval\u002Ftrain_cross_encoder.py`): joint encoding, classification head.\n- Hard negative mining: `nemo_automodel\u002Frecipes\u002Fretrieval\u002Fmine_hard_negatives.py`.\n\n## Training Loop Details\n\nThe training loop follows this structure per epoch:\n\n```\nfor epoch in range(num_epochs):\n    for batch_idx in range(batches_per_epoch):\n        # --- gradient accumulation inner loop ---\n        for micro_batch in micro_batches:\n            if pipeline_parallel:\n                schedule.step(micro_batch)    # PP schedule\n            else:\n                loss = model(micro_batch)     # direct forward\n                loss.backward()\n\n        # --- optimizer step ---\n        scale_grads_and_clip_grad_norm(model, max_norm)\n        optimizer.step()\n        lr_scheduler.step()\n        optimizer.zero_grad()\n\n        # --- logging ---\n        MetricsSample(step, epoch, loss, grad_norm, lr, mem, tps, mfu)\n\n        # --- validation (at configured intervals) ---\n        if step % val_check_interval == 0:\n            run_validation()\n\n        # --- checkpoint (at configured intervals) ---\n        if step % checkpoint_interval == 0:\n            save_checkpoint()\n```\n\n### StepScheduler\n\nControls all training progression: total epochs, total steps, gradient accumulation steps, validation interval, checkpoint interval, and logging interval.\n\n### Gradient Clipping\n\nApplied via `scale_grads_and_clip_grad_norm()` after the backward pass and before the optimizer step. Controlled by `clip_grad_norm.max_norm` in config.\n\n### Context Parallelism\n\nWhen `cp_size > 1`, batches are split across the context-parallel group using `make_cp_batch_and_ctx()`. This must happen before the forward pass.\n\n### MetricsSample\n\nEach training step produces a `MetricsSample` with fields:\n\n- `step` -- global step count\n- `epoch` -- current epoch\n- `loss` -- training loss\n- `grad_norm` -- gradient norm after clipping\n- `lr` -- current learning rate\n- `mem` -- GPU memory usage\n- `tps` -- tokens per second\n- `mfu` -- model FLOPS utilization\n\n## Validation & Checkpointing\n\n### Validation\n\n- Runs at intervals defined by `step_scheduler.val_check_interval`.\n- Uses the validation dataloader built from `validation_dataset` config.\n- Model is set to eval mode; gradients are disabled.\n\n### Checkpointing\n\n- Default format: consolidated safetensors for easy deployment on HF ecosystem (always prefer this over DCP).\n- Checkpoint interval controlled by `step_scheduler.checkpoint_interval`.\n- Resume training via the `restore_from` config key pointing to a checkpoint directory.\n\n```yaml\nrestore_from:\n  path: \u002Fcheckpoints\u002Fstep-500\n```\n\n## Pitfalls\n\n| Problem | Cause | Fix |\n|---|---|---|\n| Silent config errors | Typo in `_target_` value | The class path must be a valid, importable Python callable. Double-check the module path and class name. |\n| Training crashes at first step | `global_batch_size` not divisible by `local_batch_size * dp_size * grad_accumulation_steps` | Ensure the batch size math is consistent across all dimensions. |\n| New recipe not accessible via CLI | Missing CLI command alias registration | Register the new route in the CLI app so `automodel \u003Ccommand> \u003Cdomain>` resolves correctly. |\n| Shape mismatch at forward pass | Dataset collate function output does not match model input signature | Verify that the collate function returns tensors with the keys and shapes the model expects. |\n| OOM during validation | Validation batch size too large or gradients not disabled | Wrap validation in `torch.no_grad()` and consider a smaller validation batch size. |\n| Checkpoint restore fails | Mismatched model architecture between checkpoint and config | Ensure the model config matches the checkpoint exactly (layer count, hidden dim, vocab size). |\n","# NeMo AutoModel Recipe Development\n\n## Instructions\n\nFor recipe questions, answer with the smallest complete path to action:\n\n1. Name the relevant recipe file or YAML section.\n2. List the builder functions or config keys involved.\n3. Include a minimal YAML or command example when the question asks how to\n   configure something.\n4. End with a local validation command or tiny CPU-compatible test.\n\nFor conceptual recipe questions, answer from this skill without inspecting the\nrepository or loading other AutoModel skills unless the user asks you to edit\nfiles. Keep the response focused on recipe YAML, builders, CLI routing, tests,\nand local validation.\n\nUse these compact answer patterns for common questions:\n\n- New finetuning recipe variant: start from the closest file under\n  `nemo_automodel\u002Frecipes\u002F`, update the model, dataset or dataloader,\n  optimizer, loss, LR scheduler, step scheduler, and checkpoint builders,\n  register a CLI route only if adding a command or domain alias, add example\n  YAML under `examples\u002F`, then add a tiny CPU-compatible unit test and run\n  `automodel finetune llm -c \u003Cconfig.yaml>`.\n- `_target_` fields: describe `_target_` as the fully qualified Python callable,\n  explain that sibling keys become keyword arguments, show optimizer and dataset\n  examples, and mention nested CLI overrides such as `--optimizer.lr`.\n- Validation and checkpointing: name `step_scheduler.val_check_interval`,\n  `step_scheduler.checkpoint_interval`, `validation_dataset`,\n  `restore_from.path`, and consolidated safetensors; include the minimal YAML\n  snippet from this skill.\n\nFor validation and checkpointing, always name:\n\n- `step_scheduler.val_check_interval` for validation cadence.\n- `step_scheduler.checkpoint_interval` for save cadence.\n- `validation_dataset` as the validation dataloader source.\n- `restore_from.path` for resume.\n- Consolidated safetensors as the default checkpoint format for HF ecosystem\n  compatibility.\n\n## Routing Boundary\n\nUse this skill for recipe construction and execution-flow questions: YAML\nstructure, `_target_` callables, builder functions, validation datasets,\ncheckpoint configuration, CLI route registration, and recipe-specific tests.\n\nDo not use this skill for standalone distributed strategy selection, cluster\nlauncher configuration, or model architecture onboarding unless the user is\nasking how those choices appear inside an AutoModel recipe YAML.\n\n## Recipe Architecture\n\n### Execution Flow\n\n```\nCLI (automodel finetune llm -c config.yaml)\n  -> app.py parses command + domain + config\n    -> recipe script (e.g. train_ft.py) main(config_path)\n      -> Recipe class .setup() builds all components\n        -> .run_train_validation_loop() executes training\n```\n\n### Recipe Class\n\nRecipes inherit from `BaseRecipe` and implement two methods:\n\n- `setup()` -- builds model, optimizer, dataloader, loss, LR scheduler, step scheduler, and checkpoint config via builder functions.\n- `run_train_validation_loop()` -- executes the training and validation loop.\n\n### Builder Pattern\n\nAll components are constructed through dedicated builder functions:\n\n- `build_model()` -- instantiates the model from config\n- `build_optimizer()` -- creates optimizer (AdamW, etc.)\n- `build_dataloader()` -- sets up train and validation dataloaders\n- `build_loss_fn()` -- creates the loss function\n- `build_lr_scheduler()` -- creates the learning rate scheduler\n- `build_step_scheduler()` -- creates the step scheduler controlling training progression\n- `build_checkpoint_config()` -- configures checkpointing\n\n### Infrastructure Application Order\n\nComponents are applied in this strict order after building:\n\n1. PEFT (LoRA, etc.)\n2. FP8 quantization\n3. QAT (quantization-aware training)\n4. Checkpoint load \u002F restore\n5. Parameter freezing\n6. Sharding (FSDP2, Megatron-FSDP, DDP)\n7. Device placement\n8. `torch.compile`\n9. Context parallelism hooks\n\n## YAML Config Anatomy\n\nA complete recipe config follows this structure:\n\n```yaml\nstep_scheduler:\n  max_steps: 1000\n  num_epochs: 1\n  grad_accumulation_steps: 4\n  val_check_interval: 100\n  checkpoint_interval: 500\n  log_interval: 10\n\ndist_env:\n  master_addr: localhost\n  master_port: 29500\n\nrng:\n  seed: 42\n\nmodel:\n  _target_: nemo_automodel.models.llm.NemotronHForCausalLM\n  name_or_path: meta-llama\u002FLlama-3.2-1B\n  # additional model kwargs passed to the constructor\n\ncompile:\n  enabled: false\n  backend: inductor\n\nclip_grad_norm:\n  max_norm: 1.0\n\ndistributed:\n  strategy: fsdp2       # fsdp2 | megatron_fsdp | ddp\n  dp_size: auto\n  tp_size: 1\n  cp_size: 1\n\nloss_fn:\n  _target_: torch.nn.CrossEntropyLoss\n\ndataset:\n  _target_: nemo_automodel.datasets.squad.SquadDataset\n  tokenizer_name_or_path: meta-llama\u002FLlama-3.2-1B\n  max_seq_length: 2048\n\nvalidation_dataset:\n  _target_: nemo_automodel.datasets.squad.SquadDataset\n  split: validation\n\npacked_sequence:\n  enabled: false\n\ndataloader:\n  batch_size: 4\n  num_workers: 4\n  pin_memory: true\n\noptimizer:\n  _target_: torch.optim.AdamW\n  lr: 2.0e-5\n  weight_decay: 0.01\n\nlr_scheduler:\n  _target_: nemo_automodel.schedulers.CosineAnnealingWarmup\n  warmup_steps: 50\n  min_lr: 1.0e-6\n```\n\n### The `_target_` Pattern\n\nThe `_target_` key specifies a fully qualified Python callable. All remaining keys in that section are passed as keyword arguments:\n\n```yaml\noptimizer:\n  _target_: torch.optim.AdamW   # callable\n  lr: 2.0e-5                    # kwarg\n  weight_decay: 0.01            # kwarg\n```\n\nThis is equivalent to: `torch.optim.AdamW(lr=2e-5, weight_decay=0.01)`.\n\n### CLI Overrides\n\nAny config value can be overridden from the command line:\n\n```bash\nautomodel finetune llm -c config.yaml \\\n  --optimizer.lr 1e-4 \\\n  --step_scheduler.max_steps 500 \\\n  --distributed.tp_size 2\n```\n\n## Examples\n\nValidation and checkpointing:\n\n```yaml\nstep_scheduler:\n  val_check_interval: 100\n  checkpoint_interval: 500\n\nvalidation_dataset:\n  _target_: nemo_automodel.datasets.squad.SquadDataset\n  split: validation\n\nrestore_from:\n  path: \u002Fcheckpoints\u002Fstep-500\n```\n\n## Domain-Specific Notes\n\n### LLM\n\n- `nemo_automodel\u002Frecipes\u002Fllm\u002Ftrain_ft.py` handles both finetuning and pretraining. The distinction is in the config (dataset, learning rate, etc.).\n- `nemo_automodel\u002Frecipes\u002Fllm\u002Fkd.py` implements knowledge distillation with a teacher and student model.\n- `nemo_automodel\u002Frecipes\u002Fllm\u002Fbenchmark.py` runs throughput and latency benchmarks.\n\n### VLM\n\n- Uses `NeMoAutoModelForImageTextToText` instead of causal LM classes.\n- Config includes a `processor` section instead of a standalone tokenizer.\n- Recipe lives in `nemo_automodel\u002Frecipes\u002Fvlm\u002Ffinetune.py`.\n\n### Diffusion\n\n- Uses `NeMoAutoDiffusionPipeline`.\n- Requires a `parallel_scheme` dict in config to define parallelism.\n- Only supports DDP and FSDP2 strategies (no Megatron-FSDP).\n- Recipe lives in `nemo_automodel\u002Frecipes\u002Fdiffusion\u002Ftrain.py`.\n\n### Retrieval\n\n- Two encoder patterns:\n  - **Bi-encoder** (`nemo_automodel\u002Frecipes\u002Fretrieval\u002Ftrain_bi_encoder.py`): separate query and document encoders, contrastive loss.\n  - **Cross-encoder** (`nemo_automodel\u002Frecipes\u002Fretrieval\u002Ftrain_cross_encoder.py`): joint encoding, classification head.\n- Hard negative mining: `nemo_automodel\u002Frecipes\u002Fretrieval\u002Fmine_hard_negatives.py`.\n\n## Training Loop Details\n\nThe training loop follows this structure per epoch:\n\n```\nfor epoch in range(num_epochs):\n    for batch_idx in range(batches_per_epoch):\n        # --- gradient accumulation inner loop ---\n        for micro_batch in micro_batches:\n            if pipeline_parallel:\n                schedule.step(micro_batch)    # PP schedule\n            else:\n                loss = model(micro_batch)     # direct forward\n                loss.backward()\n\n        # --- optimizer step ---\n        scale_grads_and_clip_grad_norm(model, max_norm)\n        optimizer.step()\n        lr_scheduler.step()\n        optimizer.zero_grad()\n\n        # --- logging ---\n        MetricsSample(step, epoch, loss, grad_norm, lr, mem, tps, mfu)\n\n        # --- validation (at configured intervals) ---\n        if step % val_check_interval == 0:\n            run_validation()\n\n        # --- checkpoint (at configured intervals) ---\n        if step % checkpoint_interval == 0:\n            save_checkpoint()\n```\n\n### StepScheduler\n\nControls all training progression: total epochs, total steps, gradient accumulation steps, validation interval, checkpoint interval, and logging interval.\n\n### Gradient Clipping\n\nApplied via `scale_grads_and_clip_grad_norm()` after the backward pass and before the optimizer step. Controlled by `clip_grad_norm.max_norm` in config.\n\n### Context Parallelism\n\nWhen `cp_size > 1`, batches are split across the context-parallel group using `make_cp_batch_and_ctx()`. This must happen before the forward pass.\n\n### MetricsSample\n\nEach training step produces a `MetricsSample` with fields:\n\n- `step` -- global step count\n- `epoch` -- current epoch\n- `loss` -- training loss\n- `grad_norm` -- gradient norm after clipping\n- `lr` -- current learning rate\n- `mem` -- GPU memory usage\n- `tps` -- tokens per second\n- `mfu` -- model FLOPS utilization\n\n## Validation & Checkpointing\n\n### Validation\n\n- Runs at intervals defined by `step_scheduler.val_check_interval`.\n- Uses the validation dataloader built from `validation_dataset` config.\n- Model is set to eval mode; gradients are disabled.\n\n### Checkpointing\n\n- Default format: consolidated safetensors for easy deployment on HF ecosystem (always prefer this over DCP).\n- Checkpoint interval controlled by `step_scheduler.checkpoint_interval`.\n- Resume training via the `restore_from` config key pointing to a checkpoint directory.\n\n```yaml\nrestore_from:\n  path: \u002Fcheckpoints\u002Fstep-500\n```\n\n## Pitfalls\n\n| Problem | Cause | Fix |\n|---|---|---|\n| Silent config errors | Typo in `_target_` value | The class path must be a valid, importable Python callable. Double-check the module path and class name. |\n| Training crashes at first step | `global_batch_size` not divisible by `local_batch_size * dp_size * grad_accumulation_steps` | Ensure the batch size math is consistent across all dimensions. |\n| New recipe not accessible via CLI | Missing CLI command alias registration | Register the new route in the CLI app so `automodel \u003Ccommand> \u003Cdomain>` resolves correctly. |\n| Shape mismatch at forward pass | Dataset collate function output does not match model input signature | Verify that the collate function returns tensors with the keys and shapes the model expects. |\n| OOM during validation | Validation batch size too large or gradients not disabled | Wrap validation in `torch.no_grad()` and consider a smaller validation batch size. |\n| Checkpoint restore fails | Mismatched model architecture between checkpoint and config | Ensure the model config matches the checkpoint exactly (layer count, hidden dim, vocab size). |\n",{"name":5,"license":15,"metadata":44,"description":7,"when_to_use":48},{"tags":45,"author":32},[46,47],"nemo-automodel","recipe-development","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.","main","7a940b8e5af16c95e5c190a524421d32fc7445a9",".claude\u002Fskills\u002Fnemo-automodel-recipe-development","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui","https:\u002F\u002Fneuroads.com.br","2026-08-12 00:42:44",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add headmktlucca-ui\u002Fneuroads-lp --skill nemo-automodel-recipe-development",{"tool":62,"command":63},"bunx","bunx skills add headmktlucca-ui\u002Fneuroads-lp --skill nemo-automodel-recipe-development",{"tool":65,"command":66},"pnpm","pnpm dlx skills add headmktlucca-ui\u002Fneuroads-lp --skill nemo-automodel-recipe-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fnemo-automodel-recipe-development\u002FSKILL.md",true,[70,76,80,84],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"BENCHMARK.md","REFERENCE","参考文档",4109,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fnemo-automodel-recipe-development\u002FBENCHMARK.md",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"evals\u002Fevals.json",3529,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fnemo-automodel-recipe-development\u002Fevals\u002Fevals.json",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"skill-card.md",3739,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fnemo-automodel-recipe-development\u002Fskill-card.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"skill.oms.sig","OTHER","其他",4613,"https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fnemo-automodel-recipe-development\u002Fskill.oms.sig",[91,118,143,168,186,221],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":106,"publishedAt":39},"01M6PTDCZTXTGSTX4RFK901YSZ","xunit-skill","Generates xUnit.net tests in C#. Covers Fact\u002FTheory, constructor injection, IClassFixture, and FluentAssertions. Use when user mentions \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal\", \"C# xUnit\". Triggers on: \"xUnit\", \"[Fact]\", \"[Theory]\", \"Assert.Equal C#\", \"xUnit.net\".","MIT","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxunit-skill\u002FSKILL.md",[98,103],{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000023","Skill与智能体开发",[107,108,109,110,111,112,113,114,115,116,117],"xunit","xunit skill","testing","injection","user","use","tests","triggers","unit","unit-testing","C#",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":126,"publishedAt":39},"01M6PTCB59ZTG5FTMWGPYEMMBP","xcuitest-skill","Generates XCUITest UI tests for iOS\u002FiPadOS apps in Swift. Apple's native testing framework for reliable, fast UI automation. Supports local simulators and TestMu AI cloud real devices. Use when user mentions \"XCUITest\", \"XCTest\", \"iOS UI test\", \"Swift test\", \"XCUIApplication\". Triggers on: \"XCUITest\", \"XCTest UI\", \"iOS UI test\", \"Swift UI test\", \"XCUIApplication\", \"TestMu\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fxcuitest-skill\u002FSKILL.md",[124,125],{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},[127,128,109,129,130,131,132,133,112,134,135,136,137,138,113,114,139,140,141,142],"xcuitest","xcuitest skill","automation","test","testing framework","ios","devices","mobile","mobile-testing","ui test","local","apple","apps","native","for","objective",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":153,"publishedAt":39},"01M6PTATMNTY9NF4J7KSR76YK6","world-builder","Create and manage generative game zones for Dorothy's Pokemon-style world. Use this skill when creating, updating, or designing game worlds via MCP tools.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworld-builder\u002FSKILL.md",[149,152],{"categoryNo":150,"categoryName":151,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},[154,155,156,157,36,158,159,160,112,161,162,163,164,165,166,141,167],"builder","world","world builder","MCP","mcp tools","Tools","game","pokemon","manage","style","via","theme","zone","generative",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":176,"publishedAt":39},"01M6PT9Z92JTSQEHE1QR0NNW5F","webdriverio-skill","Generates WebdriverIO (WDIO) automation tests in JavaScript or TypeScript. Supports local and TestMu AI cloud. Use when user mentions \"WebdriverIO\", \"WDIO\", \"wdio.conf\", \"browser.url\", \"$\", \"$$\". Triggers on: \"WebdriverIO\", \"WDIO\", \"wdio\", \"browser.$\".","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebdriverio-skill\u002FSKILL.md",[174,175],{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},[177,109,178,129,179,180,181,182,111,112,183,137,113,114,184,185],"webdriverio skill","typescript","javascript","browser","cloud","e2e","e2e-testing","URL","conf",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":201,"publishedAt":39},"01M6PT9NVK36ZWCQ69YXK3FR4K","web-design-guidelines","Web platform design and accessibility guidelines. Use when building web interfaces, auditing accessibility, implementing responsive layouts, or reviewing web UI code. Triggers on tasks involving HTML, CSS, web components, WCAG compliance, responsive design, or web performance.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb\u002FSKILL.md",[192,195,196],{"categoryNo":193,"categoryName":194,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":150,"categoryName":151,"taxonomyType":101,"taxonomyTypeDesc":102},{"categoryNo":197,"categoryName":198,"taxonomyType":199,"taxonomyTypeDesc":200},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,114,220],"design","web","guidelines","web design guidelines","web design","css","performance","components","web components","tasks","code","web performance","ui","platform design","html","responsive design","responsive","platform","implementing",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":229,"publishedAt":39},"01M6PT9A3JKRE3X34276F2FW5R","watchos-design-guidelines","Apple Human Interface Guidelines for Apple Watch. Use when building watchOS apps, complications, or workout features. Triggers on tasks involving Watch UI, Digital Crown, glanceable interfaces, or wrist-based interactions.","https:\u002F\u002Fgithub.com\u002Fheadmktlucca-ui\u002Fneuroads-lp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwatchos\u002FSKILL.md",[227,228],{"categoryNo":150,"categoryName":151,"taxonomyType":101,"taxonomyTypeDesc":102},{"categoryNo":197,"categoryName":198,"taxonomyType":199,"taxonomyTypeDesc":200},[202,204,230,211,214,112,231,232,138,219,233,114,139,234,141,235,236],"watchos design guidelines","workout","human","watch","interface","platform-design","features"]