Generated banner for Tao Train Image Classification
Generated logo for Tao Train Image Classification

Tao Train Image Classification

NVIDIAOfficialCreated by NVIDIA Corporation

  • Skill
  • Tool integration
  • Data and AI
  • Apache-2.0
  • Medium risk

From the author

PyTorch-based TAO image classification. Supports a wide range of backbones (FAN, EfficientNet, ResNet, etc.) with distillation and quantization for deployment. Use when training, evaluating, distilling, quantizing, exporting, or running inference for a TAO image-classification (PyT) model. Trigger phrases include "train image classifier", "TAO classification", "ResNet/EfficientNet/FAN backbone classifier", "classification-pyt".
— the description by NVIDIA Corporation

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a PyTorch-based framework for image classification tasks within the NVIDIA TAO ecosystem. It supports a variety of model backbones, including FAN, EfficientNet, and ResNet. The skill facilitates the full model lifecycle, including training, evaluation, distillation, quantization, and export. It includes AutoML capabilities for training and provides integration paths for TensorRT deployment.

What it does

  • Trains image classification models using various supported backbones.
  • Supports model distillation and quantization for optimized deployment.
  • Exports models to ONNX format for further processing.
  • Integrates with TAO Deploy for TensorRT engine generation and inference.
  • Provides AutoML-enabled training workflows.
  • Handles evaluation of model checkpoints and TensorRT engines.

When to use it

  • When you need to train an image classification model using PyTorch backbones.
  • When you need to optimize a model through distillation or quantization.
  • When you need to prepare a model for deployment via TensorRT.
  • When you need to perform inference or evaluation on classification datasets.

Advantages

  • Supports a wide range of model backbones.
  • Includes built-in support for model distillation and quantization.
  • Automates training workflows with AutoML integration.
  • Provides clear paths for TensorRT deployment and engine generation.

Usage examples

“Train an image classifier using the ResNet backbone.”
The agent initiates the training process using the specified ResNet backbone, applying the required dataset and configuration overrides.
“Quantize my trained classification model.”
The agent runs the quantization action, utilizing the provided calibration dataset to optimize the model for deployment.
“Generate a TensorRT engine for my exported ONNX model.”
The agent triggers the gen_trt_engine action to convert the ONNX model into a TensorRT engine for optimized inference.
“Evaluate my model performance on the test dataset.”
The agent runs the evaluation workflow, calculating metrics based on the provided test images and model checkpoint.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/nvidia/tao-train-image-classification/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip tao-train-image-classification.zip -d .agents/skills

Documentation by NVIDIA Corporation

Classification PyT

Standalone install? If this session was not initialized by the TAO skill bank plugin, run the tao-setup skill first (host preflight, credentials, cross-skill discovery).

PyTorch image classification. Supports a wide range of backbones (FAN, EfficientNet, ResNet, etc.) with distillation and quantization for deployment.

Set model.backbone.pretrained_backbone_path for backbone weights or train.pretrained_model_path for full model.

For TAO Deploy TensorRT actions (gen_trt_engine, TensorRT evaluate, and TensorRT inference), read references/tao-deploy-image-classification.md first. Deploy spec templates live in this skill's references/ folder with the spec_template_deploy_*.yaml prefix.

Dataclass Schemas

Generated TAO Core schemas are packaged in schemas/<action>.schema.json, with schemas/manifest.json listing available actions. Each generated schema also emits references/spec_template_<action>.yaml from the schema top-level default field. AutoML enablement is declared at the model layer in references/skill_info.yaml via automl_enabled. Runnable AutoML for an action requires schemas/<action>.schema.json and references/spec_template_<action>.yaml to exist and parse. Use the packaged selected-action schema for automl_default_parameters, automl_disabled_parameters, defaults, min/max bounds, enums, option weights, math conditions, dependencies, and popular parameters. Do not expect ~/tao-core at runtime; maintainers regenerate schemas/templates before packaging the skill bank.

Train Action Policy

