What problem does it solve? Producing a consistent, structured report from NVIDIA VSS deployments requires choosing the right backend (VLM clip analysis vs. video-analytics incident queries), resolving clip URLs, and filling report templates correctly — this Skill automates that routing and rendering workflow. ## Core Features & Use Cases - Mode A — Per-clip VLM reports: Resolves a recorded clip URL via VST, calls an OpenAI-compatible VLM chat/completions endpoint (NIM Cosmos or RT-VLM), and renders a Video Analysis Report from a fixed template. - Mode B — Incident-range reports: Queries video_analytics__get_incidents through VA-MCP for a time range and sensor, tallies verdicts, and renders an Incident Range Report without calling the VLM. - Deployment-aware routing: Probes VST, VLM, and VA-MCP endpoints, hands off to deployment or storage skills when prerequisites fail, and rewrites clip URLs to browser-reachable public host/port values. - Use Case: An operator asks for a report on incidents on warehouse_safety_0001 between two timestamps; the Skill queries analytics, groups incidents by sensor, and returns a markdown report with verdict tallies and browser-playable evidence clip links. ## Quick Start Ask the agent to generate a report for a recorded sensor video or for incidents within a specific time range on a given sensor.