Agent skill · DevOps & Cloud

vss-setup-video-analytics-api

Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.

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

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

Facts
Files in the skill folder: 9
SKILL.md size: 9 KB
Bundled scripts: none
Version: 3.2.0
Declared author: NVIDIA Video Search and Summarization team
Path: skills/vss-setup-video-analytics-api/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 Deploy the video-analytics-api REST service standalone with the user's chosen config, data-log bind, and Elasticsearch / Kafka connectivity. ## 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. Detailed reference material lives in `references/`. ## Examples Worked end-to-end examples are kept under `evals/` (each `*.json` manifest contains a runnable scenario). Run a Tier-3 evaluation to replay them: ```bash nv-base validate skills/vss-setup-video-analytics-api --agent-eval ``` A minimal standalone bring-up looks like: ```bash cd $REPO/deploy/docker export VSS_APPS_DIR=$(pwd) export VSS_DATA_DIR=${VSS_DATA_DIR:-/tmp/vss-data} mkdir -p "$VSS_DATA_DIR/data_log/vss_video_analytics_api" docker compose -f services/analytics/video-analytics-api/compose.yml up -d vss-video-analytics-api curl -sf http://localhost:8081/livez ``` Follow [`references/deploy-video-analytics-api-service.md`](references/deploy-video-analytics-api-service.md) for the full workflow (config source, data-log bind, infrastructure dependencies, REST endpoints). For the field-by-fie

What's inside
Steps it walks through
  1. Purpose
  2. Instructions
  3. Examples
  4. Limitations
  5. Troubleshooting
  6. When to use
  7. Prerequisites
  8. Workflow
  9. Endpoint Reference
  10. Kafka-dependent features (runtime, requires broker)
  11. Dynamic config
  12. Dynamic calibration
  13. RTLS / AMR
  14. Routing rules
Ships with 8 files
  • BENCHMARK.md
  • evals/evals.json
  • evals/standalone_deploy.json
  • references/configuration.md
  • references/deploy-video-analytics-api-service.md
  • references/ngc-api-key-registry-login.md
  • skill-card.md
  • skill.oms.sig
Commands it runs
nv-base validate skills/vss-setup-video-analytics-api --agent-eval
cd $REPO/deploy/docker
export VSS_APPS_DIR=$(pwd)
export VSS_DATA_DIR=${VSS_DATA_DIR:-/tmp/vss-data}
mkdir -p "$VSS_DATA_DIR/data_log/vss_video_analytics_api"
docker compose -f services/analytics/video-analytics-api/compose.yml up -d vss-video-analytics-api
curl -sf http://localhost:8081/livez
More from video-search-and-summarization
All skills →
About this skill
What does the vss-setup-video-analytics-api skill do?

Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.

How do I install it?

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