nemotron-add-step

Name: nemotron-add-step
Availability: InStock
Author: NVIDIA-NeMo

Add a Nemotron step to the catalog with manifests and wiring.

1.8k|373|Updated Oct 3, 2025

Search Tags:#validation #configuration #manifest #nemotron #dev tooling #step catalog #pipeline wiring

Ready to run

npx skills add https://github.com/NVIDIA-NeMo/Nemotron --skill nemotron-add-step

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nemotron-add-step
Source: https://github.com/NVIDIA-NeMo/Nemotron/tree/main/skills/nemotron-add-step
Command: npx skills add https://github.com/NVIDIA-NeMo/Nemotron --skill nemotron-add-step

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps contributors add a new entry to the Nemotron step catalog without breaking the manifest schema, wiring, or validation flow used by nemotron-customize.

Core Features & Use Cases

Guided step design: Collects the missing facts needed to correctly define a new step (category, stack library, consumed/produced artifact types, and references).
Repo-convention generation: Creates the standard step directory with step.toml plus starter configs, optionally adds step.py only when needed, and updates category guides when appropriate.
Schema-safe validation: Ensures types.toml, references, and generated manifests conform to the existing workflow by running repo validation commands after generation.

Quick Start

Ask the skill to add your new catalog step by invoking: /nemotron-add-step.

Frequently Asked Questions about nemotron-add-step

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add a new step to the Nemotron step catalog without breaking manifests?▼

To add a new Nemotron step safely, generate the standard directory with step.toml, starter configs, and correct wiring for nemotron-customize routing. It reads live conventions like types.toml and validates against the step test suite before finalizing.

What is the correct way to configure nemotron-customize routing for a custom pipeline step?▼

Configuring nemotron-customize routing requires defining consumed and produced artifact types in the step manifest. The step must conform to existing library patterns across categories like curate, sdg, translate, pretrain, or eval to pass validation.

Do I need to manually update types.toml when extending the Nemotron step catalog?▼

You do not need to manually update types.toml blindly. The generation process reads live step conventions from types.toml and example manifests to ensure your new step extension aligns with existing schema requirements and validation flows.

Can I create a new Nemotron step for the peft or rl category using existing library patterns?▼

Yes, you can create steps for peft, rl, optimize, benchmark, and other catalog categories. The process applies existing library patterns to generate repository-relative references and validate the manifests for any supported category.

Why does my new pipeline step fail nemotron-customize validation after generation?▼

Pipeline step validation fails when manifests, configurations, or types.toml entries do not conform to the workflow schema. Running repo validation commands after generation ensures references and artifact types align with the index and step test suite.