Developer Asset Hub for NVIDIA Nemotron — A one-stop resource for training recipes, usage cookbooks, datasets, and full end-to-end reference examples to build with Nemotron models
NVIDIA Nemotron is a developer resource for building with the Nemotron family of AI models, providing training recipes, deployment guides, datasets, cookbooks, and end-to-end examples. It is intended for developers and researchers training, customizing, deploying, or applying Nemotron models to agentic AI use cases. Its catalogue add-ons include a Claude Code plugin that guides users through Nemotron customization steps.
Skill Claude CodeCodex
Prepare, validate, build, and use Nemotron Customizer airgap image bundles for offline clusters. Use when planning airgapped deployments, editing deploy/nemotron-customizer/airgap/airgap.yaml, selecting workflow targets, grouping step execution images, baking repo overlays or wheel additions, resuming airgap runner…
Skill Claude CodeCodex
Onboard a new model family (Nemotron or third-party) into skills/ — paper chunks, recipe summaries, context packs, and model card. Use when a contributor wants downstream skills like /nemotron-customize to be able to route to a new model.
Skill Claude CodeCodex needs its repo
Add a cross-cutting decision pattern under src/nemotron/steps/patterns/. Use when a recurring ML decision (tokenizer lock, eval bookends, LoRA-on-small-data, etc.) must be encoded so other skills can fire it during planning.
Skill Claude CodeCodex
Add a new step under src/nemotron/steps/ / / — manifest (step.toml), runner glue, configs, and per-step README.md. Use when extending the catalog so /nemotron-customize can route to it.
Skill Claude CodeCodex
Reference desk for Nemotron 3 Nano / Llama-Nemotron Nano 3 — architecture, training data, recipes, evaluation, quantization, deployment. Use when the user asks facts about the model rather than building a pipeline.
Skill Claude CodeCodex
Generates BYO custom safety policies for NVIDIA Nemotron content-safety guardrails — Nemotron-Content-Safety-Reasoning-4B (text) and multimodal Nemotron-3-Content-Safety. Produces a Markdown policy, JSON taxonomy, and drop-in inference prompts. Maps rough words or an existing policy to V2 categories, adding custom…
Skill Claude CodeCodex
Use when planning, debugging, tuning, evaluating, exporting, or deploying public Nemotron embed/rerank retrieval recipes.
Skill Claude CodeCodex
Reference desk for NVIDIA Nemotron 3 Super — architecture, training data, recipes (pretrain/SFT/RL/eval/quantization), and deployment notes. Use when the user asks facts about Super3 rather than building a pipeline.
Skill Claude CodeCodex
Reference desk for NVIDIA Nemotron 3 Ultra (550B-A55B) — architecture, NVFP4 pretraining, SFT, MOPD (multi-teacher on-policy distillation), MTP boosting, quantization, inference. Use when the user asks facts about Ultra rather than building a pipeline.
Skill Claude CodeCodex
Run the Nemotron-3 Ultra Text2SQL LoRA fine-tuning tutorial (NeMo Megatron-Bridge) end-to-end for the user on their SLURM cluster: data prep, distributed checkpoint conversion, and packed LoRA fine-tuning of the 550B hybrid Mamba-Transformer MoE, ending at a saved adapter. Use when the user wants to run this cookbook…
Skill Claude CodeCodex
Review Nemotron pull requests for critical bugs, tests, and documentation affected by the change.
Skill Claude CodeCodex
Reference desk for NVIDIA Nemotron 3.5 Lightning (30B-A3B), a hybrid Mamba-Transformer MoE with MTP built from Nano 3 Base by distillation from Super 3 Base, single-stage text SFT, RLVR, MTP boosting, and W4A16 NVFP4 quantization. Use when the user asks facts about Lightning 3.5 rather than building a pipeline.
Skill Claude CodeCodex
Reference desk for NVIDIA Nemotron 3.5 Super (120B-A12B), covering vision-language architecture, MTP, distillation pretraining from Ultra 3 Base, Indic CPT, SFT, RLVR, specialist teachers, two-phase MOPD, MTP boosting, NVFP4 quantization, and inference. Use when the user asks facts about Super 3.5 rather than building…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: