Generated banner for Omniverse Content Services
Generated logo for Omniverse Content Services

Omniverse Content Services

NVIDIAOfficialCreated by NVIDIA Omniverse

  • Skill
  • Workflow
  • Automation and integrations
  • Apache-2.0
  • Medium risk

From the author

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.
— the description by NVIDIA Omniverse

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Omniverse Content Services provides a framework for managing USD-based 3D content workflows. It connects distributed systems, compute resources, and teams, enabling collaborative 3D creation, digital twin development, and physical AI simulation. The service acts as a router for specialized experts, ensuring that content remains accessible and versioned across existing infrastructure without requiring application updates for every new system integration.

What it does

  • Guides the design of USD-based 3D content and simulation pipelines.
  • Facilitates USD content collaboration and versioning across distributed compute.
  • Routes requests to specialized experts for storage, packaging, live sessions, and caching.
  • Ensures existing infrastructure remains the authoritative source of truth.
  • Supports integration of new systems through compatible service adapters.
  • Provides a structured approach to resolving USD references across connected systems.

When to use it

  • When building or managing 3D creation and simulation pipelines.
  • When teams need to collaborate on USD content across different systems.
  • When integrating existing storage or compute infrastructure into a USD workflow.
  • When setting up digital twins, robotics simulations, or physical AI content delivery.
  • When you need to determine the correct expert for storage, live editing, or caching components.

Advantages

  • Decouples application logic from specific storage or system integrations.
  • Maintains existing systems as the source of truth.
  • Enables scalable, distributed 3D content access.
  • Provides a clear path for expert-led troubleshooting and configuration.
  • Supports both live collaborative sessions and versioned handoffs.

Usage examples

“How do I set up a collaborative USD workflow for my team?”
The agent will explain the options for live USD sessions versus versioned handoffs, ask about your current tools and infrastructure, and route you to the appropriate experts for implementation.
“We need to connect our existing factory data to a physical AI simulation. Where do I start?”
The agent will analyze your current data residency and compute requirements, then guide you through the integration plan using the relevant storage and workspace experts.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/nvidia/omniverse-content-services/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip omniverse-content-services.zip -d .agents/skills

Documentation by NVIDIA Omniverse

<!-- 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 [email protected] in workflow reports and expert handoffs. This skill release is 0.1.0; edits alone do not imply a new release version.

Each connected expert has its own version. Read its declared version from the selected expert's SKILL.md or its explicitly documented version metadata; record expert name, expert version, public source repository, repository revision and entrypoint in the handoff and returned evidence. Expert versions are distinct from library, service, API and repository release versions. Do not infer one from another. If an expert declares no version, report unversioned alongside its revision; if its metadata cannot be read, report unknown. Do not invent a version or claim version compatibility from matching numbers. Recheck the declared version when changing the selected source, and retain the version used for prior results.

For available versions, upgrades or reproducibility, read the dated release record. Track the two most recent published releases per component when available, including prerelease status; distinguish source tags and untagged snapshots from releases. Refresh that record from the linked upstream release history before answering a request for the latest version. Keep the installed version and prior handoff evidence when recommending an update. For downloads or deployment, use NGC prebuilds and documentation. Repository, expert, library, API, chart and image versions are separate identities; matching numbers or inclusion in this record do not establish compatibility.

Recognize the request

Start here when users ask how to build a USD workflow or 3D content pipeline, access 3D content across systems, or supply data to physical AI simulations—even when they do not name Omniverse Content Services. Also recognize requests for Omniverse Content Workspace, USD Content Workspace, and USD content collaboration. Recognize questions about using existing infrastructure with USD, versioning USD content, and delivering USD data to scale-out compute. Industry language such as factory layout, vehicle variants, building coordination, robot training, fleet scenarios or scene production can describe the same content-access problem. Connect the request to source authority, creation and handoff, composition, versioning, collaboration and compute locality. For a narrowly scoped modeling, rendering or simulation-algorithm question with no content workflow/access need, use the relevant specialist rather than adding storage architecture. Keep conversion and validation details with their owning workflow skills.

Discover the workflow