This model is AutoML-enabled at the model layer. Before handling any train-stage request, read references/skill_info.yaml and resolve the run override from either an explicit automl_policy value or the user's workflow request. Use automl_policy: on by default and only expose on / off in new launch prompts. Treat phrases like "turn off AutoML", "disable AutoML", "no HPO", or "plain training" as automl_policy: off for this run only. When automl_policy: on, automl_enabled: true, and both schemas/train.schema.json and references/spec_template_train.yaml are packaged, route the train action through tao-skill-bank:tao-run-automl by default with this model's skill_dir. Preserve workflow/application overrides for datasets, specs, output directories, GPU/platform settings, parent checkpoints, and automl_policy. Use direct model training only when automl_policy: off or the packaged train schema/template is missing; in the missing-schema case, report that AutoML is enabled but not runnable for this model until schemas are generated.

Non-train actions such as evaluate, inference, export, and deploy flows stay in this model skill. The per-run automl_policy override does not change model metadata.

Training Requirements

  • Dataset type: image_classification

  • Formats: classification_pyt

  • Monitoring metric: val_acc_1

  • AutoML train scope: exclude distill.teacher.* parameters from ordinary train searches. Those fields belong to the separate distill action and do not change classification_pyt train behavior even though they appear in the combined generated schema.

Per-Action Dataset Requirements
ActionSpec KeySourceFilesList?
distilldataset.train_dataset.images_dirtrain_datasetsimages_train.tar.gzNo
distilldataset.classes_filetrain_datasetsclasses.txtNo
distilldataset.val_dataset.images_direval_datasetimages_val.tar.gzNo
evaluatedataset.val_dataset.images_direval_datasetimages_val.tar.gzNo
evaluatedataset.classes_fileeval_datasetclasses.txtNo
evaluatedataset.test_dataset.images_dirinference_datasetimages_test.tar.gzNo
exportdataset.root_dirtrain_datasetsNo
inferencedataset.val_dataset.images_direval_datasetimages_val.tar.gzNo
inferencedataset.classes_fileeval_datasetclasses.txtNo
inferencedataset.test_dataset.images_dirinference_datasetimages_test.tar.gzNo
quantizedataset.train_dataset.images_dirtrain_datasetsimages_train.tar.gzNo
quantizedataset.classes_filetrain_datasetsclasses.txtNo
quantizedataset.val_dataset.images_direval_datasetimages_val.tar.gzNo
quantizedataset.quant_calibration_dataset.images_dircalibration_datasetimages_train.tar.gzNo
traindataset.train_dataset.images_dirtrain_datasetsimages_train.tar.gzNo
traindataset.classes_filetrain_datasetsclasses.txtNo
traindataset.val_dataset.images_direval_datasetimages_val.tar.gzNo
Typical Spec Overrides

Data source overrides are mandatory for every action — the agent MUST construct data source paths from the Per-Action Dataset Requirements table above and include them in spec_overrides.

TRAIN_IMAGES_DIR = "/workspace/data/extracted/train/images_train"
VAL_IMAGES_DIR = "/workspace/data/extracted/val/images_val"
TEST_IMAGES_DIR = "/workspace/data/extracted/test/images_test"
CLASSES_FILE = "/workspace/data/s3/classes.txt"
WRITABLE_RESULTS_DIR = "/results"   # must be a writable bind, not the image CWD

For local Docker, download the S3 archives, extract them first, and point dataset.*.images_dir at the extracted class-root folder. Do not pass images_train.tar.gz, images_val.tar.gz, or images_test.tar.gz directly to local Docker specs; the skill metadata declares these inputs as folders.

train (mandatory data sources):

{
    "train.num_epochs": 2,
    "train.validation_interval": 2,
    "train.checkpoint_interval": 2,
    "train.num_gpus": 1,
    "dataset.train_dataset.images_dir": TRAIN_IMAGES_DIR,
    "dataset.classes_file": CLASSES_FILE,
    "dataset.val_dataset.images_dir": VAL_IMAGES_DIR,
    "dataset.root_dir": WRITABLE_RESULTS_DIR,
}

dataset.root_dir is mandatory for train, not just for export. CLDataset writes a classes.txt into root_dir during setup, so it must point at a writable bind mount (the results mount is the natural choice). The spec template defaults it to '', which makes the write land in the container working directory — that succeeds under a root container but fails under any runner that drops to a non-root user:

PermissionError: [Errno 13] Permission denied: 'classes.txt'
  .../classification_pyt/dataloader/dataset.py, in CLDataset.__init__

