vss-setup-video-analytics-api SKILL.md skillA
vss-setup-video-analytics-api from nvidia-ai-blueprints/video-search-and-summarization is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nvidia-ai-blueprints/video-search-and-summarization/vss-setup-video-analytics-api@v3.3.0-rc0Pins v3.3.0-rc0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nvidia-ai-blueprints/video-search-and-summarization
- Path
skills/deployment/vss-setup-video-analytics-api/SKILL.md- Versions recorded
- 5
- Latest version
- v3.3.0-rc0, committed Sep 29, 2026
- First version recorded
- Sep 1, 2026
- Size
- 10,296 bytes
- Repository stars
- 1,968
- License
- Apache-2.0
Use to deploy the vss-video-analytics-api REST service standalone with its Elasticsearch ingest-pipeline, selectable Kafka/Redis stream type, and Kafka-topic readiness gates when Kafka is selected. Not for full warehouse deploy.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Purpose
Deploy the video-analytics-api REST service standalone with the user's chosen config and data-log bind. The service exposes port 8081 and `/livez` only after Elasticsearch, the `insertion-timestamp-pipeline`, and, when `STREAM_TYPE=kafka`, the configured Kafka topic requirements are ready.
## 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/deployment/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
```
…Read the whole file at its exact version.
How to install
mdr add nvidia-ai-blueprints/video-search-and-summarization/vss-setup-video-analytics-api@sha256:820f06b1eca0b6f6The line at the top of this page pins the label v3.3.0-rc0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ecbaljkm64ayri5n)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 1, 2026 and Sep 29, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v3.3.0-rc0 latest | 2026-09-29 | 7ccc5db | 10,296 B | A | view · diff |
| v3.3.0 | 2026-09-14 | 4ac059f | 10,292 B | A | view · diff |
| v3.3.0 | 2026-09-02 | a057165 | 10,257 B | A | view · diff |
| v3.3.0 | 2026-09-02 | dbf146f | 10,290 B | A | view · diff |
| v3.3.0 | 2026-09-01 | fdf50ba | 9,625 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10296 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nvidia-ai-blueprints/video-search-and-summarization · 1,968 stars · license Apache-2.0 · pushed 2026-11-07 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_ecbaljkm64ayri5n GET https://markdownregistry.com/api/v1/resolve?ref=nvidia-ai-blueprints/video-search-and-summarization/vss-setup-video-analytics-api GET https://markdownregistry.com/api/v1/blob/820f06b1eca0b6f6c1265137840d39166f77d765dbc31ec9d63b42fe34392327
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from nvidia-ai-blueprints/video-search-and-summarization
Every file in nvidia-ai-blueprints/video-search-and-summarization