Official agent skill

Tao Run Deft Cr Its Mining

by NVIDIA in NVIDIA/skills

Run the mining-based DEFT improvement workflow for ITS Cosmos-Reason binary video questions, focused on the non-reasoning classification/evaluation path.

OfficialApache-2.0Auto-check: notes

Install Tao Run Deft Cr Its Mining

skills CLI
$ npx skills add NVIDIA/skills --skill tao-run-deft-cr-its-mining -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/skills tao-run-deft-cr-its-mining --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tao-run-deft-cr-its-mining .claude/skills/tao-run-deft-cr-its-mining && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tao-run-deft-cr-its-mining
GitHub stars
3.6k
Token cost
~4.9k tokens
SKILL.md length
2,027 words
Files
33 (incl. scripts, references, assets)
Skills in repo
390
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run the mining-based DEFT improvement workflow for ITS Cosmos-Reason binary video questions, focused on the non-reasoning classification/evaluation path.

  • The user asks for a DEFT CR ITS mining workflow
  • SKILL.md covers Prerequisites, Bundled Resources, User Inputs (DEFT Workspace… and Baseline Evaluation, plus 4 more sections
  • Runs Python and Shell scripts from its folder
  • Traffic-camera Cosmos Reason improvement loop

What it does

Tao Run Deft Cr Its Mining is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Run the mining-based DEFT improvement workflow for ITS Cosmos-Reason binary video questions, focused on the non-reasoning classification/evaluation path. Use when the user asks for a DEFT CR ITS mining workflow, traffic-camera Cosmos Reason improvement loop, collision-identification workflow with data mining, or iterative Cosmos-RL refinement driven by gap analysis.

Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 37 other files, including scripts, reference files and assets (for example `BENCHMARK.md`, `assets/default_cosmos_embed_inference.yaml` and `config/skillspector-baseline.yaml`). Compatibility notes: Requires Docker with NVIDIA Container Toolkit, Python 3.11 with venv/ensurepip, numpy, pandas, pyarrow, PyYAML, and huggingfacehub, plus the selected platform…

The repository describes itself as: Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA, and RAG workflows end to end. The licence is Apache-2.0.

When your agent uses it

  • The user asks for a DEFT CR ITS mining workflow
  • Traffic-camera Cosmos Reason improvement loop
  • Collision-identification workflow with data mining
  • Iterative Cosmos-RL refinement driven by gap analysis

Example prompts

  • “/tao-run-deft-cr-its-mining”

Requirements

  • Python 3
  • A Bash shell
  • Docker
  • Compatibility (from SKILL.md): Requires Docker with NVIDIA Container Toolkit, Python 3.11 with venv/ensurepip, numpy, pandas, pyarrow, PyYAML, and huggingface_hub, plus the selected platform CLI.
  • Pre-approved tools (allowed-tools): Read, Bash, Write, Task

What it can do on your machine

Read from SKILL.md and the folder at commit 14a98ae. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • Write
    • Task

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 7 files in scripts/ (Python and Shell, from the files we listed), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires Docker with NVIDIA Container Toolkit, Python 3.11 with venv/ensurepip, numpy, pandas, pyarrow, PyYAML, and huggingface_hub, plus the selected platform CLI.

    From compatibility in the SKILL.md frontmatter.

Context cost

Tao Run Deft Cr Its Mining loads about 4.9k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 99 tokens; SKILL.md has 2,027 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~99
When it runs · the whole SKILL.md, loaded when a task matches
~4.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, Write, Task

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from NVIDIA/skills at commit 14a98ae, republished under its Apache-2.0 licence (© NVIDIA). 2,027 words, ~4,926 tokens.

Download SKILL.mdSave it as .claude/skills/tao-run-deft-cr-its-mining/SKILL.md (or your agent's skills folder). This skill also uses 32 other files; get the full folder from GitHub.
name
tao-run-deft-cr-its-mining
description
Run the mining-based DEFT improvement workflow for ITS Cosmos-Reason binary video questions, focused on the non-reasoning classification/evaluation path. Use when the user asks for a DEFT CR ITS mining workflow, traffic-camera Cosmos Reason improvement loop, collision-identification workflow with data mining, or iterative Cosmos-RL refinement driven by gap analysis.
allowed-tools
Read, Bash, Write, Task
compatibility
Requires Docker with NVIDIA Container Toolkit, Python 3.11 with venv/ensurepip, numpy, pandas, pyarrow, PyYAML, and huggingface_hub, plus the selected platform CLI.
license
Apache-2.0
metadata.author
NVIDIA Corporation
metadata.version
0.1.0
tags
application, workflow, deft, its, cosmos-reason, cosmos-rl, mining

Skill: TAO Run DEFT CR ITS Mining

Prerequisites

Before preflight, follow references/host-prerequisites.md; use its selected DEFT_PYTHON for every bundled helper and stop if the dependency probe fails.

Bundled Resources

Resolve DEFT_SKILL_ROOT to the absolute directory containing this installed SKILL.md. The agent or plugin runtime resolves this path; it is not a user input. Invoke bundled helpers with "$DEFT_PYTHON" "$DEFT_SKILL_ROOT/scripts/<name>.py" .... Never require a skill-bank checkout or change the user's working directory to a repository root.

This workflow invokes tao-finetune-cosmos-embed, tao-analyze-gaps-vlm-bcq, tao-mine-nearest-neighbors, and the selected platform skill by registered skill name. Those skills own their credentials, actions, and bundled assets. Cosmos Reason is workflow-owned: resolve images.tao_toolkit.deft_cosmos_reason, generate TOMLs with this workflow's helpers and configured base templates, and submit the exact train/evaluate commands in references/mining-loop.md through the selected platform. Do not invoke tao-finetune-cosmos-reason for planning, templates, action bundles, commands, or hook resolution.

User Inputs (DEFT Workspace and Workflow Configuration Yaml)

The user should provide a DEFT workspace absolute path that will be used for the entire run. This path should not be /workspace because that conflicts with the Cosmos Reason skills.

The layout of the DEFT workspace should be as follows:

text
<deft_workspace>/
├── data/
├── hf_cache/
├── model/
├── specs/
└── results/
PathPurpose
<deft_workspace>/data/User-provided KPI and training datasets, including LLaVA annotations and media directories.
<deft_workspace>/hf_cache/Persistent Hugging Face cache used when workflow steps download or reuse HF models.
<deft_workspace>/model/Local model/checkpoint inputs for the workflow, including the baseline Cosmos Reason checkpoint and any user-provided Cosmos Embed checkpoint.
<deft_workspace>/specs/User-provided configuration files, including templates for Cosmos Reason train and evaluate, Cosmos Embed inference, and TAO Data Services mining.
<deft_workspace>/results/All workflow-generated run artifacts, including state, logs, baseline evaluation, Cosmos Embed outputs, mining outputs, and iteration directories.

Each workflow run writes under a run-specific directory inside <deft_workspace>/results/. If run.name is set in workflow.yaml, that exact value is used as the directory name; otherwise the workflow creates a timestamped directory. For example, run.name: deft_cr_its_mining_test writes baseline evaluation under <deft_workspace>/results/deft_cr_its_mining_test/baseline/evaluate.

The run directory layout is:

text
<deft_workspace>/results/<run_name_or_timestamp>/
├── workflow.yaml
├── deft_state.json
├── loop_log.jsonl
├── bcq_accuracy_report.md
├── bcq_accuracy_summary.json
├── baseline/
│   └── evaluate/
│       └── bcq_accuracy_metrics.json
├── cosmos_embed_output/
│   ├── kpi/
│   └── train/
├── embedding_parquets/
│   ├── kpi/
│   │   └── embeddings.parquet
│   └── train/
│       └── embeddings.parquet
├── iter_1/
│   └── evaluate/
│       └── bcq_accuracy_metrics.json
├── iter_2/
└── ...

workflow.yaml is a copy of the high-level config that produced the run. loop_log.jsonl is the append-only event source for resume, and every stage-log append atomically refreshes deft_state.json as its current snapshot. baseline/evaluate/ stores the initial evaluation of the baseline model. Each completed evaluation also stores bcq_accuracy_metrics.json. The run-level bcq_accuracy_report.md and bcq_accuracy_summary.json compare the baseline with every completed iteration. cosmos_embed_output/kpi/ and cosmos_embed_output/train/ store raw Cosmos Embed preparation and inference outputs. embedding_parquets/kpi/ and embedding_parquets/train/ store the fixed mining-ready parquet artifacts computed once from the KPI and train datasets. Each iter_<N>/ directory stores the artifacts for one DEFT improvement iteration.

Workflow Configuration

There should be a file called <deft_workspace>/specs/workflow.yaml, which will be the high-level workflow config for the full DEFT run:

yaml
run:
  name: null
  max_iterations: 1

kpi_dataset:
  annotations_path: /abs/path/to/deft_workspace/data/kpi/annotations.json
  media_dir: /abs/path/to/deft_workspace/data/kpi/media

train_dataset:
  annotations_path: /abs/path/to/deft_workspace/data/train/annotations.json
  media_dir: /abs/path/to/deft_workspace/data/train/media

cosmos_reason:
  baseline_model_path: /abs/path/to/deft_workspace/model/reasoner_checkpoint
  base_evaluate_toml: /abs/path/to/deft_workspace/specs/cr_base_evaluate.toml
  base_train_toml: /abs/path/to/deft_workspace/specs/cr_base_train.toml
  continual_model: false

mining:
  embeddings_spec_template: /abs/path/to/deft_workspace/specs/cosmos_embed_inference_template.yaml
  embeddings_modality: both
  cosmos_embed_checkpoint_path: null
  embedding_parquets:
    kpi: null
    train: null
  mining_spec_template: /abs/path/to/deft_workspace/specs/mining_spec_template.yaml
  mine_unique_only: true

run, kpi_dataset, train_dataset, cosmos_reason, and mining are required; configured paths must be absolute inside <deft_workspace>. cosmos_reason.baseline_model_path must be a Cosmos Reasoner checkpoint. Convert a native Omni checkpoint first with tao-finetune-cosmos-reason. The optional continual_model defaults to false, which starts every iteration from the baseline. embeddings_modality selects KPI targets; train/source embeddings always include text and video. The optional mine_unique_only defaults to true and filters previously mined train/source paths from later iterations.

Write all workflow outputs under <deft_workspace>/results; do not add another output root. When run.name is set, use <deft_workspace>/results/<run.name> and explain that baseline/, cosmos_embed_output/, embedding_parquets/, and iter_<N>/ are nested there. When it is null, create <deft_workspace>/results/run_<YYYYMMDD_HHMMSS> and record that path in deft_state.json so resume never recomputes it.

Before running any workflow stage, validate the config:

bash
"$DEFT_PYTHON" "$DEFT_SKILL_ROOT/scripts/verify_workflow_yaml.py" \
  --workspace "$WORKSPACE" \
  --workflow-yaml "$WORKSPACE/specs/workflow.yaml"

The validator checks required fields, workspace-contained absolute paths, embeddings_modality, path existence, Omni baselines, and compatibility between KPI/train LLaVA annotations and their media_dir. Every annotation needs a unique non-empty id; its video must resolve against that dataset's media directory. The Cosmos Embed template must declare a positive inference.num_gpus, which preflight prints for hardware verification. mining.cosmos_embed_checkpoint_path accepts null, an absolute workspace-local path, or a Hugging Face model id with an optional hf_model:// prefix. Optional mining.embedding_parquets.kpi and .train values must be absolute existing mining-ready Parquet files inside the workspace with filepath, embedding, and modality columns. KPI must contain exactly the selected modalities; train must contain both text and video. The removed text_embeddings and video_embeddings fields are invalid. Each stage still follows its underlying skill, container, or platform runner's mount behavior.

If preflight rejects a Cosmos3 Omni baseline, tell the user that this workflow requires a Reasoner checkpoint, ask them to convert it first with tao-finetune-cosmos-reason, and exit without initializing the workflow.

If the user does not provide custom Cosmos Reason or Cosmos Embed templates, copy $DEFT_SKILL_ROOT/assets/cr_base_evaluate.toml, $DEFT_SKILL_ROOT/assets/cr_base_train.toml, and $DEFT_SKILL_ROOT/assets/default_cosmos_embed_inference.yaml into <deft_workspace>/specs/. Use tao-mine-nearest-neighbors to copy its bundled assets/default_nearest_neighbors.yaml when the user does not provide a mining template. Point workflow.yaml at the workspace copies. The bundled Cosmos Embed template requests 8 GPUs; do not launch until preflight confirms the selected platform can satisfy that request, or the user approves a modified template.

Initialize a run once after validation:

bash
"$DEFT_PYTHON" "$DEFT_SKILL_ROOT/scripts/initialize_workflow.py" \
  --workspace "$WORKSPACE" \
  --workflow-yaml "$WORKSPACE/specs/workflow.yaml"

Use the printed run_dir as RUN_DIR for every later command. If run.name is null, never ask another preparation script to derive the run directory again; pass --run-dir "$RUN_DIR" so all stages write into the initialized run.

Do not use --force for an ordinary resume. It rewrites the state/config snapshot but intentionally leaves loop_log.jsonl and all stage artifacts in place. Use it only to repair the snapshot for the same run; choose a new run.name for a clean restart. Before resuming, run "$DEFT_PYTHON" "$DEFT_SKILL_ROOT/scripts/resume_position.py" --run-dir "$RUN_DIR" and continue from the reported stage.

Baseline Evaluation

Run baseline evaluation once before the DEFT iteration loop. This evaluates cosmos_reason.baseline_model_path on the KPI dataset and produces the first results.json used by gap analysis. Immediately run scripts/compute_bcq_accuracy_metrics.py on that file and store baseline/evaluate/bcq_accuracy_metrics.json. Its parser recognizes yes and no in short or free-form responses, including capitalization and punctuation. It reports false positives, false negatives, accuracy, balanced accuracy, and unparseable predictions. Use references/mining-loop.md for the exact commands, completion check, and logging rule.

Initialize Mining Embeddings

Initialize mining embeddings once before the DEFT iteration loop. The KPI and train datasets are fixed for the run, so their Cosmos Embed outputs are reusable across all iterations.

Use scripts/prepare_cosmos_embed_inference.py to prepare the Cosmos Embed inference specs from workflow.yaml. The KPI dataset requires the modality or modalities selected by mining.embeddings_modality; the train dataset always requires text and video. If the user provides a complete dataset Parquet under mining.embedding_parquets.kpi or .train, the preparation script stages it at $RUN_DIR/embedding_parquets/<dataset>/embeddings.parquet and generates no inference specs for that dataset. While staging, it remaps text embedding identifiers from the source run's question files to the current run's lookup by question content; embeddings and video identifiers are preserved. If the dataset value is null or omitted, the script generates every required modality spec for that dataset. Partial per-modality reuse is not supported. If mining.cosmos_embed_checkpoint_path is an absolute local path, the script uses it for generated specs. If it is a remote Hugging Face model id, with or without the hf_model:// prefix, the script downloads or reuses it under <deft_workspace>/hf_cache and writes the local downloaded checkpoint path into the generated inference specs. If the field is null, the script uses nvidia/Cosmos-Embed1-224p.

The script downloads remote HF checkpoints before Cosmos Embed runs because Cosmos Embed startup can race when inference.num_gpus > 1 and multiple workers try to download the same model at once. If both combined dataset Parquets are provided, the preparation script does not need the checkpoint and does not download it.

Use scripts/prepare_cosmos_embed_inference.py once. It prepares both the KPI dataset and the train dataset:

bash
"$DEFT_PYTHON" "$DEFT_SKILL_ROOT/scripts/prepare_cosmos_embed_inference.py" \
  --workspace "$WORKSPACE" \
  --workflow-yaml "$WORKSPACE/specs/workflow.yaml" \
  --run-dir "$RUN_DIR"

The preparation script writes only the missing embedding specs under the initialized RUN_DIR. Initialization owns the $RUN_DIR/workflow.yaml snapshot; this stage does not derive a new run or overwrite that snapshot.

For each dataset without a supplied combined Parquet, the preparation script writes all required modality-specific inference specs under cosmos_embed_output/<dataset>/specs/, creates raw Cosmos Embed result directories, stages text questions as files for stable joins, and writes lookup.parquet. After inference, the conversion script gathers those separate modality outputs into one mining-facing file per dataset. Each row contains filepath, embedding, and modality:

text
$RUN_DIR/embedding_parquets/kpi/embeddings.parquet
$RUN_DIR/embedding_parquets/train/embeddings.parquet

The KPI parquet contains only the selected modality or modalities. The train parquet always contains both text and video rows.

Show full SKILL.md (698 more words)Show less
Run Cosmos Embed Inference

Use tao-finetune-cosmos-embed for each generated inference spec. Follow the mandatory terminal-exit validation, permission repair, and conversion procedure in references/mining-loop.md. Do not run inference or conversion for a dataset whose combined Parquet was supplied during preparation.

The generated lookup Parquet uses annotation_id for the original LLaVA id and video_path for resolved media. Do not rename either column to video_id; that external field belongs to Cosmos Reason and gap-analysis records.

DEFT Mining Loop

Run iterations 1..run.max_iterations. The loop is mining-only: no PAIDF or generated-video branch runs in this skill. Before gap analysis, each iteration rewrites Cosmos Reason result video_id values from LLaVA annotation ids to resolved KPI video paths and stores the prepared predictions in the iteration's gaps/ directory. It then runs gap analysis, builds one selected-modality target parquet, mines it against the combined text/video train source in one tao-mine-nearest-neighbors run, converts mined rows to LLaVA annotations, merges annotations, trains Cosmos Reason, evaluates the trained checkpoint, computes that evaluation's BCQ accuracy metrics, and removes the resumable training checkpoints while preserving the exported safetensors. At loop termination, generate the run-level accuracy report and include its baseline/iteration table in the agent's final response. See references/mining-loop.md for exact commands and completion criteria.

Completion Criteria

StageComplete when
validate_workflowverify_workflow_yaml.py exits successfully.
initialize_workflow$RUN_DIR/workflow.yaml and $RUN_DIR/deft_state.json exist.
baseline_evaluateThe evaluate job exits successfully, exactly one baseline results.json is found, and baseline/evaluate/bcq_accuracy_metrics.json exists.
prepare_cosmos_embed_inferenceEach dataset has a lookup parquet and either all required Cosmos Embed specs or a staged combined embedding Parquet.
cosmos_embedEvery generated inference spec has a current completion_validation.json; exit 0 is accepted after output validation, while exit 130 additionally records a teardown warning.
convert_embeddingsembedding_parquets/{kpi,train}/embeddings.parquet exist; train contains both modalities and KPI contains the selected modalities.
gap_analysis$RUN_DIR/iter_<N>/gaps/predictions.json exists and the container exits successfully. The workflow counts valid rows directly from kpi_gaps.jsonl; missing or empty output after successful completion means zero weak samples.
prepare_nearest_neighbor_miningOne target parquet, optional filtered source parquet, and one nearest-neighbor spec exist.
mine_nearest_neighborsOne mined-neighbor parquet and mining summary exist.
record_mined_pathsWhen mine_unique_only is true, $RUN_DIR/mining/mined_paths_log.parquet exists; otherwise the stage is logged as skipped.
prepare_cosmos_reason_trainMined and accumulated LLaVA annotations plus train/specs/train.toml exist, with a positive expected optimizer-step count.
trainThe Cosmos Reason job reaches terminal success, reports at least one optimizer step, and has writable timestamped output and checkpoint directories.
evaluateEvaluation preparation finds the latest completed training checkpoint, the evaluation job exits successfully, exactly one iteration results.json is found, and its bcq_accuracy_metrics.json exists.
cleanup_cosmos_reason_trainingtrain/checkpoint_cleanup.json exists, raw checkpoint directories are gone, and its listed safetensors exports remain.
loop_stopStop reason is logged and bcq_accuracy_report.md plus bcq_accuracy_summary.json compare the baseline with every completed iteration.

Troubleshooting

Prediction id does not match an annotation: Confirm the evaluation used the same KPI annotations configured by kpi_dataset.annotations_path. Every Cosmos Reason result video_id must match a LLaVA annotation id or an already-resolved annotation video path.

No target embeddings matched: Check that gaps/predictions.json and gap-analysis video_id paths match the KPI LLaVA media paths used during embedding preparation. Text mode also requires the question text to match after removing <video> and trailing “Answer with yes or no.”

Mined neighbors do not join to train lookup: Confirm every mined filepath exists in embedding_parquets/train/embeddings.parquet. Its modality determines whether the path must match train lookup.parquet filepath for text or video_path for video.

Run directory looks nested under results/<run.name>: This is expected. run.name is the run directory name under <deft_workspace>/results; all baseline, embedding, and iteration artifacts are nested there.

Docker output permissions or Cosmos Reason status paths fail: Stop and follow the permission-repair and stage-local TAO status contracts in references/mining-loop.md.

Unparseable prediction count is nonzero: Report the count to the user and inspect the corresponding raw results.json responses. These predictions count as incorrect in accuracy and class recall; the metrics script does not silently drop them. An unparseable ground truth stops metric computation because the expected class is undefined.

Cosmos Reason reports No space left on device for /dev/shm/nccl-*: This is container shared memory, not ordinary disk capacity. For local Docker, run the Cosmos Reason action through tao-run-on-docker and require --shm-size=8g --ulimit memlock=-1 --ulimit stack=67108864. Confirm these flags in the submitted job before retrying. Other platforms must provide equivalent shared-memory and memlock settings.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 32 other files (scripts, references, assets) in skills/tao-run-deft-cr-its-mining of NVIDIA/skills.

  • SKILL.md
  • BENCHMARK.md
  • assets/cr_base_evaluate.toml
  • assets/cr_base_train.toml
  • assets/default_cosmos_embed_inference.yaml
  • config/skillspector-baseline.yaml
  • evals/evals.json
  • references/host-prerequisites.md
  • references/mining-loop.md
  • scripts/cleanup_cosmos_reason_training.py
  • scripts/compute_bcq_accuracy_metrics.py
  • scripts/cosmos_embed_outputs_to_parquet.py
  • scripts/deft_python.sh
  • scripts/find_cosmos_reason_results.py
  • scripts/initialize_workflow.py
  • scripts/log_stage.py
  • … and 17 more

Open the folder on GitHubat commit 14a98ae

Compare with similar skills

Tao Run Deft Cr Its Mining next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tao Run Deft Cr Its Mining compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tao Run Deft Cr Its Mining this skillNVIDIA/skills3.6k—~4.9kAutomated safety check: NotesApache-2.0
Skill Improversickn33/agentic-awesome-skills47k2 repos~1.5kAutomated safety check: PassMIT
Matematico Taosickn33/agentic-awesome-skills47k2 repos~459Automated safety check: PassMIT
Improve Oaselastic/kibana21k—~4.8kAutomated safety check: PassCustom licence
Self-Improve Evolutionary LoopYeachan-Heo/oh-my-claudecode40k—~5.3kAutomated safety check: WarnMIT
Cosmos Providerdotnet/efcore15k—~242Automated safety check: PassMIT

Similar skills

  • Skill Improver

    sickn33/agentic-awesome-skills

    Iteratively improve a Claude Code skill using the skill-reviewer agent until it meets quality standards.

    47k GitHub starsUsed in 2 repos~1.5k tokens
    Agent WorkflowsAuto-check passed
  • Matematico Tao

    sickn33/agentic-awesome-skills

    Matemático ultra-avançado inspirado em Terence Tao. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~459 tokens
    Auto-check passed
  • Improve Oas

    elastic/kibana

    Official

    Add or improve OpenAPI descriptions, examples, and code samples for a Kibana API area.

    21k GitHub stars~4.8k tokensUpdated today
    Backend & APIsAuto-check passed
  • Self-Improve Evolutionary Loop

    Yeachan-Heo/oh-my-claudecode

    Runs an autonomous improvement loop on a repository: agents propose and execute plans, a tournament picks the winner by benchmark, and each round is recorded and plotted.

    40k GitHub stars~5.3k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check: warnings
  • Cosmos Provider

    dotnet/efcore

    Official

    Implementation details for the EF Core Azure Cosmos DB provider.

    15k GitHub stars~242 tokensUpdated yesterday
    Auto-check passed
  • Skill Improvement Loop

    Donchitos/Claude-Code-Game-Studios

    Improves a single skill through a test, fix and retest loop, keeping or reverting each change based on how the static and category scores move.

    26k GitHub stars~1.7k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check: notes

More from NVIDIA/skills

All 390 skills in this repo
  • Official

    A skill your agent uses when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice.

    3.6k GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check passed
  • Official

    Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.

    3.6k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Official

    Runs and validates an end-to-end Mission Control demo in a locally installed Isaac Sim, with a Nova Carter robot driven through a Python server.

    3.6k GitHub stars~4.8k tokensUpdated yesterday
    Auto-check passed
  • Orchestrates defect image generation for PCBA, metal surface and glass inspection with NVIDIA Cosmos AnomalyGen on OSMO, from cold-start Day 0 to real-photo Day 1 labeling.

    3.6k GitHub stars~5k tokensUpdated yesterday
    Auto-check: notes
  • Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.

    3.6k GitHub stars~4.7k tokensUpdated yesterday
    Auto-check: notes
  • Official

    Runs NVIDIA TAO Data Services KPI analysis on object detection results, comparing predictions to ground truth and writing per-class precision, recall and AP to a CSV.

    3.6k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check: notes

Questions about Tao Run Deft Cr Its Mining

What does Tao Run Deft Cr Its Mining do?

Run the mining-based DEFT improvement workflow for ITS Cosmos-Reason binary video questions, focused on the non-reasoning classification/evaluation path. Tao Run Deft Cr Its Mining is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Run the mining-based DEFT improvement workflow for ITS Cosmos-Reason binary video questions, focused on the non-reasoning classification/evaluation path.

When should I use Tao Run Deft Cr Its Mining?

Tao Run Deft Cr Its Mining fits situations like: the user asks for a DEFT CR ITS mining workflow; traffic-camera Cosmos Reason improvement loop; collision-identification workflow with data mining; iterative Cosmos-RL refinement driven by gap analysis.

How do I install Tao Run Deft Cr Its Mining in Claude Code?

Run `npx skills add NVIDIA/skills --skill tao-run-deft-cr-its-mining -a claude-code`. Or copy the skill folder (skills/tao-run-deft-cr-its-mining in NVIDIA/skills) into .claude/skills/tao-run-deft-cr-its-mining in your project. Claude Code loads it when a task matches its description.

How do I install Tao Run Deft Cr Its Mining in Codex?

Run `npx skills add NVIDIA/skills --skill tao-run-deft-cr-its-mining -a codex`. Or copy the skill folder (skills/tao-run-deft-cr-its-mining in NVIDIA/skills) into .agents/skills/tao-run-deft-cr-its-mining in your project. Codex loads it when a task matches its description.

Can I use Tao Run Deft Cr Its Mining in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/skills --skill tao-run-deft-cr-its-mining -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tao-run-deft-cr-its-mining, .gemini/skills/tao-run-deft-cr-its-mining, .github/skills/tao-run-deft-cr-its-mining and .opencode/skills/tao-run-deft-cr-its-mining in your project.

What does Tao Run Deft Cr Its Mining need to run?

Going by SKILL.md and its folder, Tao Run Deft Cr Its Mining needs Python and a shell for the scripts in its folder. Our summary lists: Python 3; A Bash shell; Docker. Its frontmatter pre-approves these tools: Read, Bash, Write, Task. Compatibility (from SKILL.md): Requires Docker with NVIDIA Container Toolkit, Python 3.11 with venv/ensurepip, numpy, pandas, pyarrow, PyYAML, and huggingface_hub, plus the selected platform CLI..

Does Tao Run Deft Cr Its Mining access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Tao Run Deft Cr Its Mining safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Tao Run Deft Cr Its Mining use?

Tao Run Deft Cr Its Mining is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tao Run Deft Cr Its Mining use?

About 4.9k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.1k tokens, read only when the agent opens those files.

What are the alternatives to Tao Run Deft Cr Its Mining?

Skills that share tags, products or a category with Tao Run Deft Cr Its Mining: Skill Improver (sickn33/agentic-awesome-skills, 47k stars), Matematico Tao (sickn33/agentic-awesome-skills, 47k stars), Improve Oas (elastic/kibana, 21k stars) and Self-Improve Evolutionary Loop (Yeachan-Heo/oh-my-claudecode, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tao Run Deft Cr Its Mining?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,555 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 9, 2026.

Source: NVIDIA/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.