Generated banner for Tao Run Deft Object Detection
Generated logo for Tao Run Deft Object Detection

Tao Run Deft Object Detection

NVIDIAOfficialCreated by NVIDIA Corporation

  • Skill
  • Workflow
  • Software development
  • Apache-2.0
  • Medium risk
  • Has scripts

From the author

Run the full DEFT smart-data-augmentation loop for NVIDIA TAO Grounding DINO object detection: zero-shot baseline inference, KPI analysis, per-class gap analysis, SigLIP embedding of weak images, unique-neighbor mining against a source pool, ODVG dataset staging, and retraining — repeated for a fixed number of iterations. Also prepares the source pool the loop mines from, as a separate run: Co-DETR pseudo-labeling, folding to the target classes, KITTI→COCO→ODVG conversion, and embedding. Use for prompts like "run the DEFT OD loop", "run smart data augmentation for grounding dino", "mine and retrain my detection model", "improve OD mAP with gap analysis and mining", "prep the source pool", or "pseudo-label my unlabeled images for mining"; do not use for standalone TAO training, one-off inference, or gap analysis alone.
— the description by NVIDIA Corporation

AutoGineer summary

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

This skill executes a multi-stage, iterative workflow designed to improve object detection model performance through smart data augmentation. It manages a complete loop including zero-shot baseline inference, KPI analysis, per-class gap analysis, SigLIP-based embedding, unique-neighbor mining from a source pool, dataset staging, and retraining. The skill also provides a separate invocation for preparing the source pool, which involves pseudo-labeling raw images with Co-DETR, remapping classes, and converting data formats. It operates as a state-managed loop, ensuring consistency across iterations and providing automated reporting.

What it does

  • Performs zero-shot baseline inference and KPI analysis on Grounding DINO models.
  • Conducts per-class gap analysis to identify model weaknesses.
  • Mines unique, high-value training samples from a prepared source pool using SigLIP embeddings.
  • Stages mined data into the ODVG format for iterative model retraining.
  • Prepares source pools by pseudo-labeling raw images and converting them to the required ODVG format.
  • Maintains a persistent state machine to track progress and ensure auditability across training iterations.

When to use it

  • When you need to improve the mAP of a Grounding DINO model through iterative data mining.
  • When you have a large pool of unlabeled images that need to be pseudo-labeled and mined for training.
  • When you want to automate the gap analysis, mining, and retraining cycle.
  • When you need to prepare a source pool of images for use in a DEFT-based detection workflow.

Advantages

  • Automates complex, multi-step data augmentation and training loops.
  • Reduces manual effort in identifying and labeling high-value training data.
  • Ensures consistent data processing and state management across iterations.
  • Provides clear visibility into model performance trends through automated KPI reporting.

Usage examples

“run the DEFT OD loop”
The agent initiates the iterative mining and retraining process, starting with baseline inference and gap analysis.
“prep the source pool”
The agent runs the Co-DETR pseudo-labeling and embedding pipeline to prepare your raw images for future mining.
“mine and retrain my detection model”
The agent performs gap analysis, mines new samples from the source pool, stages the data, and triggers a retraining iteration.
“improve OD mAP with gap analysis and mining”
The agent executes the full DEFT loop to identify performance gaps and iteratively grow the training dataset to boost mAP.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/nvidia/tao-run-deft-object-detection/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip tao-run-deft-object-detection.zip -d .agents/skills

Documentation by NVIDIA Corporation

Skill: tao-run-deft-object-detection

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).

Execution Contract

