tao-convert-dataset-format
Run `tao-daft convert` to convert NVIDIA TAO DAFT datasets between supported formats. Do not use for non-DAFT data.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 5
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 e55078243dcadb8b… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Convert a TAO DAFT Dataset
Standalone install? If this session was not initialized by the TAO skill bank plugin, run the
tao-setupskill 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-daftinstalled (wheel only, not the source repo). Confirm withtao-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.
- 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, ...). - Path and output are flags —
--path PATH(source),--output OUTPUT(destination). Both required at the leaf; passing positionally fails. --pathaccepts both granularities — a single scene/dataset or a parent directory; the converter walks the tree.- Per-pair flags live at the leaf — flag sets differ between
targets (e.g. media-handling). Always check the leaf
--help.
Operating procedure:
tao-daft --version— confirm install, pin version in any report.tao-daft convert --help— list supported source formats.tao-daft convert <source> --help— list valid targets for that source.- Infer source from layout (same directory markers as the
tao-validate-dataset-formatskill's "Format inference"). If you cannot infer or the target is unspecified, ask. tao-daft convert <source> <target> --help— pick flags for the user's intent (task subset, media copy vs reference, metadata).- 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
--helpreports for the installed version — don't pass an unconfirmed pair. - Source and target are positional;
--path/--outputare flags. convertonly —validateandinfohave 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 withtao-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.
Files
5- BENCHMARK.md
e8469489957.2 KB - SKILL.md
26fef280f55.1 KB - config/skillspector-baseline.yaml
8b379b90c3834 B - evals/evals.json
688dcf14c2853 B - skill-card.md
fa93e7a43f3.6 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from NVIDIA/skills8
Official NVIDIA-authored guidance for NVIDIA cuDF GPU DataFrames, pandas acceleration, dask-cuDF, ETL, joins, groupby, CSV/Parquet I/O, nullable semantics, and multi-GPU DataFrame workloads.
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
Customize NVIDIA Nemotron Voice Agent's Generic Pipecat example for healthcare appointment, five-field patient intake, or custom tool-calling workflows without a separate backend.
Calibrate a new dataset from live RTSP camera streams via the AutoMagicCalib REST API. Use when the user provides RTSP URLs or asks to calibrate live cameras; VIOS records clips, AMC ingests them, then runs calibration.
Run end-to-end calibration on the shipped sample dataset (sdg_08_2_sample_data_010926.zip) against a running AMC microservice. Use when user says 'test sample dataset', 'run sample calibration', 'verify AMC install', or 'launch and test'.
Calibrates pre-recorded `cam_*.mp4` datasets through the AutoMagicCalib REST API. Use for user-supplied local MP4s; route live RTSP streams to `amc-run-rtsp-calibration`.
Launch AutoMagicCalib microservice and web UI from NGC release images via Docker Compose. Use when user says 'deploy auto calibration', 'launch auto calibration', 'launch AMC', 'start MS+UI', or 'set up auto-magic-calib'. Requires NGC API key.
Related ai-ml skillsscan passed
Prevent AI style drift on legacy projects by scanning the codebase for implicit conventions, resolving conflicts with the operator one at a time, and writing an enforceable .ai-style-rules.md (Golden Files, naming rules, DONTs) plus an optional CLAUDE.md hook. Use when onboarding an AI agent onto a
Pair a remote AI agent with your browser. (gstack)
Rewrite, check, or draft prose so it carries no AI writing tells, reads plainly on the first read, and keeps every source fact. Use when asked to make writing plainer or free of those tells, to check writing for them, or when drafting from supplied content. Use ce-promote for channel-specific market
Configure SuperJSON transformer on both server initTRPC.create({ transformer: superjson }) and every client terminating link (httpBatchLink, httpLink, wsLink, httpSubscriptionLink) to support Date, Map, Set, BigInt over the wire. Transformer must match on both sides. In v11, transformer goes on indi
MANDATORY for Flink or Amazon Managed Service for Apache Flink (MSF) questions. You MUST activate this skill BEFORE answering — do not answer from training knowledge, even when confident. MSF has service-specific constraints (KPU model, prohibited checkpoint and parallelism config in app code, the v
Validates the user's environment for SageMaker AI operations — checks SDK version, AWS region, and execution role. Use when the user says "set up", "getting started", "check my environment", "configure SDK", or as the first step in any plan involving SageMaker/Bedrock training, evaluation, or deploy