The local Docker launcher uses the host UID:GID whenever a writable results bind is present, so non-root training hits this unless dataset.root_dir is set.

export (mandatory data sources):

{
    "export.input_height": 224,
    "export.input_width": 224,
    "dataset.root_dir": "/workspace/data/extracted",
}

gen_trt_engine:

{
    "gen_trt_engine.tensorrt.data_type": "fp16",
}

inference (mandatory data sources):

{
    "dataset.batch_size": 1,
    "dataset.val_dataset.images_dir": VAL_IMAGES_DIR,
    "dataset.classes_file": CLASSES_FILE,
    "dataset.test_dataset.images_dir": TEST_IMAGES_DIR,
}

distill (mandatory data sources):

{
    "dataset.train_dataset.images_dir": TRAIN_IMAGES_DIR,
    "dataset.classes_file": CLASSES_FILE,
    "dataset.val_dataset.images_dir": VAL_IMAGES_DIR,
    "train.optim.policy": "step",
}

evaluate (mandatory data sources):

{
    "dataset.val_dataset.images_dir": VAL_IMAGES_DIR,
    "dataset.classes_file": CLASSES_FILE,
    "dataset.test_dataset.images_dir": TEST_IMAGES_DIR,
}

quantize (mandatory data sources):

{
    "dataset.train_dataset.images_dir": TRAIN_IMAGES_DIR,
    "dataset.classes_file": CLASSES_FILE,
    "dataset.val_dataset.images_dir": VAL_IMAGES_DIR,
    "dataset.quant_calibration_dataset.images_dir": TRAIN_IMAGES_DIR,
}

Eval Dataset

Optional. Validation images are provided as a separate tar alongside training images. For small smoke datasets that do not provide a separate images_test.tar.gz, set dataset.test_dataset.images_dir to the validation archive so evaluate and inference still exercise the checkpoint handoff.

Important Parameters

  • dataset.num_classes: Number of classes. Default 20. Must match the number of subdirectories in your image tarballs.

  • model.backbone.type: Default fan_small_12_p4_hybrid. Supported backbones and their head in_channels (from model_params_mapping.py): FAN: fan_tiny, fan_small_12_p4_hybrid, fan_base_16_p4_hybrid, fan_large_16_p4_hybrid. GCViT: gcvit_tiny through gcvit_large. FasterViT: fastervit_0 through fastervit_6. ViT/EVA/DINO: vit_large_patch14_dinov2, eva02_large_patch14, etc. SigLIP-CLIPA: ViT-H-14-SigLIP-CLIPA-224, etc. Some backbones require non-default input resolution (384, 512, 768).

  • dataset.classes_file: Path to classes.txt listing class names.

  • train.optim.lr: Learning rate. Default 6e-5.

  • dataset.img_size: Input image size. Default 224.

  • dataset.batch_size: Per-GPU batch size. Default 8.

Multi-GPU / Multi-Node

Launch method: Lightning-managed (single python process, Lightning spawns workers).

Spec KeyDescriptionDefault
train.num_gpusNumber of GPUs1
train.gpu_idsGPU device indices[0]
train.num_nodesNumber of nodes1
  • Multi-GPU strategy: ddp_find_unused_parameters_true

  • No fsdp support

Multi-node env vars (set by orchestrator): WORLD_SIZE, NODE_RANK, MASTER_ADDR, MASTER_PORT, NUM_GPU_PER_NODE.

Hardware

Minimum 1 GPU(s), recommended 2 GPU(s). 16GB+ (V100 or A100) VRAM per GPU. Classification is generally lightweight. Most backbones at 224x224 fit well on 16GB GPUs with batch_size=8.

Error Patterns

CUDA out of memory: Reduce batch_size or use a smaller backbone.

num_classes mismatch: Ensure dataset.num_classes matches the actual class directories in your image tarballs and classes.txt.

Empty class directory: Every class in classes.txt must have at least one image in the corresponding subdirectory.

Distill scheduler default: The bundled distill template and schema use train.optim.policy: step. Keep that setting for distill specs unless the container implementation is updated; the 7.0 PyT distiller does not assign a scheduler interval for train.optim.policy: linear.

