Official agent skill

Tao Train Bevfusion

by NVIDIA in NVIDIA/skills

BEVFusion for multi-sensor 3D object detection. An agent skill from NVIDIA/skills.

OfficialApache-2.0Auto-check: notesAI & LLM Engineering

Install Tao Train Bevfusion

skills CLI
$ npx skills add NVIDIA/skills --skill tao-train-bevfusion -a claude-code

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

GitHub CLI
$ gh skill install NVIDIA/skills tao-train-bevfusion --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-train-bevfusion .claude/skills/tao-train-bevfusion && 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-train-bevfusion
GitHub stars
3.5k
Token cost
~3.4k tokens
SKILL.md length
1,301 words
Files
16 (incl. references)
Skills in repo
386
Repo updated
First seen
Licence
Apache-2.0

At a glance

BEVFusion for multi-sensor 3D object detection. An agent skill from NVIDIA/skills.

  • Running inference for a TAO BEVFusion model
  • SKILL.md covers Dataclass Schemas, Train Action Policy, Training Requirements and Eval Dataset, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Phrases include train BEVFusion

What it does

Tao Train Bevfusion is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. BEVFusion for multi-sensor 3D object detection. Fuses LiDAR point clouds and camera images in bird's-eye-view (BEV) space, used in autonomous driving for robust 3D perception. Use when training, evaluating, or running inference for a TAO BEVFusion model. Trigger phrases include "train BEVFusion", "LiDAR + camera fusion", "BEV 3D detection", "multi-sensor 3D perception".

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files, including reference files (for example `BENCHMARK.md`, `config/skillspector-baseline.yaml` and `evals/evals.json`). Compatibility notes: Requires docker + nvidia-container-toolkit.

It sits in AI & LLM Engineering, covering Geospatial analysis and Computer vision. It works with NVIDIA AI 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

  • Running inference for a TAO BEVFusion model
  • Phrases include train BEVFusion
  • LiDAR + camera fusion
  • BEV 3D detection

Example prompts

  • “train BEVFusion”
  • “LiDAR + camera fusion”
  • “BEV 3D detection”
  • “/tao-train-bevfusion”

Requirements

  • Python 3
  • Docker
  • Compatibility (from SKILL.md): Requires docker + nvidia-container-toolkit.
  • Pre-approved tools (allowed-tools): Read, Bash

What it can do on your machine

Read from SKILL.md and the folder at commit dfdd080. 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

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

    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 + nvidia-container-toolkit.

    From compatibility in the SKILL.md frontmatter.

Context cost

Tao Train Bevfusion loads about 3.4k tokens when it runs, and up to ~9.3k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 1,301 words of instructions outside code blocks.

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

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/skills at commit dfdd080, republished under its Apache-2.0 licence (© NVIDIA). 1,301 words, ~3,369 tokens.

