deploy-physics-agent-brev

Deploy or smoke-test the Physics Agent with Brev-hosted endpoints.

179|21|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/NVIDIA-Omniverse/content-agents --skill deploy-physics-agent-brev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-physics-agent-brev
Source: https://github.com/NVIDIA-Omniverse/content-agents/tree/main/.agents/skills/deploy-physics-agent-brev
Command: npx skills add https://github.com/NVIDIA-Omniverse/content-agents --skill deploy-physics-agent-brev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploys or smoke-tests the Physics Agent using Brev-hosted OVRTX rendering and VLM endpoints, enabling quick validation of the hybrid workflow.

Core Features & Use Cases

  • Brev-driven deployment and smoke-testing workflow for the Physics Agent including remote render and VLM coordination.
  • Guided setup and execution of the Brev render and VLM nodes with necessary environment configuration and cleanup safeguards.
  • Local USD validation integration and reusable smoke-test scenarios to verify end-to-end pipeline health.

Quick Start

Select the deploy-physics-agent-brev skill and follow the prompts to configure Brev endpoints, launch render and VLM tests, and perform cleanup.

Frequently Asked Questions about deploy-physics-agent-brev

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

FAQPage Schema
How do I deploy and smoke-test a physics agent using Brev endpoints?

To deploy and smoke-test a physics agent with Brev endpoints, select the deploy-physics-agent-brev skill and follow the guided prompts to configure Brev CLI access, launch remote render and VLM nodes, and execute local USD validation workflows.

What is a credit-conscious hybrid path for local rendering and VLM testing?

A credit-conscious hybrid path for local rendering and VLM testing splits workloads between local USD validation and remote Brev-hosted render and VLM nodes, optimizing resource usage while validating the end-to-end physics agent pipeline.

Do I need Brev CLI access to run the Physics Agent deployment workflow?

Yes, Brev CLI access is a required prerequisite. The deployment workflow depends on Brev-hosted OVRTX rendering and VLM endpoints, which are configured and launched through the Brev CLI environment.

How does local USD validation integrate with remote Brev render and VLM nodes?

Local USD validation integrates with remote Brev nodes by running reusable smoke-test scenarios that verify end-to-end pipeline health, coordinating local USD checks with remote render and VLM execution before applying cleanup safeguards.

What's the best way to verify end-to-end pipeline health for a Physics Agent?

The best way to verify pipeline health is using guided smoke-test scenarios that coordinate Brev render and VLM nodes with local USD validation, ensuring the full hybrid workflow is tested before cleanup.