Checkpoint handoff: Training produces model_epoch_*.pth checkpoints and a classifier_model_latest.pth symlink. For evaluate, inference, export, quantize, distill, and resume, select the exact intended epoch checkpoint through the SDK resolver; use the latest symlink only when the user explicitly requests latest.

Spec Param / Parent Model Inference

Model-specific inference mappings belong in this MD file, not in config.json. Generated runners should read this section and apply the mappings with SDK helpers before create_job(). This mirrors the old microservices infer_params.py flow.

Inference mappings from TAO Core classification_pyt.config.json:

ActionSpec FieldInference FunctionMeaning
distilldistill.pretrained_teacher_model_pathparent_modelmodel file inferred from the parent job results folder
distillresults_diroutput_dircurrent job results directory
evaluateevaluate.checkpointparent_modelmodel file inferred from the parent job results folder
evaluateresults_diroutput_dircurrent job results directory
exportexport.checkpointparent_modelmodel file inferred from the parent job results folder
exportexport.onnx_filecreate_onnx_fileoutput ONNX path
exportresults_diroutput_dircurrent job results directory
gen_trt_enginegen_trt_engine.onnx_fileparent_modelmodel file inferred from the parent job results folder
gen_trt_enginegen_trt_engine.trt_enginecreate_engine_fileoutput TensorRT engine path
gen_trt_engineresults_diroutput_dircurrent job results directory
inferenceinference.checkpointparent_modelmodel file inferred from the parent job results folder
inferenceinference.trt_engineparent_modelmodel file inferred from the parent job results folder
inferenceresults_diroutput_dircurrent job results directory
quantizequantize.model_pathparent_modelmodel file inferred from the parent job results folder
quantizeresults_diroutput_dircurrent job results directory
trainmodel.backbone.pretrained_backbone_pathptm_if_no_resume_modelPTM when no resume checkpoint exists
trainresults_diroutput_dircurrent job results directory
traintrain.pretrained_model_pathptm_if_no_resume_modelPTM when no resume checkpoint exists
traintrain.resume_training_checkpoint_pathresume_modelmodel file inferred from the current job results folder

For parent_model or parent_model_folder, pass the upstream train/export/AutoML child job id as parent_job_id. The SDK lists the parent result folder, filters checkpoint artifacts, and returns the selected model file or folder. Do not add these mappings back to config.json and do not patch generated runner scripts to guess checkpoint paths.

Deployment

Files

references/tao-deploy-image-classification.md

Classification PyT Deploy

Classification PyT deploy covers the TAO Deploy actions for an exported image classification model. Use the classification-pyt model skill for training, checkpoint evaluation, quantization, distillation, pruning, export, or non-TensorRT inference where those actions exist. Use this deploy workflow after export when the input artifact is an ONNX model and the desired output is a TensorRT engine or TensorRT-backed predictions.

Supported actions: gen_trt_engine, evaluate, inference.

Quick Start

Set the deploy container once at the top of the session — every command below uses it:

TAO_DEPLOY_IMAGE=nvcr.io/nvidia/tao/tao-toolkit:7.3.0-deploy  # versions-key: images.tao_toolkit.deploy
Generate TensorRT Engine
docker run --gpus all --rm --shm-size=16g \
  -v /path/to/specs:/specs \
  -v /path/to/export:/models \
  -v /path/to/results:/results \
  "$TAO_DEPLOY_IMAGE" \
  classification_pyt gen_trt_engine -e /specs/classification-pyt_deploy_gen_trt_engine.yaml
Evaluate TensorRT Engine
docker run --gpus all --rm --shm-size=16g \
  -v /path/to/specs:/specs \
  -v /path/to/eval:/data \
  -v /path/to/results:/results \
  "$TAO_DEPLOY_IMAGE" \
  classification_pyt evaluate -e /specs/classification-pyt_deploy_evaluate.yaml
TensorRT Inference
docker run --gpus all --rm --shm-size=16g \
  -v /path/to/specs:/specs \
  -v /path/to/inference:/data \
  -v /path/to/results:/results \
  "$TAO_DEPLOY_IMAGE" \
  classification_pyt inference -e /specs/classification-pyt_deploy_inference.yaml

