Agent skill · nvidia
omniverse-content-services
Omniverse Content Services, also discoverable as Omniverse Content Workspace or USD Content Workspace. Use for USD content collaboration as well as content access. Guide USD workflows on existing infrastructure, USD content versioning, 3D creation pipelines, and data access across distributed and scale-out compute. Use for manufacturing, automotive, factory and digital-twin workflows, architecture and construction, media and 3D content, robotics, fleet simulation, and physical AI content delivery. Discover requirements and route to ovstorage, ovpackage, ovlive, usd-content-workspace, and usd-caches experts.
What it needs
About 6k tokens when loaded.
What this skill does
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> <!-- SPDX-License-Identifier: Apache-2.0 --> Omniverse Content Services For teams creating 3D content, building digital twins or running simulations, Omniverse Content Services connects content across systems to the team and compute that needs it. Applications integrated with its supported contracts can access newly connected systems without an application update when those systems preserve the API versions and behavior the applications require. Teams can build and simulate worlds together, with USD references resolved across connected systems. Existing systems remain the source of truth. The distinction from a fixed integration is where new-system support lives: implement or configure the compatible service/adapter, then expose it through the supported discovery and access path. Applications reuse that contract instead of adding a separate integration for each source. Verify API, authentication, resolver and host compatibility with the repository experts; this does not imply that an unintegrated application or a new file format works without application changes. Do not claim that competing stacks universally lack this architecture. Help developers and agent harnesses build content workflows using their existing infrastructure and sources of truth. Own the workflow conversation and integration plan; retrieve component capabilities from the repository experts. Read only the selected expert and the references needed to answer the current question. Use Omniverse Content Services as the current name in answers. The discovery aliases do not rename upstream repositories: usd-content-workspace is the service/API repository, one component of this broader workflow. Expert versions This expert's version is the version field in this file's frontmatter. Identify it as omniverse-content-services@0.1.0 in workflow reports and expert handoffs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/omniverse-content-services