Agent skill · Data & Analytics

vss-query-analytics

Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.

NVIDIA-AI-Blueprintsgithub.com/NVIDIA-AI-BlueprintsGitHub ↗
claude-codeNOASSERTION
Install
npx skills add NVIDIA-AI-Blueprints/video-search-and-summarization --skill vss-query-analytics --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 9 KB
Bundled scripts: none
Version: 3.2.0
Declared author: NVIDIA Video Search and Summarization team
Path: skills/vss-query-analytics/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,773 · +19 this week
Language: C++
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Purpose Answer read-only analytics questions (incidents, metrics, sensor data) by routing through the VA-MCP server. ## Prerequisites - Active VSS deployment reachable on `$HOST_IP` (see `vss-deploy-profile`). - NGC credentials in `$NGC_CLI_API_KEY` and `$NVIDIA_API_KEY` for any image pulls. - `curl`, `jq`, and Docker available on the caller. ## Instructions Follow the routing tables and step-by-step workflows below. Each section that ends in *workflow*, *quick start*, or *flow* is intended to be executed top-to-bottom. ## Examples Worked end-to-end examples are kept under `evals/` (each `*.json` manifest contains a runnable scenario) and inline in the per-workflow `curl` blocks below. Run a Tier-3 evaluation with `nv-base validate <this-skill-dir> --agent-eval` to replay them. ## Limitations - Requires the matching VSS profile / microservice to be deployed and reachable from the caller. - NGC-hosted models and NIMs may be subject to rate-limits, GPU memory requirements, and license restrictions. - Concurrency, GPU memory, and storage limits depend on the host hardware and the profile's compose file. ## Troubleshooting - **Error**: REST call returns connection refused. **Cause**

What's inside
Steps it walks through
  1. Purpose
  2. Prerequisites
  3. Instructions
  4. Examples
  5. Limitations
  6. Troubleshooting
  7. Deployment prerequisite
  8. REQUIRED: Two-Step Pattern (copy this exactly)
  9. Tool Reference
  10. videoanalyticsgetincidents
  11. videoanalyticsgetincident
  12. videoanalyticsgetsensorids
  13. videoanalyticsgetplaces
  14. videoanalyticsgetfovhistogram
Ships with 5 files
  • BENCHMARK.md
  • evals/evals.json
  • evals/query_analytics.json
  • skill-card.md
  • skill.oms.sig
Commands it runs
curl -sf --max-time 5 "http://${HOST_IP}:9901/mcp" >/dev/null 2>&1 || \
curl -sf --max-time 5 "http://${HOST_IP}:9901/" >/dev/null
Step 1: initialize — get session ID from response HEADER
Step 2: call the tool using the session ID in the header
curl -s -X POST http://${HOST_IP:-localhost}:9901/mcp \
Recent incidents (all sensors)
For a specific sensor
Confirmed (VLM-verified) only
curl -sf --max-time 5 "http://${HOST_IP:-localhost}:9901/mcp" >/dev/null
More from video-search-and-summarization
All skills →
About this skill
What does the vss-query-analytics skill do?

Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.

How do I install it?

Run `npx skills add NVIDIA-AI-Blueprints/video-search-and-summarization --skill vss-query-analytics --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.

Keep going