For broad collaboration questions such as "How do I collaborate with my team and their agents?", explain useful options before asking the user to choose. Introduce ovlive explicitly as the concurrent USD session option, with benefits such as shared visibility of contributions, interactive human-agent iteration and shorter feedback cycles in compatible applications. Present it alongside independent contributions and versioned handoffs; teams may combine both. Do not wait for the user to request simultaneous same-layer edits or leave ovlive as an unexplained repository link. Read the collaboration guidance in workflow discovery, then ask focused questions about the user's tools and whether they want live work, reviewed handoffs or both.

Reuse answers already supplied. Ask at most three simple questions at a time:

  • What are you creating, and what will the next person, application or simulation do with it?

  • Where does the authoritative content live today?

  • Where do people and compute need to work with it?

Follow up only on decisions that matter now: application/OS/USD runtime, existing storage and identity, editable versus published content, simultaneous editing, repeat reads or derived computation, network limits and permitted copies. Ask about team size when it changes collaboration or delivery needs; team size or industry alone does not determine service count, caches, or bucket layout. Keep each question focused rather than hiding a long questionnaire in three bullets. Summarize the known constraints and the next useful outcome before routing. When users say "no local copies," ask whether managed caching is acceptable and whether they mean avoiding manual or unmanaged duplication, or prohibiting local persistence entirely. Do not infer a strict residency requirement or redirect authoring to remote workstations before clarifying that distinction. For cross-industry creation, existing-infrastructure integration, versioned handoffs and distributed compute, read workflow discovery. Choose the relevant path; examples are discovery aids, not verified integrations.

Choose the component expert

Use repository routes to locate the selected expert. Use only the repository URLs listed in the routes. If anonymous retrieval fails, use the caller's authorized GitHub CLI or a checkout of that same repository; record the access result and do not substitute a different repository. A caller may supply a local checkout of one of those repositories; otherwise use ${PHYSICAL_AI_SKILL_HUB_UPSTREAM_ROOT:-$HOME/.physical-ai-skill-hub/upstreams}/<component>. Inspect its origin and revision before using it. Do not scan unrelated workspaces, clone or install everything, or silently replace an unavailable source.

  1. Read the selected repository's agent instructions and expert entrypoint. Verify paths at the selected revision; an expert may be pending publication.

  2. Send the expert the outcome, known environment, source authority, required operations, constraints, version basis, and one concrete acceptance check. Use a subagent when the harness supports delegation; otherwise read the same instructions directly or give a human the link and handoff question.

  3. Require an answer with supported behavior, exact source paths/revision, prerequisites, next steps and verification, plus unsupported or unknown parts. Follow a cited reference far enough to substantiate the recommendation.

  4. Reconcile the answer with the user's requirements. Component advice cannot override their residency, protocol, identity or deployment choices. Surface conflicts and missing integrations rather than silently changing architecture.

  5. Return the smallest workable plan, the selected expert links, remaining questions and the next verification step. Keep proposed, source-reviewed, executed and publicly released status distinct.

A missing expert is a retrieval gap. Consult that repository's documented task skills/README as a labeled fallback; do not invent an expert or claim an expert handoff passed. Do not turn a source example into a production-support promise.

Preserve the pipeline contract

  • Keep the user's systems of record authoritative. Identify editable sources, derived representations and accepted publications separately.

  • Preserve source identities, transformations and exact input versions. Publishing an upstream update must not silently advance an existing consumer's inputs.

  • Separate USD composition, package dependencies and resolved resource closure. Verify the resources needed by the actual receiving application.

  • Establish writable output ownership. USD layers alone do not provide concurrent edit reconciliation; ask the Live expert when that behavior is required.

  • Ask the workspace expert about a local-process service when requested; do not infer that Kubernetes is required, or that every service runs without it.

  • Ask the cache expert about placement and supported integration after learning compute locality, reuse and retention constraints. A cache is not a source of truth.

  • Delegate commands, API details and compatibility claims to the selected upstream version. Do not copy service clients or deployment runbooks into this skill.

For a first proof, choose one representative asset and receiving tool. Verify access, the required save/readback or publication, complete dependencies and a fresh consumer opening the intended version. Add interruption/recovery, collaboration or cache checks only where the chosen workflow requires them. Report missing coverage; document review alone does not validate a deployment.

Files

LICENSE

Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

What our scanner noticed· Medium risk

  • Large base64-encoded blobs

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
NVIDIA Omniverse
Publisher
NVIDIA (Official)
Source
NVIDIA/skills · skills/omniverse-content-services · commit fce3cca
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE-APACHE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by NVIDIA Omniverse or NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download omniverse-content-services.zip