Download SKILL.mdSave it as .claude/skills/tao-train-bevfusion/SKILL.md (or your agent's skills folder). This skill also uses 15 other files; get the full folder from GitHub.
name
tao-train-bevfusion
description
BEVFusion for multi-sensor 3D object detection. Fuses LiDAR point clouds and camera images in bird's-eye-view (BEV) space, used in autonomous driving for robust 3D perception. Use when training, evaluating, or running inference for a TAO BEVFusion model. Trigger phrases include "train BEVFusion", "LiDAR + camera fusion", "BEV 3D detection", "multi-sensor 3D perception".
allowed-tools
Read, Bash
compatibility
Requires docker + nvidia-container-toolkit.
license
Apache-2.0
metadata.version
0.1.0
metadata.author
NVIDIA Corporation
tags
multi, sensor, 3d, detection

BEVFusion

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

BEVFusion for multi-sensor 3D object detection. Fuses LiDAR point clouds and camera images in bird's-eye-view (BEV) space. Used in autonomous driving for robust 3D perception.

Set pretrained backbone paths for Swin image backbone.

BEVFusion requires the BEVFusion-specific TAO container nvcr.io/nvidia/tao/tao-toolkit:5.5.0-pyt. <!-- unpinned: BEVFusion-only container --> Shared TAO PyTorch 7.x images do not package mmdet3d and fail before any BEVFusion action can parse its spec. The model-skill action is named dataset_convert, but the 5.5 container CLI subtask is bevfusion convert -e <spec>.

Dataclass Schemas

Generated TAO Core schemas are packaged in schemas/<action>.schema.json, with schemas/manifest.json listing available actions. Each generated schema also emits references/spec_template_<action>.yaml from the schema top-level default field. AutoML enablement is declared at the model layer in references/skill_info.yaml via automl_enabled. Runnable AutoML for an action requires schemas/<action>.schema.json and references/spec_template_<action>.yaml to exist and parse. Use the packaged selected-action schema for automl_default_parameters, automl_disabled_parameters, defaults, min/max bounds, enums, option weights, math conditions, dependencies, and popular parameters. Do not expect ~/tao-core at runtime; maintainers regenerate schemas/templates before packaging the skill bank.

Train Action Policy

This model is AutoML-enabled at the model layer. Before handling any train-stage request, read references/skill_info.yaml and resolve the run override from either an explicit automl_policy value or the user's workflow request. Use automl_policy: on by default and only expose on / off in new launch prompts. Treat phrases like "turn off AutoML", "disable AutoML", "no HPO", or "plain training" as automl_policy: off for this run only. When automl_policy: on, automl_enabled: true, and both schemas/train.schema.json and references/spec_template_train.yaml are packaged, route the train action through tao-skill-bank:tao-run-automl by default with this model's skill_dir. Preserve workflow/application overrides for datasets, specs, output directories, GPU/platform settings, parent checkpoints, and automl_policy. Use direct model training only when automl_policy: off or the packaged train schema/template is missing; in the missing-schema case, report that AutoML is enabled but not runnable for this model until schemas are generated.

Non-train actions such as evaluate, inference, export, and deploy flows stay in this model skill. The per-run automl_policy override does not change model metadata.

Training Requirements

  • Dataset type: bevfusion
  • Formats: default
  • Monitoring metric: AP11
Per-Action Dataset Requirements
ActionSpec KeySourceFilesList?
dataset_convertroot_diridNo
evaluatedataset.test_datasettrain_datasetsann_file: results/{dataset_convert_job_id}/kitti_person_infos_val.pklNo
inferencedataset.root_dirtrain_datasetsNo
inferencedataset.test_datasettrain_datasetsann_file: results/{dataset_convert_job_id}/kitti_person_infos_val.pklNo
traindataset.train_datasettrain_datasetsann_file: results/{dataset_convert_job_id}/kitti_person_infos_train.pklNo
traindataset.val_datasettrain_datasetsann_file: results/{dataset_convert_job_id}/kitti_person_infos_val.pklNo
traindataset.test_datasettrain_datasetsann_file: results/{dataset_convert_job_id}/kitti_person_infos_val.pklNo
Typical Spec Overrides

Data source overrides are mandatory for every action — the agent MUST construct data source paths from the Per-Action Dataset Requirements table above and include them in spec_overrides.

python
DATA_ROOT = "/path/to/kitti_root"
CONVERTED = DATA_ROOT  # BEVFusion 5.5 writes info pickles into root_dir.
DATA_PREFIX = {"pts": "training/velodyne_reduced", "img": "training/image_2"}

dataset_convert (mandatory data sources):

python
{
    "root_dir": DATA_ROOT,
    "results_dir": DATA_ROOT,
    "mode": "training",
}

train (mandatory data sources):

python
{
    "train.num_epochs": 30,
    "train.checkpoint_interval": 10,
    "train.validation_interval": 10,
    "train.num_gpus": 1,
    "dataset.root_dir": DATA_ROOT,
    "dataset.train_dataset": {"ann_file": f"{CONVERTED}/kitti_person_infos_train.pkl", "data_prefix": DATA_PREFIX},
    "dataset.val_dataset": {"ann_file": f"{CONVERTED}/kitti_person_infos_val.pkl", "data_prefix": DATA_PREFIX},
    "dataset.test_dataset": {"ann_file": f"{CONVERTED}/kitti_person_infos_val.pkl", "data_prefix": DATA_PREFIX},
}

evaluate (mandatory data sources):

python
{
    "dataset.root_dir": DATA_ROOT,
    "dataset.test_dataset": {"ann_file": f"{CONVERTED}/kitti_person_infos_val.pkl", "data_prefix": DATA_PREFIX},
}

inference (mandatory data sources):

python
{
    "dataset.root_dir": DATA_ROOT,
    "dataset.test_dataset": {"ann_file": f"{CONVERTED}/kitti_person_infos_val.pkl", "data_prefix": DATA_PREFIX},
}

Eval Dataset

Optional. Val dataset split is configured via ann_file in dataset config.

Important Parameters

  • dataset.classes: List of detection classes. Default ["person"]. Must match the annotation categories.
  • dataset.type: Dataset type. Options: KittiPersonDataset, TAO3DSyntheticDataset, TAO3DDataset.
  • dataset.root_dir: Root directory of the KITTI-style dataset.
  • dataset.box_type_3d: 3D box coordinate frame. Options: lidar, camera. Default lidar.
  • train.optimizer.lr: Learning rate. Default 2e-4 (AdamW). Use AmpOptimWrapper for mixed precision via optimizer.wrapper_type.
  • input_modality: Dict controlling sensor modalities. Keys: use_lidar (True), use_camera (True), use_radar (False), use_map (False).
  • model.img_backbone: Image backbone. Default mmdet.SwinTransformer (Swin-Tiny). embed_dims=96, depths=[2,2,6,2].
  • model.view_transform.type: View transform for BEV projection. Options: DepthLSSTransform, LSSTransform. Default DepthLSSTransform.
  • model.point_cloud_range: Spatial extent of LiDAR. Default [0,-40,-3,70.4,40,1].
  • model.voxel_size: Voxel dimensions. Default [0.05, 0.05, 0.1].
  • dataset.train_dataset.batch_size: Per-GPU batch size. Default 4.

Multi-GPU / Multi-Node

Launch method: torchrun (LIGHTNING_EXCLUDED_NETWORK). The entrypoint runs torchrun --nnodes=N --nproc-per-node=M train.py, NOT plain python.

Spec KeyDescriptionDefault
train.num_gpusNumber of GPUs per node1
train.gpu_idsGPU device indices[0]
train.num_nodesNumber of nodes1
  • CUDA_VISIBLE_DEVICES is explicitly set from TAO_VISIBLE_DEVICES
  • BEVFusion uses mmdet3d-based distributed training, not Lightning DDP
  • NODE_RANK is copied to RANK if RANK is unset

Multi-node env vars (set by orchestrator):

VariablePurpose
WORLD_SIZENumber of nodes
NODE_RANKThis node's rank
MASTER_ADDRRank-0 node IP
MASTER_PORTRank-0 port (default 29500)
NUM_GPU_PER_NODEGPUs per node

Hardware

One GPU is supported for minimal smoke/AutoML validation with a small dataset and batch size. Use 2+ GPUs for ordinary training and 4 GPUs when practical. 24GB+ (A100 recommended) VRAM per GPU. BEVFusion is memory-intensive due to multi-sensor fusion.

Show full SKILL.md (604 more words)Show less

Error Patterns

dataset_convert required: Run the model-skill dataset_convert action (bevfusion convert -e <spec> in the BEVFusion 5.5 container) before training to produce kitti_person_infos_train.pkl, kitti_person_infos_val.pkl, and training/velodyne_reduced. For direct local-docker 5.5 runs, set results_dir to the same mounted path as root_dir; the converter writes the info pickles there and later expects them under root_dir while reducing point clouds.

KITTI directory names: The BEVFusion 5.5 converter writes reduced point clouds under training/velodyne_reduced and expects camera images under training/image_2. Do not use the stale training/lidar_reduced or training/images/ defaults when chaining dataset_convert into train/evaluate or inference.

BEVFusion 5.5 config surface: Use the 5.5 dataclass keys in packaged templates. Remove newer top-level/action keys such as model_name, wandb.group, wandb.run_id, train.checkpoint_interval_unit, evaluate.trt_engine, evaluate.batch_size, inference.trt_engine, and inference.batch_size. For train, evaluate, and inference specs, keep the non-running action stubs (train, evaluate, and inference) present with empty checkpoint strings where needed; the 5.5 runners materialize the full experiment config before running the selected action. Use YAML null, not an empty string, for train.pretrained_checkpoint and train.resume_training_checkpoint_path when no checkpoint is intended.

ModuleNotFoundError: No module named 'mmdet3d': Shared TAO PyTorch 7.x images do not include the BEVFusion mmdet3d dependency. Use nvcr.io/nvidia/tao/tao-toolkit:5.5.0-pyt; <!-- unpinned: BEVFusion-only container --> it contains mmdet3d and exposes the BEVFusion convert, train, evaluate, and inference subtasks.

Post-evaluation SIGSEGV in BEVFusion 5.5: Some local-docker runs can write checkpoints or prediction files and still finish with TAO Execution status: FAIL after Signal 11 (SIGSEGV) in cuMemRetainAllocationHandle. Do not mark the action successful from the Docker exit code alone; inspect the TAO log or status.json. On CUDA 12+ hosts, retain the TAO 5.5 dependency stack and apply the BEVFusion rotated-IoU CPU fallback and runner cleanup from tao-pytorch; do not switch the action to a shared 7.x image. The fallback is the default; BEVFUSION_ROTATE_IOU_BACKEND=gpu is an explicit opt-in to the legacy Numba CUDA evaluator. If a checkpoint was produced before this failure, use only the exact intended checkpoint such as epoch_1.pth for downstream diagnostics and do not treat last_checkpoint as a best checkpoint unless the action explicitly requests the latest checkpoint.

Missing modality data: Ensure both camera images and LiDAR point clouds are present if using multi-modal fusion.

Epoch numbering: BEVFusion checkpoint epoch numbers may not follow standard zero-padded format.

Checkpoint handoff: Use the SDK/model checkpoint resolver for parent-model selection. For direct local-docker chaining, inspect the train results and pass the exact intended checkpoint path such as epoch_1.pth; use latest.pth only when the user explicitly asks for latest. Resume/retrain must set train.resume: true and train.resume_training_checkpoint_path to the exact checkpoint being resumed.

Spec Param / Parent Model Inference

Model-specific inference mappings belong in this MD file, not in config.json. Generated runners should read this section and apply the mappings with SDK helpers before create_job(). This mirrors the old microservices infer_params.py flow.

Inference mappings from TAO Core bevfusion.config.json:

ActionSpec FieldInference FunctionMeaning
dataset_convertresults_diroutput_dircurrent job results directory
evaluateencryption_keykeyencryption key
evaluateevaluate.checkpointparent_modelmodel file inferred from the parent job results folder
evaluateresults_diroutput_dircurrent job results directory
inferenceencryption_keykeyencryption key
inferenceinference.checkpointparent_modelmodel file inferred from the parent job results folder
inferenceresults_diroutput_dircurrent job results directory
trainencryption_keykeyencryption key
trainresults_diroutput_dircurrent job results directory
traintrain.pretrained_checkpointptm_if_no_resume_modelPTM when no resume checkpoint exists
traintrain.resume_training_checkpoint_pathresume_modelmodel file inferred from the current job results folder

For parent_model or parent_model_folder, pass the upstream train/export/AutoML child job id as parent_job_id. The SDK lists the parent result folder, filters checkpoint artifacts, and returns the selected model file or folder. Do not add these mappings back to config.json and do not patch generated runner scripts to guess checkpoint paths.

© 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 15 other files (references) in skills/tao-train-bevfusion of NVIDIA/skills.

  • SKILL.md
  • BENCHMARK.md
  • config/skillspector-baseline.yaml
  • evals/evals.json
  • references/skill_info.yaml
  • references/spec_template_dataset_convert.yaml
  • references/spec_template_evaluate.yaml
  • references/spec_template_inference.yaml
  • references/spec_template_train.yaml
  • schemas/dataset_convert.schema.json
  • schemas/evaluate.schema.json
  • schemas/inference.schema.json
  • schemas/manifest.json
  • schemas/train.schema.json
  • skill-card.md
  • skill.oms.sig

Open the folder on GitHubat commit dfdd080

Compare with similar skills

Tao Train Bevfusion 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 Train Bevfusion compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tao Train Bevfusion this skillNVIDIA/skills3.5k—~3.4kAutomated safety check: NotesApache-2.0
Matlab Read Write Point Cloud Filematlab/matlab-agentic-toolkit1.1k—~3.5kAutomated safety check: PassCustom licence
Matlab Use Visual Inspectionmatlab/matlab-agentic-toolkit1.1k—~3.1kAutomated safety check: PassCustom licence
Remote Sensing Research Radarlimi124/remote-sensing-research-radar143—~1.3kAutomated safety check: PassNone
Yolo Detection 2026SharpAI/DeepCamera3.1k—~1.5kAutomated safety check: PassMIT
Robot Perceptionarpitg1304/robotics-agent-skills369—~15kAutomated safety check: PassApache-2.0

Similar skills

  • Matlab Read Write Point Cloud File

    matlab/matlab-agentic-toolkit

    Read and write 3-D point cloud data using Lidar Toolbox file I/O.

    1.1k GitHub stars~3.5k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Matlab Use Visual Inspection

    matlab/matlab-agentic-toolkit

    Build machine vision inspection systems with MATLAB Visual Inspection Toolbox.

    1.1k GitHub stars~3.1k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Remote Sensing Research Radar

    limi124/remote-sensing-research-radar

    Track, retrieve, screen, and synthesize research frontiers for geospatial AI, remote sensing big data, and transferable computer vision methods.

    143 GitHub stars~1.3k tokensUpdated 5 mo ago
    Data & AnalyticsAuto-check passed
  • Yolo Detection 2026

    SharpAI/DeepCamera

    YOLO 2026 — state-of-the-art real-time object detection. An agent skill from SharpAI/DeepCamera.

    3.1k GitHub stars~1.5k tokensUpdated 22 days ago
    AI & LLM EngineeringAuto-check passed
  • Robot Perception

    arpitg1304/robotics-agent-skills

    Comprehensive best practices for robot perception systems covering cameras, LiDARs, depth sensors, IMUs, and multi-sensor setups.

    369 GitHub stars~15k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check passed
  • Matlab Process Large Images

    matlab/matlab-agentic-toolkit

    Patterns for using blockedImage to process large images, harness parallel compute for image processing, and write custom adapters.

    1.1k GitHub stars~3k tokensUpdated today
    Data & AnalyticsAuto-check passed

More from NVIDIA/skills

All 386 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.5k 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.5k GitHub stars~2.9k tokensUpdated today
    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.5k GitHub stars~4.8k tokensUpdated today
    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.5k GitHub stars~5k tokensUpdated today
    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.5k GitHub stars~4.7k tokensUpdated today
    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.5k GitHub stars~2.7k tokensUpdated today
    Auto-check: notes

Questions about Tao Train Bevfusion

What does Tao Train Bevfusion do?

BEVFusion for multi-sensor 3D object detection. An agent skill from NVIDIA/skills. Tao Train Bevfusion is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. BEVFusion for multi-sensor 3D object detection.

When should I use Tao Train Bevfusion?

Tao Train Bevfusion fits situations like: running inference for a TAO BEVFusion model; phrases include train BEVFusion; liDAR + camera fusion; BEV 3D detection.

How do I install Tao Train Bevfusion in Claude Code?

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

How do I install Tao Train Bevfusion in Codex?

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

Can I use Tao Train Bevfusion 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-train-bevfusion -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-train-bevfusion, .gemini/skills/tao-train-bevfusion, .github/skills/tao-train-bevfusion and .opencode/skills/tao-train-bevfusion in your project.

What does Tao Train Bevfusion need to run?

SKILL.md names no scripts, command-line tools or credentials: Tao Train Bevfusion is instructions for the agent only. Our summary lists: Python 3; Docker. Its frontmatter pre-approves these tools: Read, Bash. Compatibility (from SKILL.md): Requires docker + nvidia-container-toolkit..

Does Tao Train Bevfusion 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 Train Bevfusion 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. Review the folder before installing.

What licence does Tao Train Bevfusion use?

Tao Train Bevfusion 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 Train Bevfusion use?

About 3.4k tokens (SKILL.md is roughly 13k 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 5.9k tokens, read only when the agent opens those files.

What are the alternatives to Tao Train Bevfusion?

Skills that share tags, products or a category with Tao Train Bevfusion: Matlab Read Write Point Cloud File (matlab/matlab-agentic-toolkit, 1.1k stars), Matlab Use Visual Inspection (matlab/matlab-agentic-toolkit, 1.1k stars), Remote Sensing Research Radar (limi124/remote-sensing-research-radar, 143 stars) and Yolo Detection 2026 (SharpAI/DeepCamera, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tao Train Bevfusion?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,546 GitHub stars. The repository holds 386 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.