vss-deploy-warehouse-helm SKILL.md skillA
vss-deploy-warehouse-helm 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-deploy-warehouse-helm@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-deploy-warehouse-helm/SKILL.md- Versions recorded
- 5
- Latest version
- v3.3.0-rc0, committed Sep 29, 2026
- First version recorded
- Sep 1, 2026
- Size
- 16,728 bytes
- Repository stars
- 1,968
- License
- Apache-2.0
Use when the user asks to deploy, upgrade, or size the VSS warehouse blueprint (2D / 3D / MV3DT) on Kubernetes via Helm — as opposed to Docker Compose, which is covered by vss-build-vision-ai's warehouse reference. Handles GPU-aware NUM_STREAMS capping so the deployment matches what the perception pipeline can actually sustain.
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
# VSS Warehouse — Helm Deploy ## When to Use - Deploy, upgrade, or size the VSS warehouse blueprint (2D / 3D / MV3DT) on Kubernetes via Helm - Compute a GPU-aware `NUM_STREAMS` cap for a warehouse Helm install so it matches what the perception pipeline can sustain Do not use this skill for: - Docker Compose warehouse deployment — use `vss-build-vision-ai`'s [`references/warehouse.md`](../../vss-build-vision-ai/references/profiles/warehouse.md); it owns the `HARDWARE_PROFILE` → GPU mapping table and the `blueprint_config.yml` stream-cap semantics this skill reuses. - Non-warehouse Helm profiles (`base`, `search`, `lvs`, `alerts`) — those don't have a `bp-configurator` GPU-aware stream cap; deploy them per their own chart READMEs. - Runtime operations (adding cameras, querying behavior analytics) — use `vss-manage-alerts` / `vss-query-analytics` against the running deployment. ## Why this exists Docker Compose's warehouse deploy caps `NUM_STREAMS` per GPU automatically: the configurator reads `deploy/docker/industry-profiles/warehouse-operations/blueprint-configurator/blueprint_config.yml`'s …
Read the whole file at its exact version.
How to install
mdr add nvidia-ai-blueprints/video-search-and-summarization/vss-deploy-warehouse-helm@sha256:6af968e953b64ce4The 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_3f7kvfessijpfgjt)
2 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 | 16,728 B | A | view · diff |
| v1.0.0 | 2026-09-28 | 4e29ded | 16,724 B | A | view · diff |
| v1.0.0 | 2026-09-14 | 4ac059f | 16,487 B | A | view · diff |
| v1.0.0 | 2026-09-02 | 485bdd2 | 16,489 B | A | view · diff |
| v1.0.0 | 2026-09-01 | d43fd15 | 15,468 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 (16728 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_3f7kvfessijpfgjt GET https://markdownregistry.com/api/v1/resolve?ref=nvidia-ai-blueprints/video-search-and-summarization/vss-deploy-warehouse-helm GET https://markdownregistry.com/api/v1/blob/6af968e953b64ce45495bf96ef6de0a21dd64f7a8213b32963ac5eacdd4cce2f
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