Back to Skills

vss-deploy-detection-tracking-2d

Use this skill when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice. Trigger when the user says things like 'deploy rtvi-cv', 'start warehouse 2d', 'add a stream', 'check rtvi-cv health', or 'stop the perception container'. Not for VLM, embedding, or analytics — use the matching vss-* skill.

2,759stars321forksUpdated 8/1/2026

Security Assessment

Safe(91/100)
Security Score91/100

About vss-deploy-detection-tracking-2d

This NVIDIA skill deploys, operates, debugs, tears down, and drives the REST API of the RTVI-CV 2D detection and tracking microservice, part of the Video Search and Summarization (VSS) blueprint built on DeepStream and Metropolis. It solves the operational problem of bringing up a real-time perception container (warehouse or smart-city use cases, with backends such as GDINO, RT-DETR, and Sparse4D), configuring its pipeline, managing streams, and checking its health and metrics. It unifies two action surfaces in one skill: deploy/operate/debug/teardown of the container, and calling its REST API on a running instance.

The skill uses action routing to pick a single flow per invocation and delegates detail to references and helper scripts (invoked via run_script). A representative configuration workflow copies helper scripts into the running container and applies pipeline settings in one chained call, using docker exec, docker cp, and a scoped rm -rf of a temporary /tmp/scripts directory inside the container to make the copy deterministic; this cleanup is confined to a container-local temp path, not the host. It documents structured output markers to parse, engine-cache handling, batch-size and output-sink updates, and a precise required format for rendering configuration exit boxes. Prerequisites include an active VSS deployment, NGC credentials in NGC_CLI_API_KEY and NVIDIA_API_KEY for image pulls, and curl/jq/Docker. It is Apache-2.0 licensed with published evaluation results.

It targets DevOps and perception engineers running NVIDIA video-analytics pipelines. Use cases include deploying a warehouse or smart-city perception app, adding or removing streams, checking rtvi-cv health, updating batch size or output sink, and tearing the container down. It performs standard Docker/NGC deployment operations with official tooling, not offensive or destructive host-level actions.

FAQ

What does the RTVI-CV service do?

It runs real-time 2D object detection and tracking on video streams via a DeepStream/Metropolis perception pipeline, supporting warehouse and smart-city use cases with backends like GDINO, RT-DETR, and Sparse4D.

What can this skill do beyond deployment?

It also operates, debugs, and tears down the container and calls its REST API (stream add/remove, health via /live, /ready, /startup, metrics, and embeddings) on a running instance at port 9000.

What are the prerequisites?

An active VSS deployment reachable on the host IP, NGC credentials in NGC_CLI_API_KEY and NVIDIA_API_KEY for image pulls, and curl, jq, and Docker available on the caller.

Is the rm -rf in the config workflow dangerous?

No. It removes a temporary /tmp/scripts directory inside the target container to make a subsequent docker cp deterministic across sessions; it is scoped to a container-local temp path, not the host filesystem.

When should I use a different skill?

This skill is for the 2D detection/tracking (RTVI-CV) microservice only. For VLM, embedding, or analytics services, use the matching vss-* skill, and for full VSS profiles use vss-deploy-profile.

All Files

51 files
scripts/common.sh14.3 KB
View
scripts/prelaunch_nvinfer_engine.sh8.5 KB
View
scripts/setup_sparse4d.sh9.1 KB
View
scripts/update_batch_size.sh6.5 KB
View
assets/deploy-defaults.yml9.1 KB
View
evals/deploy-evals.json3.5 KB
View
references/apply-config.md59.0 KB
View
references/next-steps.md25.4 KB
View
references/pipeline-config.md11.1 KB
View
references/task-list.md12.8 KB
View
references/usage-vss-detection-tracking-2d.md14.8 KB
View
scripts/add_streams.sh8.5 KB
View
scripts/calibration_manager.py9.8 KB
View
evals/usage-evals.json12.6 KB
View
references/resource-plan.md18.8 KB
View
references/troubleshooting.md8.0 KB
View
references/ux-conventions.md13.7 KB
View
scripts/apply_in_container.sh2.9 KB
View
scripts/clean_engine_cache.sh2.9 KB
View
scripts/fetch_resources.sh10.1 KB
View
scripts/run_app_and_wait.sh14.1 KB
View
scripts/start_app_in_container.sh6.0 KB
View
scripts/update_stream_sources.sh6.5 KB
View
skill.oms.sig15.3 KB
View
references/api-reference.md8.3 KB
View
references/deploy-vss-detection-tracking-2d.md59.2 KB
View
references/ngc-setup.md6.8 KB
View
references/start-app.md25.8 KB
View
references/upgrade-rollback.md2.3 KB
View
references/workflow-reference.md10.1 KB
View
scripts/cache_nvinfer_engine.sh4.3 KB
View
scripts/collect_metrics.sh13.9 KB
View
scripts/load_defaults.sh5.1 KB
View
scripts/setup_gdino.sh6.4 KB
View
scripts/synthesize_docker_run.sh7.2 KB
View
scripts/write_deployment_log.sh11.1 KB
View
BENCHMARK.md3.5 KB
View
evals/evals.json2.0 KB
View
references/container-reuse.md10.9 KB
View
references/environment.md6.4 KB
View
references/platforms.md7.1 KB
View
references/teardown-flow.md5.9 KB
View
references/usecases.md13.7 KB
View
scripts/apply_config.sh22.1 KB
View
scripts/check_container_gpu.sh3.1 KB
View
scripts/discover_streams.sh8.0 KB
View
scripts/render_box.sh2.3 KB
View
scripts/setup_tracker_reid.sh11.3 KB
View
scripts/update_output_sink.sh16.5 KB
View
SKILL.md17.5 KB
View
skill-card.md4.2 KB
View

Install vss-deploy-detection-tracking-2d

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

nvidia/skills