vss-deploy-profile

Deploy, verify, debug, and tear down NVIDIA VSS compose profiles on GPU hosts.

2|Updated Aug 20, 2026
One-click install
npx skills add https://github.com/atomicrajat/industry_safety_monitoring_system --skill vss-deploy-profile-atomicrajat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vss-deploy-profile
Source: https://github.com/atomicrajat/industry_safety_monitoring_system/tree/main/.claude/skills/vss-deploy-profile
Command: npx skills add https://github.com/atomicrajat/industry_safety_monitoring_system --skill vss-deploy-profile-atomicrajat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Deploying NVIDIA Video Search and Summarization (VSS) profiles involves dozens of interdependent decisions — profile selection, GPU sizing, LLM/VLM placement, credential gating, compose resolution, and readiness verification — where a single misstep surfaces as a 20-minute NIM cold-start failure. This Skill encodes the full deployment runbook so an agent executes the correct sequence every time. ## Core Features & Use Cases - Profile routing and sizing: Maps user intent to the base, alerts, lvs, search, warehouse, or edge profile, then applies per-profile GPU sizing tables and model placement rules (local, local_shared, remote). - Guarded deployment flow: Enforces credential validation, dry-run compose resolution, dangling depends_on normalization, NGC entitlement probes, and a human confirmation gate before docker compose up -d. - Readiness and debugging: Gates success on actual endpoint health checks rather than container start, with per-profile troubleshooting references for NIM probes, OOM tuning, and mode-specific failures. - Use Case: A user asks to deploy the VSS alerts profile on a 2-GPU RTX PRO 6000 host for real-time VLM alerting; the Skill stages perception models, writes env overrides, resolves and normalizes the compose file, deploys, and verifies the agent, RT-VLM, and alert-bridge endpoints. ## Quick Start Deploy the VSS base profile on this machine end-to-end using the vss-deploy-profile skill.

Frequently Asked Questions about vss-deploy-profile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a NVIDIA VSS profile with Docker Compose?

Copy the profile's .env to generated.env, apply env overrides, dry-run with docker compose config into resolved.yml, normalize dangling depends_on entries, then run docker compose up -d with the same env file. Success requires passing endpoint readiness checks, not just container startup.

How do I choose between local, shared, and remote LLM/VLM deployment?

Use dedicated local mode with 2+ GPUs, shared mode when one GPU fits both models within 85% of VRAM, and remote mode only when the user supplies an endpoint or local sizing cannot fit the chosen models. Never silently substitute a smaller model.

What credentials does VSS deployment require?

Local NIM pulls need NGC_CLI_API_KEY, remote NIM endpoints need NVIDIA_API_KEY, and edge recipes using gated Hugging Face models need HF_TOKEN. Credentials are validated before any env mutation to avoid failures during NIM cold starts.

Why does docker compose up start zero services for VSS?

The up command was run without --env-file pointing at generated.env, so COMPOSE_PROFILES was unset and no services were selected. Always pass the same env file used during the dry-run resolution step.

Can this skill deploy standalone VSS microservices?

No, it only deploys compose-based VSS profiles such as base, alerts, lvs, search, warehouse, and edge. Standalone microservice deployment belongs to the matching vss-deploy-* skill instead.

Why does the VSS alerts profile fail with HTTP 400 No such model?

VLM_NAME does not match the model basename that RT-VLM advertises at /v1/models. For the default Cosmos Reason3 Nano BF16 checkpoint, set VLM_NAME to nim_nvidia_cosmos3-nano-reasoner_bf16-final and keep VLM_NAME_SLUG as none.