Agent skill · NVIDIA
vss-generate-video-report
Use this skill when producing a VSS analysis report — Mode A per-clip VLM, Mode B incident-range via video-analytics. Not for standalone video summarization, real-time alerts or ad-hoc Q&A.
What it needs
About 10k tokens when loaded.
What this skill does
Report Generate a video analysis report by routing to one of two backends — never via POST /generate on the VSS agent. Mode Backend --- --- A. Video clip /vss-manage-video-io-storage → clip URL → VLM chat/completions B. Incident range /vss-query-analytics → incident list → narrative report If the request is ambiguous (e.g. "report on <sensor>" with no time range and no incident wording), default to Mode A. Ask only if the user mentions both a sensor and a time range. See Examples below for the request phrasings that route to each mode. --- Instructions 1. Pick the mode — Mode A for a single recorded clip/sensor video, Mode B when the request names a time range or incidents/alerts (match against Examples). 2. Verify the deployment profile for that mode under Deployment prerequisite; hand off to /vss-deploy-profile if its probe fails. 3. Run that mode's numbered steps — Mode A or Mode B below. 4. Rewrite every user-facing clip URL with the $VSSPUBLICHOST:$VSSPUBLICPORT one-liner (Browser-playable clip URL) before embedding it in the report. 5. Return the rendered report markdown to the user. Output contract for evaluators: Mode A top title MUST be exactly # Video Analysis Report. Mode B top title MUST be exactly # Incident Range Report (never # Incident Report or sensor-named variants). Mode B MUST include ## Basic Information with the exact required rows from the template (Report Identifier, Range, Scope, Total Incidents, Confirmed / Rejected / Unverified). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/vss-generate-video-report