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.
Security Assessment
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 filesInstall vss-deploy-detection-tracking-2d
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
nvidia/skills