Deploy action metadata is in tao-deploy-image-classification.skill_info.yaml. Deploy spec templates live in this references folder:

  • spec_template_deploy_gen_trt_engine.yaml

  • spec_template_deploy_evaluate.yaml

  • spec_template_deploy_inference.yaml

Deploy Workflow

  1. Train and export with the classification-pyt skill.

  2. Keep the exported ONNX artifact and any sidecar files together in the mounted model directory.

  3. Build the TensorRT engine with this workflow.

  4. Run TensorRT evaluate or inference from the engine artifact produced by gen_trt_engine.

Direct TAO Launcher spelling is tao deploy classification_pyt gen_trt_engine, tao deploy classification_pyt evaluate, tao deploy classification_pyt inference.

Required Inputs

ActionRequired artifact or dataSpec key
gen_trt_engineExported ONNX modelgen_trt_engine.onnx_file
gen_trt_engineOutput engine pathgen_trt_engine.trt_engine
evaluateTensorRT engineevaluate.trt_engine
evaluateImage classification test folderdataset.test_dataset.images_dir
inferenceTensorRT engineinference.trt_engine
inferenceImage classification test folderdataset.test_dataset.images_dir

For direct Docker runs, mount input folders at the same paths used in the spec. If the source data is packaged as images_test.tar.gz, extract it first and point dataset.test_dataset.images_dir at the extracted class-root folder. For chained jobs, map exported ONNX artifacts into gen_trt_engine.onnx_file and map the engine artifact into evaluate.trt_engine or inference.trt_engine where those actions are available. gen_trt_engine.trt_engine is the generated output path, not an upstream input artifact.

Spec Overrides

Carry structural model and dataset settings forward from the train/export spec. The deploy defaults are templates, not a substitute for the model-specific values used to produce the ONNX file.

Recommended starting overrides:

{
    'dataset.batch_size': 1,
    'gen_trt_engine.tensorrt.data_type': 'fp16',
    'inference.batch_size': 1,
    'evaluate.batch_size': 1,
    'gen_trt_engine.tensorrt.min_batch_size': 1,
    'gen_trt_engine.tensorrt.opt_batch_size': 1,
    'gen_trt_engine.tensorrt.max_batch_size': 8,
}

Model-specific notes:

  • Use fp16 for the starter-kit TensorRT engine path unless INT8 calibration is explicitly requested.

  • For TensorRT inference and evaluation, set both dataset.batch_size and the action batch size to 1 unless the engine profile was built for the larger batch. The default Classification PyT ONNX export uses a static batch-1 input, so TensorRT evaluation can still try batch 8 and fail with a static dimension mismatch if only evaluate.batch_size is overridden.

Job Chain Mapping

ActionSpec fieldParent or output
gen_trt_enginegen_trt_engine.onnx_fileexport job ONNX
gen_trt_enginegen_trt_engine.trt_enginenew engine output path
gen_trt_engine INT8calibration image/cache fieldscalibration dataset and new cache output
evaluateevaluate.trt_engineengine job output
inferenceinference.trt_engineengine job output

Outputs

ActionOutput
gen_trt_engineTensorRT engine at gen_trt_engine.trt_engine
evaluateTop-K classification metrics under results_dir
inferenceClassification predictions under results_dir

Known Pitfalls

Engine profile mismatch: Runtime batch size for evaluate or inference must fit within the TensorRT min/opt/max profile used during gen_trt_engine. If the ONNX input is static batch 1, keep dataset.batch_size, evaluate.batch_size, and inference.batch_size at 1.

Template class or shape mismatch: Copy class count, input resolution, backbone, and post-processing settings from train/export before running TAO Deploy.

INT8 calibration missing: INT8 builds need an extracted calibration image directory, a writable cache path, and enough images for cal_batch_size * cal_batches.

Mounted paths do not exist: TAO Deploy checks local paths inside the container. Make sure every path in the spec has a matching Docker mount or job artifact mapping.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Declares allowed tools, Needs Python, Needs Node.js

The author says: Requires docker + nvidia-container-toolkit.

Security

What our scanner noticed· Medium risk

  • Large base64-encoded blobs

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
NVIDIA Corporation
Publisher
NVIDIA (Official)
Source
NVIDIA/skills · skills/tao-train-image-classification · commit fce3cca
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE-APACHE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by NVIDIA Corporation or NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download tao-train-image-classification.zip