nemotron-customize
Plan, configure, and chain repo-native Nemotron customization steps into single-step or multi-step pipelines: curation, translation, SFT/PEFT (AutoModel or Megatron-Bridge), pretraining/CPT, RL alignment (DPO/RLVR/GRPO/RLHF), BYOB/MCQ benchmarks, checkpoint conversion, ModelOpt optimization, env profiles, and evaluation of trained checkpoints or existing/hosted endpoints. Use when a request names a Nemotron step or workflow, or asks to clean, translate, train, fine-tune, align, convert, optimize
Security Assessment
About nemotron-customize
nemotron-customize is an NVIDIA skill that plans, configures, and chains repo-native Nemotron model-customization steps into single-step or multi-step pipelines. It covers data curation, translation, SFT and PEFT (via AutoModel or Megatron-Bridge), pretraining and continued pretraining, RL alignment (DPO, RLVR, GRPO, RLHF), BYOB and MCQ benchmark generation, checkpoint conversion, ModelOpt optimization, environment profiles, and evaluation of trained checkpoints or existing hosted endpoints. It solves the problem of translating a model-customization request into a validated, artifact-compatible DAG of existing steps, producing only the YAML/config files needed to run them.
The skill routes primarily from bundled reference files — a step catalog, an artifact-compatibility graph, command references, hardware heuristics, and context packs — and treats live repo files under src/nemotron/steps as the verification and fallback source for exact config fields, runner imports, and manifests. It is deliberately conservative: it does not invent new catalog steps, does not generate new Python or shell outside an approved Explorer mode, and does not guess concrete values such as data paths, model IDs, GPU counts, or auth variable names, returning a Blocked handoff or asking the user instead. Prerequisites include a Nemotron repo checkout, the uv tool to invoke steps, and, for remote or hosted work, an environment profile TOML and the expected auth environment variable (for example NVIDIA_API_KEY), which the guidance insists must stay in the environment and never be inlined or committed.
The skill targets ML engineers and researchers building Nemotron customization and training pipelines. Its handling of credentials is exemplary — official env-var-based auth with explicit no-commit, no-inline guidance — and it runs repo-native training/eval CLI commands rather than arbitrary or remote code, with the user supplying all concrete execution values.
FAQ
What can this skill build?
Single-step or multi-step Nemotron pipelines spanning curation, translation, SFT/PEFT, pretraining/CPT, RL alignment, BYOB/MCQ benchmarks, checkpoint conversion, ModelOpt optimization, env profiles, and evaluation of checkpoints or hosted endpoints.
What are the prerequisites?
A checkout of the Nemotron repo with src/nemotron/steps present, the uv tool to run steps, and — for remote or hosted execution — an env profile TOML plus the auth environment variable the step expects.
How are API keys handled?
Auth variables such as NVIDIA_API_KEY are expected to be exported in the environment; the guidance explicitly says never to inline or commit them and never to present default auth variable names as facts.
Will it write new code for me?
No — it produces YAML/config for existing steps only. New Python or shell is out of scope except in an approved Explorer mode after a capability gap is named, and it never invents new catalog steps.
What happens when required values are missing?
It does not guess paths, model IDs, GPU counts, or profiles; it asks for the missing concrete values or returns a Blocked handoff.
All Files
35 filesInstall nemotron-customize
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
nvidia/skills