Agent skill

Nemotron Customizer Airgap

by NVIDIA-NeMo in NVIDIA-NeMo/Nemotron

Prepare, validate, build, and use Nemotron Customizer airgap image bundles for offline clusters.

Apache-2.0Auto-check passedAI & LLM Engineering

Install Nemotron Customizer Airgap

skills CLI
$ npx skills add NVIDIA-NeMo/Nemotron --skill nemotron-customizer-airgap -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA-NeMo/Nemotron nemotron-customizer-airgap --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA-NeMo/Nemotron.git skills-src && mkdir -p .claude/skills && cp -r skills-src/deploy/nemotron-customizer/airgap .claude/skills/nemotron-customizer-airgap && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nemotron-customizer-airgap
GitHub stars
2.1k
Token cost
~1.2k tokens
SKILL.md length
445 words
Files
11
Skills in repo
10
Repo updated
First seen
Licence
Apache-2.0

At a glance

Prepare, validate, build, and use Nemotron Customizer airgap image bundles for offline clusters.

  • Works in 3 steps: Establish the side of the workflow → Gather the minimum inputs → Plan with the runner first
  • Planning airgapped deployments
  • SKILL.md covers Read First, Workflow, Guardrails and Validation
  • Runs Python scripts from its folder; calls uv

What it does

Nemotron Customizer Airgap is an agent skill from NVIDIA-NeMo/Nemotron. 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 builds, or submitting nemotron steps run jobs inside an airgapped environment.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files (for example `README.md`, `airgap.yaml` and `configs/sft_megatron_bridge_default.yaml`).

It sits in AI & LLM Engineering, covering Deployment. It works with NVIDIA AI Platform and Docker. The repository describes itself as: 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. The licence is Apache-2.0.

When your agent uses it

  • Planning airgapped deployments
  • Editing deploy/nemotron-customizer/airgap/airgap.yaml
  • Selecting workflow targets
  • Grouping step execution images

Example prompts

  • “/nemotron-customizer-airgap”

Requirements

  • Python 3
  • Docker

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Establish the side of the workflow
  2. Gather the minimum inputs
  3. Plan with the runner first

What it can do on your machine

Read from SKILL.md and the folder at commit ca8c409. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nemotron Customizer Airgap loads about 1.2k tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 445 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~106
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA-NeMo/Nemotron at commit ca8c409, republished under its Apache-2.0 licence (© NVIDIA-NeMo). 445 words, ~1,189 tokens.

Download SKILL.mdSave it as .claude/skills/nemotron-customizer-airgap/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
nemotron-customizer-airgap
description
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 builds, or submitting `nemotron steps run` jobs inside an airgapped environment.

Nemotron Customizer Airgap

Use this skill to help an agent produce a connected-machine airgap bundle and then submit Nemotron Customizer steps from the airgapped side. Keep it grounded in the checked-in runner and manifests; do not invent a parallel packaging flow.

Read First

  • deploy/nemotron-customizer/airgap/README.md for the operator flow.
  • deploy/nemotron-customizer/airgap/airgap.yaml for the current image map.
  • deploy/nemotron-customizer/airgap/runner.py when changing behavior.
  • tests/deploy/test_airgap_runner.py before editing runner logic.
  • deploy/nemotron-customizer/airgap/configs/ for runtime overlay configs.

For selected steps, inspect the catalog through the CLI:

bash
uv run nemotron steps show <step_id> --json

Workflow

  1. Establish the side of the workflow:

    • Connected machine: validate, build, save image tarballs.
    • Airgapped side: load images, set env profiles, run selected steps.
  2. Gather the minimum inputs:

    • Target steps and config names, for example sft/megatron_bridge:tiny.
    • Target architecture or Docker platform, for example linux/amd64.
    • Available base images and whether the connected machine can pull them.
    • Airgapped env profile name, mounts, model/data/checkpoint locations.
    • Whether destructive or expensive actions such as --execute, Docker build, Docker volume cleanup, or state-file removal are explicitly allowed.
  3. Plan with the runner first:

bash
uv run python deploy/nemotron-customizer/airgap/runner.py \
  --config deploy/nemotron-customizer/airgap/airgap.yaml

Use --target <step_id>:<config> for one-off selections without editing YAML. The runner expands dependencies from dependencies, validates selected step files/configs, groups execution images, and prints selected execution images.

  1. Edit airgap.yaml only where the runner expects configuration:

    • workflow.stages or CLI --target for selected customer steps.
    • dependencies for explicit upstream Nemotron Customizer step outputs.
    • step_execution_images for step-to-image mapping.
    • execution_images for base image, tag, tar, platform, and import probes.
    • launcher_image for the launcher container.
  2. Execute only when the user asks for a real build:

bash
uv run python deploy/nemotron-customizer/airgap/runner.py \
  --config deploy/nemotron-customizer/airgap/airgap.yaml \
  --execute

