[dtlindsey]

Onboarding type

• New product onboarding
• Other: publish a workflow under the existing Physical AI manual-publication registration

Summary

Publish Omniverse Content Services 0.1.0, a workflow expert for USD content collaboration, access, caching, and versioned delivery. It routes implementation questions to the public ovstorage, ovpackage, ovlive, usd-content-workspace, and usd-caches sources.

The skill directory is an exact copy of the validated, signed source snapshot 6d2b3dcab13d6fb93c8537c7dd78580112324278, merged through source PR #288. Add its directory to the existing Physical AI entry in .github/scripts/manual-components.yml so catalog regeneration retains it. No internal development tools or evaluation transcripts are included.

Release scope

• Publication requested by the owning contributor; source repository release-approval closure records the required sign-offs.
• License: Apache-2.0, preserved from the source skill.
• No new license or third-party component is introduced by this exact-copy publication.
• Existing Physical AI direct-publication exception used for the internal source repository; no automatic private-repository sync is introduced.
• Commits signed off with DCO.

Validation

• All 10 skill files are byte-for-byte identical to the signed source snapshot.
• Native catalog content-integrity check passed: all nine non-signature files match the signature manifest, with no missing files or unsigned extras.
• Independent publication-scope review found no private repository links, personal paths, usernames, credentials, or unintended files.
• git diff --check passed.
• Source central validation completed successfully before source merge. Local validation here checks content integrity, not cryptographic authenticity; catalog CI remains authoritative for its gates.

Reviewer checklist

• Confirm publication scope and release affirmations.
• Required catalog checks pass.
• Review and merge the publication PR.

[mosheabr]

Verified: skill.oms.sig chains to the NVIDIA root and all 9 signed files match (content-integrity also passes); BENCHMARK.md Overall verdict PASS with Tier 3 results; all routed repos are public; no generated files touched. require-nvskills-ci fails only because the skill was signed in its source repo before this fork PR; metadata drift is expected for the new skill.