deploy-collection

Orchestrate end-to-end deployment of Content Agents services via deploy.py.

179|21|Updated Apr 28, 2026

Search Tags:#workflow #orchestration #infrastructure #end-to-end #deploy #docker-compose #content-agents

Ready to run

npx skills add https://github.com/NVIDIA-Omniverse/content-agents --skill deploy-collection

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploy-collection
Source: https://github.com/NVIDIA-Omniverse/content-agents/tree/main/.agents/skills/deploy-collection
Command: npx skills add https://github.com/NVIDIA-Omniverse/content-agents --skill deploy-collection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates the end-to-end deployment of the Content Agents package, coordinating multiple services and optional dependencies.

Core Features & Use Cases

Orchestrates deployment plans and service startup for Material, Physics, and Texture Agents across CPU-only environments.
Supports provider-neutral deployment with optional Brev-hosted dependencies and shared OVRTX rendering.
Validates environment configuration and wires endpoint dependencies for VLM/LLM/image generation and embeddings.

Quick Start

Run the deployment plan and start the CPU-only Content Agents stack using the provided deploy.py script.

Frequently Asked Questions about deploy-collection

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

FAQPage Schema

How do I automate end-to-end deployment of Content Agents across multiple services?▼

End-to-end deployment of Content Agents is automated by orchestrating service startup, environment wiring, and plan generation through a single scripted workflow via the deploy.py script. It coordinates Material, Physics, and Texture Agents with optional shared dependencies.

Can I deploy Material, Physics, and Texture Agents together in CPU-only environments?▼

Yes, you can deploy Content Agents together or in combos across CPU-only environments. The orchestration workflow validates environment configuration and wires shared endpoint dependencies for VLM, LLM, image generation, and embeddings.

What's the best way to orchestrate Content Agents startup without using Helm?▼

The best way to orchestrate Content Agents startup without Helm is using the provided deploy.py script. It handles plan generation, environment wiring, and service startup for CPU-based deployments without requiring Helm charts.

Does the Content Agents deployment workflow support shared rendering and endpoint dependencies?▼

Yes, the deployment workflow supports shared OVRTX rendering and wires endpoint dependencies for VLM, LLM, image generation, and embeddings. It also supports provider-neutral deployment with optional Brev-hosted dependencies.

How does environment validation work during Content Agents deployment?▼

Environment validation during Content Agents deployment ensures configuration is correct before service startup. The scripted workflow validates environment variables and wires endpoint dependencies automatically as part of the deployment plan generation.

Are there limitations when deploying Content Agents without Helm on CPU-based infrastructure?▼

The deployment workflow is designed specifically for CPU-based deployments without Helm. It orchestrates end-to-end deployment across multiple services but does not address GPU-based deployments or Helm-managed Kubernetes environments.