If a build fails midway, keep airgap-build-state.yaml and rerun the same command. Remove or move that state only when intentionally changing the plan.

  1. On the airgapped side, use images from out/airgap-manifest.yaml under step_execution_images. Submit with the plural CLI:
bash
uv run nemotron steps run <step_id> \
  -c <config-or-airgap-overlay> \
  -b <airgap-profile> \
  run.env.container_image=<image-from-manifest>

For sft/megatron_bridge, prefer the airgap overlay configs under deploy/nemotron-customizer/airgap/configs/; they clear runtime git auto-mounts because the runner bakes those repos into the execution image.

Show full SKILL.md (134 more words)Show less

Guardrails

  • Keep models, datasets, checkpoints, secrets, and customer files out of images. Put them on persistent storage and reference them through config overrides and run.env.mounts.
  • Treat ${auto_mount:git+...} as a connected-machine build input. The runner bakes pinned repo overlays into execution images so airgapped jobs do not clone from GitHub.
  • Do not add missing packages blindly. Let discover-execution-deps and import probes determine small additions; keep heavyweight framework deps in the base image choice.
  • Preserve offline defaults unless the user has an internal mirror: HF_HUB_OFFLINE=1, TRANSFORMERS_OFFLINE=1, HF_DATASETS_OFFLINE=1, and WANDB_MODE=offline.
  • Use nemotron steps ...; do not reintroduce nemotron step ....

Validation

After edits to runner logic, YAML structure, or airgap docs, run:

bash
uv run pytest tests/deploy/test_airgap_runner.py -q

For CLI-facing examples, also smoke the command shape:

bash
uv run nemotron steps --help
uv run nemotron steps show data_prep/sft_packing --json

Do not run Docker build/save stages during validation unless the user explicitly asked for a real connected-machine bundle build.

© NVIDIA-NeMo, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files in deploy/nemotron-customizer/airgap of NVIDIA-NeMo/Nemotron.

  • SKILL.md
  • .gitignore
  • Dockerfile.execution
  • Dockerfile.execution.dockerignore
  • Dockerfile.launcher
  • Dockerfile.launcher.dockerignore
  • README.md
  • airgap.yaml
  • configs/sft_megatron_bridge_default.yaml
  • configs/sft_megatron_bridge_tiny.yaml
  • runner.py

Open the folder on GitHubat commit ca8c409

Compare with similar skills

