deploy

Generates validated compose dry-runs and executes profile-specific deployments for VSS base, alerts, lvs, search targets.

Updated May 23, 2026
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill deploy-yo-steven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/video-search-and-summarization/deploy
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill deploy-yo-steven

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

VSS deployment failures are hard to diagnose because they often come from mismatched environment variables, stale containers, or partially applied compose configs that were never validated.

Core Features & Use Cases

  • Compose-centric, auditable deploy flow: builds env overrides, generates a resolved compose dry-run output, reviews it, then executes compose up.
  • Profile routing for VSS workloads: deploys base, alerts, lvs, and search by mapping user intent to the correct profile-specific references.
  • Debug and verification guardrails: includes pre-flight checks, endpoint reporting, and explicit debugging paths to validate the full ingestion-to-agent path.
  • Edge and hardware-aware behavior: routes GPU/VRAM requirements and supports edge-specific shared-mode constraints with HF token verification.

Quick Start

Ask the assistant to deploy the VSS base profile by running the deploy workflow end-to-end and verify it is reachable.

Frequently Asked Questions about deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely deploy VSS profiles with Docker Compose without breaking existing containers?

Deploy VSS profiles safely by generating a validated compose dry-run, checking prerequisites, and executing guarded teardowns to prevent stale container conflicts during the compose up flow.

Why does my VSS deployment fail with mismatched environment variables?

VSS deployment failures from mismatched environment variables are resolved by applying config-driven env_overrides and validating unexpanded tokens during a dry-run compose resolution before execution.

Can I deploy VSS search and alerts profiles on edge hardware with GPU constraints?

Deploy VSS search and alerts profiles on edge hardware by routing GPU and VRAM requirements, applying shared-mode constraints, and verifying HF tokens for profile-specific execution.

What is the best way to debug a partially applied VSS compose configuration?

Debug partially applied VSS compose configurations by running pre-flight checks, using explicit debugging paths, and verifying endpoint reporting to validate the full ingestion-to-agent path.

Does VSS deployment support local, remote, and local_shared execution modes?

VSS deployment supports local, remote, and local_shared execution modes across base, alerts, lvs, and search profiles by mapping user intent to the correct profile-specific references.

Do I need to verify prerequisites before running a VSS compose up flow?

Verify prerequisites before running the VSS compose up flow to ensure environment variables are expanded, GPU requirements are met, and stale container conflicts are guarded against during teardown.