{
  "skills": [
    "vss-deploy-profile"
  ],
  "resources": {
    "platforms": {
      "RTXPRO6000BW": {
        "gpu_count": 2
      }
    }
  },
  "env": "Multi-GPU host matching `{{platform}}` with Docker + NVIDIA container toolkit + `NGC_CLI_API_KEY`. Remote LLM/VLM endpoint env vars (`LLM_REMOTE_URL`/`LLM_REMOTE_MODEL`, `VLM_REMOTE_URL`/`VLM_REMOTE_MODEL`) may also be set. The **alerts-verification (CV)** mode (`vss-deploy-profile -m verification`) runs RT-CV perception locally on one dedicated GPU to generate candidate alerts upstream, and the VLM reviews each candidate to reduce false positives. The adapter selects this variant for `alerts_cv` evaluations. See `skills/vss-deploy-profile/references/alerts.md` § *Two Modes*.",
  "expects": [
    {
      "query": "Deploy the VSS **alerts** profile on {{platform}} for CV-driven alert generation with VLM-as-verifier. Run end-to-end and autonomously.",
      "checks": [
        "`curl -sf --max-time 15 http://localhost:8000/docs` returns exit 0 (Agent REST API responsive)",
        "`docker ps --format '{{.Names}}' | grep -qx vss-agent` returns exit 0 (Agent backend)",
        "`docker ps --format '{{.Names}}' | grep -qx redis` returns exit 0 (shared message bus)",
        "`docker ps --format '{{.Names}}' | grep -qx vss-rtvi-cv` returns exit 0 (RT-CV perception — the 'CV' in this mode)",
        "`docker ps --format '{{.Names}}' | grep -qx vss-behavior-analytics` returns exit 0 (rule-based alert generation on CV output)",
        "`docker ps --format '{{.Names}}' | grep -qx vss-alert-bridge` returns exit 0 (routes CV-generated alerts to VLM verifier)",
        "`docker ps --format '{{.Names}}' | grep -qx vss-vios-nvstreamer` returns exit 0 (video ingestion source)"
      ]
    }
  ]
}