Vss Build

What it does

When your agent uses it

• The user says build vss
• Rebuild the images
• Build from source
• Build the dependencies

Example prompts

• “build vss”
• “rebuild the images”
• “build from source”
• “/vss-build”

Requirements

• A Bash shell
• Docker

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

1. 1make build TAG=dev REGISTRY_URL=... - command-line variables win over everything.
2. 2Exported shell variables (export TAG=dev).
3. 3.env at the app root, which the Makefile reads at parse time. It is

What it can do on your machine

Read from SKILL.md and the folder at commit cdf860c. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 1 file in scripts/ (Shell), which the agent can run.

  Shell commands in SKILL.md call:

  • make
  • git
  • bash
  • docker

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use git and docker, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vss Build loads about 1.9k tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 690 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~115

When it runs · the whole SKILL.md, loaded when a task matches

~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:77

  prefix (one trailing `/` normalised) | `.env` value, shipped as `intel/` |

• NoteMentions a .env fileSKILL.md:78

  /namespace segment after the registry | `.env` value, shipped empty |

• NoteMentions a .env fileSKILL.md:80

  | `TAG` | image tag | `.env` value, else `latest` |

• NoteMentions a .env fileSKILL.md:90

  3. `.env` at the app root, which the Makefile reads at parse time. It is

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from open-edge-platform/edge-ai-libraries at commit cdf860c, republished under its Apache-2.0 licence (© open-edge-platform). 690 words, ~1,859 tokens.

name

vss-build

description

Build (and optionally push) the VSS Docker images from source with `make build`, `make build-deps`, and `make push` - the application services, the dependency microservices, or both, with registry/tag, proxy, and copyleft controls. Use when the user says "build vss", "rebuild the images", "build from source", "build the dependencies", or "push the vss images". The Makefile is the source of truth for builds; there is no build.sh at the app root.

license

Apache-2.0

metadata.version

2.0.0

metadata.tags

vss build development

<!--
SPDX-FileCopyrightText: (C) 2026 Intel Corporation
SPDX-License-Identifier: Apache-2.0
-->

# SKILL_DIR is THIS skill's own directory (shown to you when the skill loads);
# in-repo it is .github/skills/vss-build. Works the same if the skill is installed standalone.
SKILL_DIR=".github/skills/vss-build"
APP_ROOT="$(bash "$SKILL_DIR/scripts/vss-bootstrap.sh")"
cd "$APP_ROOT"

make build REGISTRY_URL= PROJECT_NAME=      # → pipeline-manager:latest, …

[ -d ../../microservices ] || \
  git -C "$(git rev-parse --show-toplevel)" sparse-checkout add microservices

# Local app rebuild, then deploy:
make build
#   ! export VSS_CREDENTIALS_FILE="${XDG_CONFIG_HOME:-$HOME/.config}/vss/vss.credentials" && ./.github/skills/vss-deploy/scripts/gen-secrets.sh && source .github/skills/vss-deploy/vss.config && source "$VSS_CREDENTIALS_FILE" && source setup.sh --summary

# First-time / dependency refresh:
make build-deps && make build

# Build for a registry and push:
make build build-deps push REGISTRY_URL=registry.example.com PROJECT_NAME=vss-team TAG=v0.9.2

# Compliance build with copyleft sources, no push:
make build-deps build ADD_COPYLEFT_SOURCES=true TAG=compliance-2026-07

make list      # expected image names for the current config
docker images | grep -E 'pipeline-manager|vss-ui|video-search|video-ingestion|multimodal-|vector-retriever'

© open-edge-platform, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (scripts) in sample-applications/video-search-and-summarization/.github/skills/vss-build of open-edge-platform/edge-ai-libraries.

• SKILL.md
• BENCHMARK.md
• evals/evals.json
• example-prompts/01-local-app-rebuild.md
• example-prompts/02-first-time-with-dependencies.md
• example-prompts/03-registry-tag-push.md
• example-prompts/04-corporate-proxy-build.md
• example-prompts/05-fresh-checkout-bootstrap.md
• example-prompts/06-copyleft-sources-build.md
• example-prompts/07-bootstrap-fresh-machine.md
• example-prompts/README.md
• scripts/vss-bootstrap.sh

Open the folder on GitHubat commit cdf860c