Agent skill · data analytics · nvidia
tao-validate-dataset-format
Run `tao-daft validate` to check NVIDIA TAO DAFT datasets for structure, schema, and cross-reference errors. Do
Why this skill is useful
Provides specific commands and validation procedures for NVIDIA TAO DAFT datasets that the AI wouldn't reliably generate on its own.
What it needs
Requires nvidia-tao-daft, python installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
Validate a TAO DAFT Dataset 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). Quick start <format> is a positional subcommand (e.g. metropolis-v3.0, cosmos-reason-v1.0); --path is required. Discover supported formats and per-format flags via tao-daft validate --help and the leaf --help (see "CLI conventions" below). Preflight Quick Start Discover the installed validator formats before choosing a format slug, then run validation with the target passed through --path: Purpose Drive tao-daft validate against a DAFT dataset (or a tree of them). The CLI is the spec; the skill picks subcommand + flags and explains the result. Trigger when the user mentions "TAO DAFT", "DAFT format", validating a DAFT dataset, schema/cross-reference errors, or tao-daft validate. Do not trigger for non-DAFT layouts (COCO, YOLO, Data Factory JSONL), or for tao-daft info / tao-daft convert — those have their own skills. If the user's opening is ambiguous, run a few --help commands first to ground yourself, then come back and confirm the task. Prerequisites nvidia-tao-daft installed (pip install nvidia-tao-daft; the wheel is enough, no source repo). Confirm with tao-daft --version. A DAFT dataset, or a parent directory of them, on local disk. Instructions CLI conventions tao-daft is nested argparse subcommands. Names and flags drift across versions, so discover the current surface from --help rather than trusting any list in this doc. 1. Format is a positional subcommand, not --format: tao-daft validate <format> [flags]. List current formats via tao-daft validate --help; slugs look like metropolis-v3.0, cosmos-reason-v1.0. 2. Target is --path PATH, not positional. It accepts a single dataset/scene or a parent directory — the validator walks the tree. 3. Flags are per-format; run the leaf help, e.g. tao-daft validate metropolis-v3.0 --help, before choosing them. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/tao-validate-dataset-format