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.
npx skills add NVIDIA-AI-Blueprints/video-search-and-summarization --skill vss-generate-video-report --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
What does the vss-generate-video-report skill do?
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.
How do I install it?
Run `npx skills add NVIDIA-AI-Blueprints/video-search-and-summarization --skill vss-generate-video-report --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From NVIDIA-AI-Blueprints/video-search-and-summarization, a repository with 1,773 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.