Tao Validate Dataset Format
NVIDIAOfficialCreated by NVIDIA Corporation
- Skill
- Review and audit
- Software development
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides an interface to the tao-daft validate command, enabling users to verify the integrity of NVIDIA TAO DAFT datasets. It guides the user through discovering supported dataset formats, identifying the correct validation subcommands, and executing checks against local dataset paths. The skill ensures that validation is performed according to the specific requirements of the installed version of the nvidia-tao-daft package.
What it does
- Checks dataset structure, schema, and cross-references for DAFT-formatted data.
- Discovers available validation formats via the tao-daft CLI.
- Supports validation of individual datasets or entire directory trees.
- Provides guidance on identifying dataset formats based on directory markers.
- Interprets validation results and failure codes from the CLI output.
When to use it
- When you need to verify that a dataset conforms to the DAFT format requirements.
- When you encounter schema or cross-reference errors in a TAO DAFT dataset.
- When you need to confirm the validity of a dataset before running further TAO operations.
- When you are unsure which validation flags are required for a specific DAFT format.
Advantages
- Uses the official CLI as the source of truth for validation specifications.
- Helps prevent errors by guiding the user through format-specific flag discovery.
- Automates the process of checking complex dataset trees.
- Provides clear feedback on validation success or failure.
Usage examples
- “Validate my DAFT dataset located at /data/my_dataset.”
- The agent will identify the dataset format, run the appropriate tao-daft validate command with the --path flag, and report the validation results.
- “How do I check the schema for a metropolis-v3.0 dataset?”
- The agent will list the available flags for the metropolis-v3.0 format and execute the validation command on the specified path.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/nvidia/tao-validate-dataset-format/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip tao-validate-dataset-format.zip -d .agents/skills
Documentation by NVIDIA Corporation
Validate 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 validate <format> --path <dataset-or-parent-dir><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
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 validator formats before choosing a format slug, then
run validation with the target passed through --path:
tao-daft --version
tao-daft validate --help
tao-daft validate <format> --help
tao-daft validate <format> --path /path/to/daft-datasetPurpose
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-daftinstalled (pip install nvidia-tao-daft; the wheel is enough, no source repo). Confirm withtao-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.
Format is a positional subcommand, not
--format:tao-daft validate <format> [flags]. List current formats viatao-daft validate --help; slugs look likemetropolis-v3.0,cosmos-reason-v1.0.Target is
--path PATH, not positional. It accepts a single dataset/scene or a parent directory — the validator walks the tree.Flags are per-format; run the leaf help, e.g.
tao-daft validate metropolis-v3.0 --help, before choosing them. Don't assume a flag from one format exists on another.
So the loop is: tao-daft --version → tao-daft validate --help →
pick format (infer if unspecified, see below) →
tao-daft validate <format> --help → run → interpret.
Format inference
Use directory markers, not filenames:
meta.jsonnext tomedia/andtext/⇒cosmos-reason-v1.0.A directory (or nested directories) containing
contextual/, typically alongsideraw/andtask/⇒metropolis-v3.0.Neither marker present ⇒ ask the user; do not guess.
Reading errors
The CLI ends every run with a VALIDATION RESULTS block, then
✅ VALIDATION PASSED or ❌ VALIDATION FAILED, and exits non-zero on
failure (safe to chain in scripts).
Output can be large on big trees — capture the full output to a file and read it in slices rather than scrolling inline.
Limitations
Validates DAFT only. Non-DAFT layouts (COCO, YOLO, Data Factory JSONL, etc.) belong in the upstream converter skills.
Supported formats are whatever
tao-daft validate --helpreports for the installed version; older slugs may have been retired.Covers
validateonly. Defer to the dedicated skills fortao-daft infoandtao-daft convert.Don't reimplement validation in Python; the CLI is the spec.
Troubleshooting
tao-daft: command not found— wheel not installed in the active env.pip install nvidia-tao-daft; verifytao-daft --version.error: argument --path is required— path passed positionally. Move it behind--path.invalid choice: '<format>'— slug isn't wired up in this version. Re-runtao-daft validate --helpand pick from the list.Auto-detection (raw type / contextual set) is wrong — override via the format's scope-restriction flag; discover the name from the leaf
--help.CI wants warnings to fail — add
--strict.
Files
- ATTRIBUTION.mdAdded by AutoGineer951 B
- BENCHMARK.md7.2 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md4.9 KiB
- config/skillspector-baseline.yaml834 B
- evals/evals.json880 B
- skill-card.md4.0 KiB
- skill.oms.sig4.7 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
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
The author says: Requires Python 3.10+ and the nvidia-tao-daft package (pip install nvidia-tao-daft).
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
- Instructions that use the network
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-validate-dataset-format · 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-validate-dataset-format.zip