Back to Skills

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.

2,741stars319forksUpdated 7/31/2026

Security Assessment

Safe(95/100)
Security Score95/100

About vss-generate-video-report

vss-generate-video-report produces analysis reports from NVIDIA's Video Search and Summarization (VSS) blueprint. It solves the problem of turning recorded video clips or time-ranged incident data into a consistently structured markdown report, routing every request to the correct backend rather than misusing the VSS agent's generic POST /generate endpoint.

The skill supports two modes. Mode A (Video clip) resolves a clip URL through the video I/O storage service and runs a VLM chat/completions call to caption or summarize a single recorded clip or sensor video. Mode B (Incident range) queries the video-analytics service for an incident list over a time range and renders a narrative incident report. It enforces strict output contracts — exact report titles and required Basic Information rows — verifies the correct deployment profile with lightweight read-only curl probes (VST/VLM reachability for Mode A, VA-MCP for Mode B), and hands off to a deploy skill when a probe fails. It carefully separates the agent-internal clip URL used for in-cluster VLM frame pulls from a rewritten browser-playable URL surfaced in the rendered report, using public host/port environment variables exported by the deploy layer.

It targets operators and engineers running the VSS blueprint who need repeatable report artifacts. Negative triggers steer ad-hoc visual Q&A, semantic archive search, read-only metrics lookup, deploy/profile changes, and real-time alert management to their dedicated skills instead.

FAQ

What are the two report modes?

Mode A reports on a single recorded video clip or sensor video via a VLM chat/completions call; Mode B reports on incidents/alerts over a named time range via the video-analytics service, rendering a narrative incident report.

What deployment prerequisites are needed?

Mode A needs the VSS base profile (VST plus a VLM NIM); Mode B needs the alerts profile (VA-MCP plus Elasticsearch). The skill runs a short curl reachability probe and hands off to the deploy skill (with user confirmation) if it fails.

How does it handle clip URLs?

It keeps the original agent-internal host:port URL for local or in-cluster VLM frame pulls, and only rewrites URLs shown in the rendered report to a browser-playable public host:port using environment variables exported by the deploy layer.

When should I not use this skill?

For ad-hoc visual Q&A, semantic archive search, read-only metrics lookups without a report, deploy/teardown/profile changes, or real-time alert management — each has a dedicated skill. Reports must never be routed through the VSS agent's POST /generate.

All Files

8 files
evals/evals.json2.6 KB
View
assets/video-analysis-report.md0.5 KB
View
SKILL.md18.2 KB
View
assets/incident-range-report.md0.7 KB
View
skill-card.md4.1 KB
View
evals/base_profile_report.json9.0 KB
View
BENCHMARK.md3.5 KB
View
skill.oms.sig5.2 KB
View

Install vss-generate-video-report

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