Treat this as a disk-backed state machine, not as a prose recipe.

  1. Preserve every explicit user value. epoch 1 means train.num_epochs=1; a spec value or documented default applies only when the user did not supply that parameter. Show the source of every run parameter (user, spec, or default) in the Pre-Flight Summary.

  2. After the user approves the Summary, initialize deft_state.json once with scripts/init_deft_state.py. Never hand-author or reinitialize it on resume.

  3. Run every bundled or inline host-Python command through scripts/deft_python.sh. On startup, after context compaction, before every stage, and before any completion claim, run:

    <skill_root>/scripts/deft_python.sh \
      <skill_root>/scripts/audit_deft_run.py --results-dir "${RESULTS_DIR}"

    If it prints DEFT_RUN_STATUS=INVALID, stop and repair the listed disk inconsistency; do not launch another stage. Read the path printed as read_before_action before continuing.

  4. Invoke the mapped underlying skill after reading the DEFT overlay. Do not replace a missing or unread stage reference, or a failed skill call, with guessed shell commands, inline Python, a different output tree, or fabricated data.

  5. Commit every stage with scripts/commit_stage.py; it verifies artifacts, updates deft_state.json, appends exactly one ordered loop_log.jsonl event, and rolls back if its audit fails.

  6. Claim the loop complete only when this exits zero:

    <skill_root>/scripts/deft_python.sh \
      <skill_root>/scripts/audit_deft_run.py \
      --results-dir "${RESULTS_DIR}" --require-complete

Context Discipline

  • Load references just in time. Run the audit, read only its read_before_action file and the current stage's named section, then act. Never preload all references.

  • Redirect verbose train, inference, and Docker output to files. Inspect at most the final 40 lines or a one-line artifact check; never print a full spec, state file, or loop log into the conversation.

  • A Skill-tool call loads stage instructions; it does not start a background orchestrator. Continue the documented stage in the parent immediately after it returns.

When to Use This Skill

Use this skill when the user wants an agent to run the full smart-data-augmentation loop for a TAO Grounding DINO detection model: zero-shot baseline, gap analysis, mining, dataset growth, and retraining across N iterations.

  • "Run the DEFT OD loop"

  • "Run smart data augmentation for grounding dino"

  • "Mine more training data for my detection model and retrain"

  • "Improve detection mAP with gap analysis and unique-neighbor mining"