Nemotron Customizer Airgap next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nemotron Customizer Airgap compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nemotron Customizer Airgap this skillNVIDIA-NeMo/Nemotron2.1k—~1.2kAutomated safety check: PassApache-2.0
Setup Workshopbrevdev/workshop-build-an-agent146—~2.3kAutomated safety check: NotesApache-2.0
Deep Researcher DeployNVIDIA-AI-Blueprints/deep-researcher-agent886—~3.5kAutomated safety check: NotesApache-2.0
Msa Search NimNVIDIA/skills3.6k1 repos~4.6kAutomated safety check: NotesApache-2.0
Generate Openenv Envadithya-s-k/FineEnvs461—~2.4kAutomated safety check: PassApache-2.0
vLLM Model ServingOrchestra-Research/AI-Research-SKILLs13k5 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • Setup Workshop

    brevdev/workshop-build-an-agent

    This skill should be used when the user wants to set up, install, deploy, bootstrap, or "spin up" the Build-an-Agent workshop (a.k.a.

    146 GitHub stars~2.3k tokensUpdated 3 days ago
    DevOps & CloudAuto-check: notes
  • Deep Researcher Deploy

    NVIDIA-AI-Blueprints/deep-researcher-agent

    A skill your agent uses when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA Deep Researcher Agent Blueprint infrastructure.

    886 GitHub stars~3.5k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Msa Search Nim

    NVIDIA/skills

    Official

    Generate multiple sequence alignments (MSAs) for protein sequences using the ColabFold MSA-Search NIM.

    3.6k GitHub starsUsed in 1 repo~4.6k tokens
    DevOps & CloudAuto-check: notes
  • Generate Openenv Env

    adithya-s-k/FineEnvs

    Builds an OpenEnv (Hugging Face) variant of an RL environment.

    461 GitHub stars~2.4k tokensUpdated 2 days ago
    AI & LLM EngineeringAuto-check passed
  • vLLM Model Serving

    Orchestra-Research/AI-Research-SKILLs

    Deploys LLMs with vLLM for high-throughput serving, covering the OpenAI-compatible server, offline batch inference, monitoring and a Docker rollout.

    13k GitHub starsUsed in 5 repos~2.3k tokens
    AI & LLM EngineeringAuto-check passed
  • Cv Deploy

    LMIXR/CV_Deployment_skill

    基于 helpfile 工程经验,协助 agent 配置 CV 主机和边缘设备环境、编译视觉与推理依赖、接入摄像头视频并打包部署服务。适用于 Ubuntu、CentOS、Windows、macOS、Jetson、树莓派和 RK3399 的 CV 工程实施与故障排查,以及相关移动端配套工具;模型训练和纯算法设计不属于本技能主线。

    188 GitHub stars~547 tokensUpdated 12 days ago
    AI & LLM EngineeringAuto-check passed

More from NVIDIA-NeMo/Nemotron

All 10 skills in this repo
  • Nemotron Add Model

    NVIDIA-NeMo/Nemotron

    Onboard a new model family (Nemotron or third-party) into skills/ — paper chunks, recipe summaries, context packs, and model card.

    2.1k GitHub stars~2.2k tokensUpdated 4 days ago
    Auto-check passed
  • Nemotron Add Pattern

    NVIDIA-NeMo/Nemotron

    Add a cross-cutting decision pattern under src/nemotron/steps/patterns/.

    2.1k GitHub stars~1.4k tokensUpdated 4 days ago
    Auto-check passed
  • Nemotron Add Step

    NVIDIA-NeMo/Nemotron

    Add a new step under src/nemotron/steps/<category/<stepid/ — manifest (step.toml), runner glue, configs, and per-step README.md.

    2.1k GitHub stars~1.7k tokensUpdated 4 days ago
    Auto-check passed
  • Nemotron Nano3

    NVIDIA-NeMo/Nemotron

    Reference desk for Nemotron 3 Nano / Llama-Nemotron Nano 3 — architecture, training data, recipes, evaluation, quantization, deployment.

    2.1k GitHub stars~1.9k tokensUpdated 4 days ago
    Auto-check passed
  • Nemotron Super3

    NVIDIA-NeMo/Nemotron

    Reference desk for NVIDIA Nemotron 3 Super — architecture, training data, recipes (pretrain/SFT/RL/eval/quantization), and deployment notes.

    2.1k GitHub stars~2.4k tokensUpdated 4 days ago
    Auto-check passed
  • Run the Nemotron-3.5 Lightning Text2SQL LoRA fine-tuning tutorial (NeMo Megatron-Bridge) end-to-end for the user on a single node: data prep, checkpoint conversion, LoRA fine-tuning of the 30B-A3B…

    2.1k GitHub stars~1.9k tokensUpdated 4 days ago
    Auto-check passed

Questions about Nemotron Customizer Airgap

What does Nemotron Customizer Airgap do?

Prepare, validate, build, and use Nemotron Customizer airgap image bundles for offline clusters. Nemotron Customizer Airgap is an agent skill from NVIDIA-NeMo/Nemotron. Prepare, validate, build, and use Nemotron Customizer airgap image bundles for offline clusters.

When should I use Nemotron Customizer Airgap?

Nemotron Customizer Airgap fits situations like: planning airgapped deployments; editing deploy/nemotron-customizer/airgap/airgap.yaml; selecting workflow targets; grouping step execution images.

How do I install Nemotron Customizer Airgap in Claude Code?

Run `npx skills add NVIDIA-NeMo/Nemotron --skill nemotron-customizer-airgap -a claude-code`. Or copy the skill folder (deploy/nemotron-customizer/airgap in NVIDIA-NeMo/Nemotron) into .claude/skills/nemotron-customizer-airgap in your project. Claude Code loads it when a task matches its description.

How do I install Nemotron Customizer Airgap in Codex?

Run `npx skills add NVIDIA-NeMo/Nemotron --skill nemotron-customizer-airgap -a codex`. Or copy the skill folder (deploy/nemotron-customizer/airgap in NVIDIA-NeMo/Nemotron) into .agents/skills/nemotron-customizer-airgap in your project. Codex loads it when a task matches its description.

Can I use Nemotron Customizer Airgap in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA-NeMo/Nemotron --skill nemotron-customizer-airgap -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nemotron-customizer-airgap, .gemini/skills/nemotron-customizer-airgap, .github/skills/nemotron-customizer-airgap and .opencode/skills/nemotron-customizer-airgap in your project.

What does Nemotron Customizer Airgap need to run?

Going by SKILL.md and its folder, Nemotron Customizer Airgap needs Python for the scripts in its folder and the command-line tools its instructions call (uv). Our summary lists: Python 3; Docker.

Does Nemotron Customizer Airgap access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Nemotron Customizer Airgap safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Nemotron Customizer Airgap use?

Nemotron Customizer Airgap is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nemotron Customizer Airgap use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nemotron Customizer Airgap?

Skills that share tags, products or a category with Nemotron Customizer Airgap: Setup Workshop (brevdev/workshop-build-an-agent, 146 stars), Deep Researcher Deploy (NVIDIA-AI-Blueprints/deep-researcher-agent, 886 stars), Msa Search Nim (NVIDIA/skills, 3.6k stars) and Generate Openenv Env (adithya-s-k/FineEnvs, 461 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nemotron Customizer Airgap?

NVIDIA-NeMo (a GitHub organization) maintains it in NVIDIA-NeMo/Nemotron, which has 2,142 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 6, 2026.

Source: NVIDIA-NeMo/Nemotron on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.