Index of every page on this site: llms.txt
All skills
nvidia avatar

/tao-convert-dataset-format

@6b75e9e
by NVIDIA Corporationnvidia/skills4.1k stars
547
Run it yourself

Run `tao-daft convert` to convert NVIDIA TAO DAFT datasets between supported formats. Do not use for non-DAFT data. Use when the user asks to convert a DAFT dataset, change DAFT format, change a TAO dataset format, or run `tao-daft convert`.

Use this Skill: https://skilld.dev/gh/nvidia/skills/tao-convert-dataset-format

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈67 tokens for metadata: the name and description. ≈1.2k when used: this file. ≈3.2k more on demand in 4 files.

Description uses 3.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈270 characters, or 3.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Convert 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

tao-daft convert <source-format> <target-format> --path <input> --output <output>

Source and target are positional subcommands; --path and --output are flags. Discover the supported formats and per-pair flags from the leaf --help (see "CLI conventions" below).

Preflight

python -c "import nvidia_tao_daft" 2>/dev/null || {
  echo "MISSING: tao-daft not installed. Run:"
  echo "  pip install nvidia-tao-daft"
  exit 1
}

Quick Start

Discover the installed CLI surface before choosing format slugs, then run the leaf conversion command with explicit --path and --output flags:

tao-daft --version
tao-daft convert --help
tao-daft convert <source-format> --help
tao-daft convert <source-format> <target-format> --path /path/to/daft --output /path/to/converted

Purpose

Drives tao-daft convert to transform a DAFT dataset (or a tree of them) between supported formats. The CLI does the real work; the skill picks the right source/target pair and flags, then explains the result.

Trigger on: converting a DAFT dataset, packaging DAFT QA / summarization / temporal tasks for VLM training, producing a meta.json-style training set, or the command tao-daft convert. Do not trigger for non-DAFT → DAFT conversion (COCO, YOLO, Data Factory JSONL) — redirect to the upstream nvidia-tao-daft repo's converter skills.

If the user opens ambiguously, run a few --help calls first.

Prerequisites

  • nvidia-tao-daft installed (wheel only, not the source repo). Confirm with tao-daft --version.
  • A DAFT dataset, or a parent directory containing many, on local disk.

Instructions

CLI conventions

tao-daft is nested argparse subcommands. The conventions below are stable across versions even when format names or flags change, so always discover the current surface from --help rather than relying on names this doc happens to mention.

  1. Source and target are both positional subcommands, not --from/--to: tao-daft convert <source> <target> [flags]. Format slugs are versioned, lowercase, dot-separated (metropolis-v3.0, cosmos-reason-v1.0, ...).
  2. Path and output are flags — --path PATH (source), --output OUTPUT (destination). Both required at the leaf; passing positionally fails.
  3. --path accepts both granularities — a single scene/dataset or a parent directory; the converter walks the tree.
  4. Per-pair flags live at the leaf — flag sets differ between targets (e.g. media-handling). Always check the leaf --help.

Operating procedure:

  1. tao-daft --version — confirm install, pin version in any report.
  2. tao-daft convert --help — list supported source formats.
  3. tao-daft convert <source> --help — list valid targets for that source.
  4. Infer source from layout (same directory markers as the tao-validate-dataset-format skill's "Format inference"). If you cannot infer or the target is unspecified, ask.
  5. tao-daft convert <source> <target> --help — pick flags for the user's intent (task subset, media copy vs reference, metadata).
  6. Execute, then interpret (see below).

Reading output

Per-scene progress prints to stdout; non-zero exit on failure. The converted dataset is written under --output — spot-check it with the tao-validate-dataset-format skill before training. For large trees, capture the full output and partial-read if huge.

Limitations

  • DAFT-supported source formats only. For non-DAFT layouts use the upstream repo's converter skills.
  • Supported pairs are whatever --help reports for the installed version — don't pass an unconfirmed pair.
  • Source and target are positional; --path / --output are flags.
  • convert only — validate and info have their own skills.
  • Do not reimplement conversion in Python; the CLI is the spec.

Troubleshooting

  • tao-daft: command not found — wheel not installed; pip install nvidia-tao-daft, verify with tao-daft --version.
  • error: argument --path/--output is required — passed positionally; move behind the flag.
  • invalid choice: '<format>' — slug not wired up in this version. Re-run the relevant --help.
  • Output rejected by tao-daft validate — re-check per-pair flags (media handling, task subset) via leaf --help; a misset flag often produces a structurally valid but semantically wrong target.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill facilitates NVIDIA TAO DAFT dataset conversion using the official nvidia-tao-daft CLI tool. All identified resources and packages are vendor-owned, and no security risks were detected.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at 6b75e9e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
metadata
{
  "author": "NVIDIA Corporation",
  "version": "0.1.0"
}
tags
[
  "tao-daft",
  "dataset",
  "conversion",
  "vlm",
  "cosmos-reason"
]
All 1 allowed tools
Read Bash
Other metadata
compatibility
Requires Python 3.10+ and the nvidia-tao-daft package (pip install nvidia-tao-daft).

README badge

README badge for nvidia/skills/tao-convert-dataset-format