Also use it to prepare the source pool, which is a separate run that completes before the loop launches (see ## Two Invocations: Prep, Then Loop):

  • "Prep the source pool"

  • "Pseudo-label my unlabeled images for mining"

  • "Build the mining pool from these raw images"

Do not use this skill for a single standalone TAO training run, one-off inference, or gap analysis alone. Invoke the relevant leaf skill directly instead.

Scope: Grounding DINO + ODVG

This loop targets Grounding DINO with ODVG training annotations (tmm_odvg.jsonl + labelmap.json), matching the reference pipeline. dataset.train_data_sources is a list; each iteration appends one new ODVG source rather than rewriting a combined CSV. DINO and RT-DETR (COCO) are not supported by this workflow — use the leaf skills directly for those.

The loop does not train at baseline. It evaluates the supplied zero-shot / pretrained checkpoint as iteration 0 and only trains from iteration 1 onward, once mining has produced data to add.

Two Invocations: Prep, Then Loop

The source pool is prepared by its own run, before the loop launches. They are separate because a pool is prepped once and then serves many loop runs — coupling them would re-label and re-embed the same images on every launch.

InvocationDoesProduces
"Prep the source pool"Co-DETR pseudo-labels raw pool images, folds to the target classes, converts KITTI→COCO→ODVG, verifies, embedscoco.json, odvg/, source_embeddings.parquet, pool_report.json
"Run the DEFT loop"baseline → iterationscheckpoints, KPI, the mAP trend

Follow references/prep-source-pool.md for the first. The loop then takes those four paths as inputs; Pre-Flight validates them and init_deft_state.py pins them, so a run cannot reach mine with no corpus to search.

Launch Intake

Do not ask which platform to run on. This workflow supports one: every stage launches with docker run, and its compatibility line requires docker plus the nvidia-container-toolkit. The bank's rule in AGENTS.md is to treat a single supported platform as the selection and only ask when an application supports several — asking here would offer a choice that nothing downstream can act on.

Read tao-run-on-docker's ## Credentials section.

Never ask for or read credential values. Check only whether the required environment variable is set; if unset, tell the user which variable to export.

Agent Behavior

There is exactly one user gate: pre-flight confirmation. Print the Pre-Flight Summary (see references/preflight.md), then STOP and wait for explicit approval ("go", "yes", "looks good"). Do not launch any side-effecting step before that approval.

After the gate, the skill is fully autonomous. Run the entire loop without asking for confirmation. Only stop if a step fails with an unrecoverable error or a hard-stop gate fires. Print a one-line status update at each stage milestone.

Auto-mode required. The post-gate loop fires constant side-effecting calls; without auto-accept mode it stalls on the first prompt. Remind the user at the Pre-Flight Summary to enable auto-mode (shift+tab) before approving.

Non-zero command rule. Never repeat an unchanged failed command. Read the final error block, map it to the loaded stage reference, make one evidence-based correction, and rerun its documented verification. If the reference does not cover the failure, commit status=error and halt.

Revised plan. If any run parameter changes after the Summary was shown, re-run Pre-Flight and show an updated Summary before proceeding.

Workflow

Full detail in references/pipeline-and-state.md.

  1. Pre-Flight. Run every check in references/preflight.md. Resolve workspace, specs, annotations, the zero-shot checkpoint, the source-pool embedding parquet, and container images. Hard stop only on missing input you cannot resolve yourself.

  2. Prep (once, before baseline). If the source pool is not already labeled and embedded, pseudo-label it with Co-DETR, fold the predictions onto the user's target classes, convert KITTI→COCO→ODVG, and embed the pool. Skip any step whose output already exists — no script does this for you, so check before each step. See references/prep-source-pool.md.

  3. Baseline (iter_0) — no training. Run inference with the supplied zero-shot / pretrained checkpoint, then kpi_analyze. Seed train_grounding_dino.yaml from the user's template for later iterations to extend.

  4. Iterate. For each iteration 1..max_iterations, run the seven stages in order: gap_analysis → embed → mine → stage → train → inference → kpi_analyze. Each iteration's gap_analysis consumes the previous phase's inference labels. Between stages run the audit and follow its one-line disk-backed next action.

  5. Stop when max_iterations is reached or a hard-stop gate fires. mAP is reported, not gated — the loop does not early-exit on a metric target.

  6. The report renders itself. results/DEFT_Loop_Report.md is written by init_deft_state.py and re-rendered by every accepted commit_stage.py call. Do not spawn a subagent for it and do not compose it by hand; to refresh it out of band, run scripts/render_report.py --results-dir "${RESULTS_DIR}".

All stages run inline in the parent context. Prefer invoking the underlying tao-skill-bank:* skills via the Skill tool, layering loop conventions on top via the matching references/*.md overlay.

Using Bundled Scripts

Run bundled scripts through <skill_root>/scripts/deft_python.sh. Resolve every path argument to an absolute host path first. Use commit_stage.py for all state and log writes. See references/scripts-and-agents.md.

Stage Reference Modules

Each stage maps to one underlying skill or to bundled glue. Read only the current stage's overlay, then invoke.

The overlays are written against two loop variables that Pre-Flight sets and every stage uses: N, the current iteration number, and PHASE, which is baseline or iter${N}. They are stated here because a stage overlay is read on its own — see references/preflight.md for the full set.

If an overlay is missing, stop and ask the user to reinstall the plugin — the loop cannot run a stage whose settings it does not have. If a mapped skill is unavailable, do not stop and do not improvise: fall back to the overlay's documented docker run as described in references/scripts-and-agents.md, and commit that stage with --execution-path direct-container instead of the documented skill. The overlay carries everything the invocation needs, so the fallback produces the same artifacts.

On a runtime without a Skill tool (Codex, for example), the mapped skills are still on disk under the plugin root: read skills/<layer>/<name>/SKILL.md there for the invocation contract, then run it through the direct-container fallback above, committing the stage with --execution-path direct-container. On such a runtime that fallback is the expected route for every stage, not an exception.

StageOverlayUnderlying skill
prep (once)references/prep-source-pool.mdtao-skill-bank:tao-train-codetr + tao-generate-image-embeddings (+ bundled glue)
gap_analysisreferences/tao-analyze-gaps-od-map.mdtao-skill-bank:tao-analyze-gaps-od-map
embedreferences/tao-generate-image-embeddings.mdtao-skill-bank:tao-generate-image-embeddings
minereferences/tao-mine-od-images.mdtao-skill-bank:tao-mine-od-images
stagereferences/stage-mined-data.md(bundled glue — no leaf skill)
train, inferencereferences/grounding-dino.mdtao-skill-bank:tao-train-grounding-dino
kpi_analyzereferences/tao-analyze-detection-kpi.mdtao-skill-bank:tao-analyze-detection-kpi

Path rule (invariant). Record absolute host paths under ${RESULTS_DIR}. Mount "$WORKSPACE:$WORKSPACE" with identical host and container paths. TAO's update_results_dir appends the task name to results_dir, so passing results_dir=X to train writes X/train/ and to inference writes X/inference/. Never append the subdirectory yourself.

Data, Pre-Flight, Pipeline, and State References

TopicReference
Data contract, ODVG layout, source pool, output treereferences/data-layout.md
One-time source-pool prep (pseudo-label, remap, convert, embed)references/prep-source-pool.md
Pre-Flight checks, defaults, Summary templatereferences/preflight.md
Pipeline stages, state schema, loop-end sequencereferences/pipeline-and-state.md
Bundled scripts, glue, the report renderer, stage tablereferences/scripts-and-agents.md

max_iterations defaults to 1 — one mine, train and score pass, the smallest run that yields a comparison against the baseline. Confirm it with the user when they have not said how many iterations they want; an unattended run takes the default rather than stopping to ask.

Gating

Run the full Pre-Flight, print the Summary, then STOP at the one user gate. After approval, run the baseline and the seven-stage iteration pipeline.

Hard-stop and never auto-retry on: any stage status=error; a missing or zero-row source-pool embedding parquet; a zero-row mining result when weak images were present; a missing ODVG annotation source; an image/annotation mismatch after staging; or a train exit that emits no new iteration checkpoint. The loop stops when max_iterations is reached or an unrecoverable gate fires. Each terminal path commits loop_stop through commit_stage.py, then follows the loop-end sequence in references/pipeline-and-state.md.

Files

scripts/apply_spec_overrides.py

#!/usr/bin/env python3
# SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
# SPDX-License-Identifier: Apache-2.0

"""Set values in a spec emitted by ``emit_default_spec.py``.

Completes the pair: ``emit_default_spec.py`` produces the canonical spec with
``???`` on mandatory fields, this fills them, and no spec is ever hand-edited.

    --apply-workflow-defaults assets/overlays/kpi_analyze.yaml --set results_dir=/abs/out

Every value in the final spec comes from one of three places, and the flags exist
to keep them apart:

1. **TAO's own default**, for any field nobody mentions. Left alone.
2. **A workflow default** — a setting this workflow requires that differs from
   TAO's default, the same on every run. These live in version control as a flat
   dotted-key YAML under ``assets/overlays/``, one file per stage, and are applied
   with ``--apply-workflow-defaults FILE`` (repeatable, applied in order, first).
3. **A run-specific value** — paths, checkpoints, GPU counts. ``--set KEY=VALUE``,
   applied last.

The split exists because 1 and 2 are indistinguishable in the finished spec. TAO's
analytics default for ``kpi.num_recall_points`` is 11 where this workflow needs 101;
a run that never names it reads AP off a coarser curve and nothing reports a
difference. Holding workflow defaults in a file applies them on every run and makes
changing one show up as a diff.

A ``--set`` naming a key a workflow-defaults file already set is an error: a run
quietly overriding a documented workflow setting is exactly the case worth catching.
``--allow-workflow-default-override`` permits it where a run genuinely must differ,
and says so on stderr.

Keys are dotted paths into nested mappings. Values are parsed as YAML scalars, so
``8`` is an int, ``true`` a bool, ``null`` None, ``[a, b]`` a list, and anything
else a string — matching how the same text would behave written into the file.

``--set-from-file KEY=FILE`` is ``--set`` with the value read from a file, so a
mapping another script emitted is never retyped by hand. Unlike a workflow-defaults
file, which holds one dotted key per leaf, this assigns a whole block — which is why
it is a separate flag rather than another file to apply.

Creating a key that is not already present requires ``--allow-new``. Without it a
typo'd path is an error rather than a silently added field the loader ignores,
which is the failure mode this script exists to prevent.

``--require-no-mandatory`` exits non-zero if any ``???`` remains. Prefer
``--require-no-mandatory-under BLOCK`` for a stage that uses one block of a
multi-action spec: ``default_specs`` marks fields mandatory for every action it
supports, so the whole-spec check can never pass for, say, a KITTI→COCO conversion
that never reads the ``odvg`` block.
"""

from __future__ import annotations

import argparse
import json
import sys
from pathlib import Path

import yaml

MANDATORY = "???"


def parse_value(raw: str):
    """Parse a scalar the way PyYAML would if it were written into the file."""
    return yaml.safe_load(raw)


def set_path(tree: dict, dotted: str, value, allow_new: bool,
             materialised: set[str]) -> str:
    """Set tree[a][b][c] = value. Returns a repr of what was there before.

    ``materialised`` accumulates the dotted paths of blocks this invocation turned
    from ``null`` into a mapping, and is shared across every ``--set``.

    A block the schema declares ``null`` -- ``dataset.infer_data_sources`` is one --
    has no declared members, so no member key can be checked against it. Requiring
    the leaf to pre-exist there would reject every key the caller came to add, and
    checking only the first would reject the second. Once a block is materialised
    it stays open for the rest of the call; blocks the schema really defines still
    reject unknown keys.
    """
    parts = dotted.split(".")
    node = tree
    for i, key in enumerate(parts[:-1]):
        path = ".".join(parts[: i + 1])
        if not isinstance(node, dict) or key not in node:
            if not allow_new:
                raise KeyError(f"{path!r} is not in the spec (pass --allow-new to create it)")
            node[key] = {}
            materialised.add(path)
        elif node[key] is None:
            node[key] = {}
            materialised.add(path)
        node = node[key]

    leaf = parts[-1]
    parent = ".".join(parts[:-1])
    if not isinstance(node, dict):
        raise KeyError(f"{parent!r} is not a mapping")
    if leaf not in node and not allow_new and parent not in materialised:
        raise KeyError(f"{dotted!r} is not in the spec (pass --allow-new to create it)")
    previous = node.get(leaf, "<absent>")
    node[leaf] = value
    return repr(previous)


def load_overlay(path: Path) -> dict[str, object]:
    """Load a flat ``dotted.key: value`` overlay.

    Flat rather than nested so each setting is one line: a nested block would
    diff as a block, and a reviewer checking whether ``kpi.num_recall_points`` is
    still 101 would have to read the surrounding structure to find out.

    A mapping value is rejected for the same reason it would be wrong: writing
    ``kpi: {iou_threshold: 0.5}`` replaces the whole ``kpi`` block, silently
    dropping every sibling the schema had emitted.
    """
    data = yaml.safe_load(path.read_text(encoding="utf-8")) or {}
    if not isinstance(data, dict):
        raise ValueError(f"{path}: expected a mapping of dotted keys, got {type(data).__name__}")
    for key, value in data.items():
        if not isinstance(key, str):
            raise ValueError(f"{path}: key {key!r} is not a string")
        if isinstance(value, dict):
            raise ValueError(
                f"{path}: {key!r} has a mapping value. Use one dotted key per leaf "
                f"({key}.<field>: <value>) — assigning a whole block replaces it and "
                "drops the fields the schema emitted alongside."
            )
    return data


def remaining_mandatory(tree, prefix: str = "") -> list[str]:
    found: list[str] = []
    if isinstance(tree, dict):
        for k, v in tree.items():
            found += remaining_mandatory(v, f"{prefix}{k}.")
    elif isinstance(tree, list):
        for i, v in enumerate(tree):
            found += remaining_mandatory(v, f"{prefix}{i}.")
    elif tree == MANDATORY:
        found.append(prefix.rstrip("."))
    return found


def parse_args() -> argparse.Namespace:
    parser = argparse.ArgumentParser(description=__doc__,
                                     formatter_class=argparse.RawDescriptionHelpFormatter)
    parser.add_argument("--spec", required=True, help="Spec to modify.")
    parser.add_argument("--out", default=None, help="Where to write. Defaults to --spec.")
    parser.add_argument("--apply-workflow-defaults", "--overlay",
                        dest="overlay", action="append", default=[], metavar="FILE",
                        help="Settings this workflow requires that differ from TAO's "
                             "defaults, as a flat dotted-key YAML. Repeatable; applied in "
                             "order, before --set. (--overlay is the former name.)")
    parser.add_argument("--set", action="append", default=[], metavar="KEY=VALUE",
                        help="Run-specific dotted key and YAML-parsed value. Repeatable.")
    parser.add_argument("--set-from-file", "--set-from-yaml",
                        dest="set_from_yaml", action="append", default=[], metavar="KEY=FILE",
                        help="Like --set, but the value is read from a YAML file, so a "
                             "generated block goes in whole instead of being retyped. A file "
                             "with one top-level key contributes that key's value. Repeatable. "
                             "(--set-from-yaml is the former name.)")
    parser.add_argument("--allow-workflow-default-override", "--allow-overlay-override",
                        dest="allow_overlay_override", action="store_true",
                        help="Permit a --set to change a key a workflow-defaults file "
                             "already set. Without it that collision is an error.")
    parser.add_argument("--allow-new", action="store_true",
                        help="Permit creating keys absent from the spec.")
    parser.add_argument("--require-no-mandatory", action="store_true",
                        help="Exit non-zero if any ??? remains anywhere in the spec.")
    parser.add_argument("--require-no-mandatory-under", action="append", default=[],
                        metavar="PREFIX",
                        help="Exit non-zero only if a ??? remains under this dotted prefix. "
                             "Repeatable. A schema dump carries mandatory fields for every "
                             "action it supports, so the whole-spec check cannot pass for a "
                             "stage that uses one block — scope it to the blocks the stage "
                             "actually reads.")
    parser.add_argument("--report-json", default=None,
                        help="Record every key applied and its source, so a run can be "
                             "audited without re-deriving what the overlay contained.")
    return parser.parse_args()


def main() -> int:
    try:
        args = parse_args()

        spec_path = Path(args.spec).expanduser().resolve()
        if not spec_path.is_file():
            raise FileNotFoundError(f"--spec does not exist: {spec_path}")
        tree = yaml.safe_load(spec_path.read_text(encoding="utf-8")) or {}
        if not isinstance(tree, dict):
            raise ValueError(f"{spec_path}: expected a mapping at the top level")

        # Collected rather than printed as we go: nothing is written until every
        # override succeeds, so reporting one as applied before then is a lie if a
        # later one raises.
        applied: list[str] = []
        materialised: set[str] = set()
        record: dict[str, dict] = {}

        # Overlays first, so --set carries only what varies per run and a
        # collision between the two is detectable rather than last-write-wins.
        from_overlay: dict[str, str] = {}
        for overlay_arg in args.overlay:
            overlay_path = Path(overlay_arg).expanduser().resolve()
            if not overlay_path.is_file():
                raise FileNotFoundError(
                    f"--apply-workflow-defaults does not exist: {overlay_path}")
            for dotted, value in load_overlay(overlay_path).items():
                try:
                    previous = set_path(tree, dotted.strip(), value,
                                        args.allow_new, materialised)
                except KeyError as exc:
                    raise KeyError(
                        f"{exc.args[0]} — from workflow defaults {overlay_path.name}; no changes "
                        "were written, the spec is unmodified"
                    ) from exc
                from_overlay[dotted.strip()] = overlay_path.name
                record[dotted.strip()] = {"source": overlay_path.name, "value": value}
                applied.append(f"  {dotted.strip()}: {previous} -> {value!r}  [{overlay_path.name}]")

        # A generated block is loaded whole rather than retyped as a --set literal:
        # a fold transcribed by hand is a fold that can be typed wrong. A file with
        # one top-level key contributes that key's value, so an emitted
        # `category_mapping:` file drops straight onto `inference.category_mapping`.
        for item in args.set_from_yaml:
            if "=" not in item:
                raise ValueError(f"--set-from-file expects KEY=FILE, got {item!r}")
            dotted, filename = item.split("=", 1)
            dotted = dotted.strip()
            src = Path(filename.strip()).expanduser().resolve()
            if not src.is_file():
                raise FileNotFoundError(f"--set-from-file does not exist: {src}")
            loaded = yaml.safe_load(src.read_text(encoding="utf-8"))
            if isinstance(loaded, dict) and len(loaded) == 1:
                loaded = next(iter(loaded.values()))
            if dotted in from_overlay and not args.allow_overlay_override:
                raise ValueError(
                    f"--set-from-file {dotted} collides with workflow defaults "
                    f"{from_overlay[dotted]}; pass --allow-workflow-default-override "
                    "if this run genuinely must differ."
                )
            try:
                previous = set_path(tree, dotted, loaded, args.allow_new, materialised)
            except KeyError as exc:
                raise KeyError(
                    f"{exc.args[0]} — no changes were written; the spec is unmodified"
                ) from exc
            record[dotted] = {"source": src.name, "value": loaded}
            applied.append(f"  {dotted}: {previous} -> <{src.name}>  [set-from-file]")

        for item in args.set:
            if "=" not in item:
                raise ValueError(f"--set expects KEY=VALUE, got {item!r}")
            dotted, raw = item.split("=", 1)
            dotted = dotted.strip()
            if dotted in from_overlay and not args.allow_overlay_override:
                raise ValueError(
                    f"--set {dotted} collides with workflow defaults "
                    f"{from_overlay[dotted]}, which already set it. That file holds "
                    "settings this workflow requires on every run, so "
                    "a --set that changes one is the drift this guards against. Pass "
                    "--allow-workflow-default-override if this run genuinely must differ."
                )
            if dotted in from_overlay:
                print(f"NOTE: --set {dotted} overrides workflow default "
                      f"{from_overlay[dotted]}",
                      file=sys.stderr)
            try:
                previous = set_path(tree, dotted, parse_value(raw),
                                    args.allow_new, materialised)
            except KeyError as exc:
                raise KeyError(
                    f"{exc.args[0]} — no changes were written; the spec is unmodified"
                ) from exc
            record[dotted] = {"source": "--set", "value": parse_value(raw)}
            applied.append(f"  {dotted}: {previous} -> {raw}")

        out = Path(args.out).expanduser().resolve() if args.out else spec_path
        out.parent.mkdir(parents=True, exist_ok=True)

        # Validate before the file lands. Writing first and checking after left an
        # invalid spec on disk on a non-zero exit, which a resume reads as usable.
        left = remaining_mandatory(tree)
        scoped = [
            key for key in left
            if any(key == prefix or key.startswith(f"{prefix}.")
                   for prefix in args.require_no_mandatory_under)
        ]
        blocking = left if args.require_no_mandatory else scoped
        if blocking:
            where = ("" if args.require_no_mandatory
                     else f" under {', '.join(args.require_no_mandatory_under)}")
            print(f"  {len(blocking)} field(s) still ???{where}: "
                  f"{', '.join(blocking[:8])}", file=sys.stderr)
            print(f"  nothing was written; {out} is unchanged", file=sys.stderr)
            return 1

        with out.open("w", encoding="utf-8") as fh:
            yaml.safe_dump(tree, fh, sort_keys=False, default_flow_style=False)
        if args.report_json:
            rp = Path(args.report_json).expanduser().resolve()
            rp.parent.mkdir(parents=True, exist_ok=True)
            rp.write_text(json.dumps({
                "spec": str(spec_path),
                "out": str(out),
                "overlays": [Path(o).name for o in args.overlay],
                "applied": record,
            }, indent=2, default=str), encoding="utf-8")

        for line in applied:
            print(line)
        print(f"spec -> {out}")

        if left:
            print(f"  {len(left)} field(s) still ???: {', '.join(left[:8])}",
                  file=sys.stderr)
        return 0
    except Exception as exc:  # noqa: BLE001
        print(f"ERROR: {exc}", file=sys.stderr)
        return 1


if __name__ == "__main__":
    raise SystemExit(main())

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 docker + nvidia-container-toolkit and one or more CUDA GPUs. Workflows declare additional requirements.

Security

What our scanner noticed· Medium risk

  • Large base64-encoded blobs
  • References to credential files
  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

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-run-deft-object-detection · 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-run-deft-object-detection.zip