diff --git a/.github/scripts/manual-components.yml b/.github/scripts/manual-components.yml
index 577067438..9aac25a2e 100644
--- a/.github/scripts/manual-components.yml
+++ b/.github/scripts/manual-components.yml
@@ -20,6 +20,7 @@ components:
       - isaac-humanoid-cloud-control
       - isaac-mission-control-showcase
       - omniverse-cad-to-simready
+      - omniverse-content-services
       - omniverse-realtime-viewer
       - omniverse-usd-performance-tuning
       - physical-ai-infrastructure-setup-and-resilient-scaling
diff --git a/skills/omniverse-content-services/BENCHMARK.md b/skills/omniverse-content-services/BENCHMARK.md
new file mode 100644
index 000000000..2277f6dac
--- /dev/null
+++ b/skills/omniverse-content-services/BENCHMARK.md
@@ -0,0 +1,139 @@
+# Skill Benchmark: omniverse-content-services
+
+> ✅ **Overall verdict: PASS — Recommended for publication**
+
+## Publication Recommendation
+
+Recommended for publication based on the completed evaluation evidence in this report.
+
+## Evaluation Metadata
+
+- Skill: `omniverse-content-services`
+- Evaluation date: 2026-10-24
+- Evaluator version: `1.5.6`
+- Agents: Claude Code (`aws/anthropic/bedrock-claude-opus-5-5`), Codex (`openai/openai/gpt-6.1-sol`)
+- Tasks: 10 evaluation tasks (8 positive, 2 negative)
+- Dataset digest: `sha256:26ba432fafb9b59ca9f07418d47b8d52deb447fa024755733b0bc0958056faa1` (skill-evaluator-dataset-snapshot/1)
+- Attempts per task: 1
+- Environment: `k8s-sandbox`
+- Tier 2 evidence: required for publication
+- Tier 3 evidence: required for publication
+
+Each task attempt ran in its own isolated sandbox pod.
+
+## What This Report Answers
+
+The three-tier evaluation checks whether the skill:
+
+- is safe to use;
+- produces correct answers;
+- is discovered and activated when needed;
+- helps the agent complete the user's goal and expected workflow; and
+- avoids wasted skill and tool usage.
+
+## Results at a Glance
+
+| Measure | Claude Code (Baseline → Skill Uplift) | Codex (Baseline → Skill Uplift) |
+|---|---:|---:|
+| Overall | 88.2% — baseline ran, but no comparable score was available; uplift unavailable | 80.0% — baseline ran, but no comparable score was available; uplift unavailable |
+| Security | 100.0% → 85.0% (-15.0 points) | 100.0% → 85.0% (-15.0 points) |
+| Correctness | 64.0% → 100.0% (+36.0 points) | 74.0% → 92.0% (+18.0 points) |
+| Discoverability | 95.0% — baseline ran, but no comparable score was available; uplift unavailable | 83.1% — baseline ran, but no comparable score was available; uplift unavailable |
+| Effectiveness | 45.3% → 86.3% (+41.0 points) | 50.7% → 69.4% (+18.7 points) |
+| Efficiency | 74.6% — baseline ran, but no comparable score was available; uplift unavailable | 70.4% — baseline ran, but no comparable score was available; uplift unavailable |
+
+**How to read this table:** baseline is the same task attempted without the target skill. Scores are rounded to one decimal; threshold-adjacent values use additional precision so their displayed band matches the verdict. Uplift is derived from those displayed scores and shown in percentage points.
+
+Example: `47.0% → 92.0% (+45.0 points)` means the skill-assisted run scored 92.0%, 45.0 percentage points above its 47.0% no-skill baseline.
+
+A partial dimension was calculated from only the available configured signals; review the detailed report before relying on it.
+
+## Token Usage
+
+Actual Tier 3 execution usage is reported for every observed agent/case pair and both conditions.
+
+| Agent | Dataset case | With skill | Without skill | Delta | Change | Coverage |
+|---|---|---:|---:|---:|---:|---|
+| claude-code | All cases | 10,464,332 | 3,148,814 | +7,315,518 | +232.33% | skill 10/10; base 10/10 |
+| claude-code | clarify-local-caching | 427,742 | 64,136 | +363,606 | +566.93% | skill 1/1; base 1/1 |
+| claude-code | custom-backend-contract | 1,824,221 | 1,901,998 | -77,777 | -4.09% | skill 1/1; base 1/1 |
+| claude-code | existing-systems-to-simulation | 269,967 | 94,200 | +175,767 | +186.59% | skill 1/1; base 1/1 |
+| claude-code | local-versioned-storage-handoff | 751,580 | 333,593 | +417,987 | +125.30% | skill 1/1; base 1/1 |
+| claude-code | mesh-modeling-negative | 30,666 | 30,902 | -236 | -0.76% | skill 1/1; base 1/1 |
+| claude-code | prebuilds-and-cache-routing | 229,340 | 156,269 | +73,071 | +46.76% | skill 1/1; base 1/1 |
+| claude-code | reproducible-package-inputs | 6,691,988 | 125,688 | +6,566,300 | +5224.29% | skill 1/1; base 1/1 |
+| claude-code | simulation-algorithm-negative | 33,265 | 62,133 | -28,868 | -46.46% | skill 1/1; base 1/1 |
+| claude-code | team-and-agent-collaboration | 104,514 | 132,460 | -27,946 | -21.10% | skill 1/1; base 1/1 |
+| claude-code | version-and-source-identities | 101,049 | 247,435 | -146,386 | -59.16% | skill 1/1; base 1/1 |
+| codex | All cases | 1,182,435 | 454,263 | +728,172 | +160.30% | skill 10/10; base 10/10 |
+| codex | clarify-local-caching | 65,611 | 30,866 | +34,745 | +112.57% | skill 1/1; base 1/1 |
+| codex | custom-backend-contract | 560,062 | 63,834 | +496,228 | +777.37% | skill 1/1; base 1/1 |
+| codex | existing-systems-to-simulation | 68,189 | 30,618 | +37,571 | +122.71% | skill 1/1; base 1/1 |
+| codex | local-versioned-storage-handoff | 171,438 | 53,572 | +117,866 | +220.01% | skill 1/1; base 1/1 |
+| codex | mesh-modeling-negative | 13,652 | 13,506 | +146 | +1.08% | skill 1/1; base 1/1 |
+| codex | prebuilds-and-cache-routing | 86,091 | 71,553 | +14,538 | +20.32% | skill 1/1; base 1/1 |
+| codex | reproducible-package-inputs | 120,259 | 127,091 | -6,832 | -5.38% | skill 1/1; base 1/1 |
+| codex | simulation-algorithm-negative | 22,617 | 22,750 | -133 | -0.58% | skill 1/1; base 1/1 |
+| codex | team-and-agent-collaboration | 60,615 | 26,904 | +33,711 | +125.30% | skill 1/1; base 1/1 |
+| codex | version-and-source-identities | 13,901 | 13,569 | +332 | +2.45% | skill 1/1; base 1/1 |
+| ALL AGENTS | Dataset aggregate | 11,646,767 | 3,603,077 | +8,043,690 | +223.25% | skill 20/20; base 20/20 |
+
+Prompt tokens include cached reads, so total tokens are `prompt + completion` (cached is not added twice). The Efficiency score uses `(prompt - cached) + completion`. N/A means the relevant trajectory counters were not available; coverage is never estimated.
+
+## Tier Status
+
+| Tier | Purpose | Status | Evidence |
+|---|---|---|---|
+| Tier 1 | Static validation | **PASSED WITH OBSERVATIONS** | 11 validator(s); 18 finding(s) |
+| Tier 2 | Semantic deduplication | **PASSED** | 2 validator(s); 0 finding(s) |
+| Tier 3 | Live agent evaluation | **PASS** | 2 agent(s); 10 task(s) |
+
+## Findings and Observations
+
+<details>
+<summary>Show detailed findings and successful checks</summary>
+
+- **MEDIUM** QUALITY/quality_efficiency: Deeply nested references in prebuilt-artifacts.md (`skills/omniverse-content-services/SKILL.md`)
+- **MEDIUM** SCHEMA/frontmatter_field_placement: Root field 'version' is ignored; use 'metadata.version' (`skills/omniverse-content-services/SKILL.md`)
+- **MEDIUM** SCHEMA/body_recommended_section: Missing recommended section: '## Instructions' (`skills/omniverse-content-services/SKILL.md`)
+- **MEDIUM** SCHEMA/body_recommended_section: Missing recommended section: '## Examples' (`skills/omniverse-content-services/SKILL.md`)
+- **MEDIUM** SECURITY/Skill Enumeration (AS3): Agent Snooping: skills/ovstorage-expert/SKILL.md (`references/repositories.md:17`)
+- 13 additional finding(s) are available in the full evaluation artifacts.
+
+</details>
+
+## Scoring Methodology
+
+<details>
+<summary>Show dimension definitions, source signals, and thresholds</summary>
+
+| Dimension | Question | Scored signals |
+|---|---|---|
+| Security | Is it safe to use? | `security` (100%) |
+| Correctness | Is the answer correct? | `accuracy` (100%) |
+| Discoverability | Was the right skill loaded when needed? | `skill_execution` (100%) |
+| Effectiveness | Did the skill help complete the task? | `goal_accuracy` (50%) + `behavior_check` (50%) |
+| Efficiency | Did it avoid wasted tool calls and token usage? | `skill_efficiency` (50%) + `token_efficiency` (50%) |
+
+- Dimension bands: PASS at 50% or above; NEUTRAL from 40% to below 50%; FAIL below 40%.
+- Overall Tier 3 lift: PASS at +5 points or more; FAIL at -10 points or less; values between those bands are NEUTRAL.
+- Overall verdict: PASS only when every configured dimension passes for at least one supported agent. Lift is reported as diagnostic evidence and does not override this gate.
+- The 50% attempt pass threshold is a separate per-task gate; it is not the dimension pass threshold.
+- Effectiveness is the equal-weight mean of goal completion (`goal_accuracy`) and expected workflow adherence (`behavior_check`).
+- Efficiency is 50% tool-call productivity (the backward-compatible `skill_efficiency` wire id) and 50% `token_efficiency`. Positive-case skill routing is scored under Discoverability, not Efficiency; a negative case without a routing target is N/A. N/A sources are omitted, remaining weights are renormalized, and the dimension is marked partial.
+
+Signals present in this run:
+
+- `security` (Security): unsafe operations, secret leakage, and unauthorized access.
+- `skill_execution` (Skill Execution): whether the expected skill was selected, decoys were avoided, and the workflow executed.
+- `skill_efficiency` (Tool Productivity): tool-call productivity (legacy wire id; routing is scored under Discoverability).
+- `accuracy` (Accuracy): final-answer correctness against the reference answer.
+- `goal_accuracy` (Goal Accuracy): whether the user's goal was achieved.
+- `behavior_check` (Behavior Check): whether the expected workflow behavior was followed.
+- `token_efficiency` (Token Efficiency): actual uncached prompt plus completion usage (50% of Efficiency).
+
+</details>
+
+## Freshness
+
+Regenerate this benchmark when the skill, evaluation dataset, target agent/model, evaluator version, environment, or scoring policy changes.
diff --git a/skills/omniverse-content-services/README.md b/skills/omniverse-content-services/README.md
new file mode 100644
index 000000000..3e891e7cb
--- /dev/null
+++ b/skills/omniverse-content-services/README.md
@@ -0,0 +1,59 @@
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
+# Omniverse Content Services
+
+Version: **0.1.0**
+
+A workflow expert for USD content collaboration, 3D content pipelines, and
+physical AI simulation data access. It helps identify source systems, authoring
+and compute locations, collaboration needs, and permitted caching, then routes
+implementation questions to the appropriate repository expert. Existing systems
+remain the source of truth.
+
+Use it for manufacturing and factory planning, automotive configurations,
+architecture and construction, digital twins, media and 3D asset creation,
+robotics, and fleet simulation. It connects these tasks to common questions:
+how to use existing infrastructure with USD, create and publish content versions,
+coordinate contributions, and deliver consistent inputs to scale-out compute.
+
+## Use the expert
+
+Load [SKILL.md](SKILL.md) in your agent harness, or ask:
+
+> Use Omniverse Content Services to design a content pipeline from our existing
+> storage to our authoring applications and simulation workers.
+
+Other starting questions:
+
+- How can our factory team use CAD and existing storage in a USD workflow?
+- How do we version a vehicle or building scene without silently changing downstream inputs?
+- How can robot or fleet simulation workers reuse the right USD assets across sites?
+
+The expert also recognizes Omniverse Content Workspace, USD Content Workspace,
+and USD content collaboration as discovery phrases.
+
+## Public components
+
+| Repository | Role |
+| --- | --- |
+| [ovstorage](https://github.com/nvidia-omniverse/ovstorage) | Content access, authentication, and USD resolution |
+| [usd-caches](https://github.com/nvidia-omniverse/usd-caches) | Source-content and derived-data caching |
+| [usd-content-workspace](https://github.com/nvidia-omniverse/usd-content-workspace/tree/release/v0.1.0) | Service contracts, adapters, and deployment workflows from `release/v0.1.0` |
+| [ovlive](https://github.com/nvidia-omniverse/ovlive) | Concurrent USD collaboration |
+| [ovpackage](https://github.com/nvidia-omniverse/ovpackage) | Versioned publication and package dependencies |
+
+See [repository routes](references/repositories.md) for expert discovery and
+[workflow discovery](references/workflow-discovery.md) for qualification questions
+and first-proof criteria. Repository routes are not compatibility guarantees:
+verify availability, source revisions, and application support before execution.
+
+The dated [release record](references/releases.md) tracks the latest two published
+releases where available, source-only tags, and each connected expert's version
+status. See [NGC prebuilds and documentation](references/prebuilt-artifacts.md) for
+service images, Helm charts, cache packages and their owning guides. This workflow
+expert remains **0.1.0**; component versions advance independently.
+
+The expert distinguishes proposed designs, source-reviewed capabilities, and
+runtime validation. It does not replace the component experts or claim that an
+untested deployment is ready for production.
diff --git a/skills/omniverse-content-services/SKILL.md b/skills/omniverse-content-services/SKILL.md
new file mode 100644
index 000000000..479f363bc
--- /dev/null
+++ b/skills/omniverse-content-services/SKILL.md
@@ -0,0 +1,180 @@
+---
+name: omniverse-content-services
+description: >-
+  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.
+version: "0.1.0"
+license: Apache-2.0
+tools: [Read, Shell, Write]
+metadata:
+  author: NVIDIA Omniverse
+  tags: [omniverse, usd, 3d, content-pipelines, content-access, physical-ai, simulation, digital-twins, storage]
+  domain: content-workflows
+---
+
+<!-- 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.
+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](references/releases.md). 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](references/prebuilt-artifacts.md).
+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](references/workflow-discovery.md), 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](references/workflow-discovery.md).
+Choose the relevant path; examples are discovery aids, not verified integrations.
+
+## Choose the component expert
+
+Use [repository routes](references/repositories.md) 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.
diff --git a/skills/omniverse-content-services/evals/evals.json b/skills/omniverse-content-services/evals/evals.json
new file mode 100644
index 000000000..8a7e7de40
--- /dev/null
+++ b/skills/omniverse-content-services/evals/evals.json
@@ -0,0 +1,133 @@
+{
+  "skill_name": "omniverse-content-services",
+  "evals": [
+    {
+      "id": "existing-systems-to-simulation",
+      "prompt": "Our factory team has CAD assemblies, architectural models and robot scenes across an asset system, a file share and object storage. We want people and simulation workers to use this content while each existing system remains authoritative. What workflow should we explore first? Give advice only; do not install or change anything.",
+      "expected_output": "A focused content-access workflow that preserves the existing systems, distinguishes source conversion from delivery, selects the appropriate component owners, and proposes one representative asset-to-consumer proof before scaling.",
+      "files": [],
+      "assertions": [
+        "Selects omniverse-content-services for the content-access and pipeline coordination request.",
+        "Keeps the existing systems authoritative and distinguishes editable sources from derived or published simulation inputs.",
+        "Routes client access and USD resolution to ovstorage and service contracts or adapters to usd-content-workspace without claiming ready-made support for every asset system or native format.",
+        "Asks at most three focused initial questions about the intended consumer, source access or compute locality, and proposes opening one representative asset with its dependencies in the receiving tool.",
+        "Provides advice without installing services, modifying source assets or claiming a deployment has been tested."
+      ]
+    },
+    {
+      "id": "team-and-agent-collaboration",
+      "prompt": "How can my team and their agents collaborate on USD content? We have not decided whether to work live or exchange reviewed contributions. Explain the options before asking us to choose; do not deploy anything.",
+      "expected_output": "An explanation of live USD sessions with ovlive, independent contributions with versioned handoffs, and a combination of both, with concrete benefits and a small number of application and workflow questions.",
+      "files": [],
+      "assertions": [
+        "Introduces ovlive by name as a live USD session option before requiring the user to request same-layer editing.",
+        "Explains shared visibility of contributions and interactive human-agent feedback as benefits.",
+        "Offers reviewed versioned handoffs alongside live work and explains that accepted simulation inputs can stay pinned while editing continues.",
+        "Qualifies application and client integration rather than promising automatic conflict-free editing in every tool.",
+        "Asks at most three simple follow-up questions and does not start a service."
+      ]
+    },
+    {
+      "id": "clarify-local-caching",
+      "prompt": "Our remote artists work on home GPUs against a central content store. We do not want local copies because unmanaged downloads become stale and are hard to remove. We have no remote GPU workstations. How should we approach content access? Give a recommendation, not a deployment.",
+      "expected_output": "A clarification of managed caching versus unmanaged duplication, followed by an appropriate access/cache handoff that preserves the central source of truth without assuming that remote authoring is required.",
+      "files": [],
+      "assertions": [
+        "Asks whether managed local caching is acceptable instead of interpreting no local copies as an absolute ban on local persistence.",
+        "Distinguishes disposable read caches from writable working files, autosaves and offline replicas.",
+        "Routes cache placement and retention questions to usd-caches and client access to ovstorage, while keeping the central store authoritative.",
+        "Does not prescribe remote GPU workstations or promise that direct network access prevents every application from persisting data.",
+        "Does not choose cache or bucket counts from team size alone."
+      ]
+    },
+    {
+      "id": "reproducible-package-inputs",
+      "prompt": "I want simulation jobs to keep using an accepted USD asset version while artists continue editing. Will package versioning automatically find every referenced texture, deduplicate changed blocks of large files, and move existing jobs to the newest asset? Explain how to verify the workflow without running it.",
+      "expected_output": "A versioned-publication workflow using ovpackage, with explicit input versions and adoption of updates, separate verification of dependency closure and storage behavior, and a fresh-consumer check.",
+      "files": [],
+      "assertions": [
+        "Routes exact package publications and dependencies to ovpackage and distinguishes them from file history or live sessions.",
+        "Keeps existing jobs pinned to accepted inputs and treats adoption of a new asset version as an explicit decision.",
+        "Does not assume that package dependency declarations prove closure of every USD reference, texture or other required resource.",
+        "Does not infer block-level deduplication from package versioning.",
+        "Proposes reopening the exact accepted scene on a fresh consumer after an upstream change, with complete dependencies, without claiming the check ran."
+      ]
+    },
+    {
+      "id": "local-versioned-storage-handoff",
+      "prompt": "Use Omniverse Content Services to advise on versioned storage on one Linux workstation. My existing folders must remain authoritative, and I do not want Kubernetes. I have not decided whether applications must edit those folders directly or use a managed store. What should we establish and test first? Do not install or write anything.",
+      "expected_output": "A local-process handoff to the workspace expert that preserves the requested architecture, clarifies managed storage versus direct folder edits, separates examples from deployable implementations, and proposes a disposable version-readback proof.",
+      "files": [],
+      "assertions": [
+        "Honors the no-Kubernetes constraint and routes service implementation questions to usd-content-workspace on release/v0.1.0.",
+        "Asks whether a managed store is acceptable or ordinary folders must remain directly editable, without deciding that architecture for the user.",
+        "Preserves the existing content and does not initialize a managed backend over the source folders.",
+        "Distinguishes verified upstream implementations, examples and build recipes, or reports an evidence gap instead of asserting that a complete durable local service is already available.",
+        "Proposes a disposable write, update, exact old-version read and restart/fresh-consumer check; performs no installation or writes."
+      ]
+    },
+    {
+      "id": "custom-backend-contract",
+      "prompt": "We want an Omniverse-compatible service for our on-prem object store with read, write and file history. We do not yet know whether its S3 interface is enabled or whether other applications will keep writing directly. What should we verify before choosing an adapter? Give a source-backed investigation path, not implementation code.",
+      "expected_output": "A bounded investigation routed to the workspace service expert and ovstorage client expert, preserving the backend and distinguishing protocol, versioning, direct-writer behavior, conformance and actual application validation.",
+      "files": [],
+      "assertions": [
+        "Routes canonical service contracts and adapters to usd-content-workspace and client access or resolution to ovstorage.",
+        "Clarifies the actual backend API and versioning behavior rather than assuming S3 compatibility or substituting another storage system.",
+        "Asks whether direct writers remain and identifies how their changes affect version identity and stale-write detection.",
+        "Separates API conformance from authenticated client/application tests, including write/readback and exact historical-version reads.",
+        "Uses the listed public repositories for evidence and reports any unavailable source rather than inventing verified commands."
+      ]
+    },
+    {
+      "id": "version-and-source-identities",
+      "prompt": "Using only the dated release record shipped with Omniverse Content Services, summarize its own version, the latest two recorded releases for ovstorage and ovpackage, and the selected workspace branch. How should I record an expert with no declared version? Is the ovstorage repository release automatically the Python wheel version, and is a workspace guide release a Git tag? Do not fetch newer data or run anything.",
+      "expected_output": "A dated evidence summary that distinguishes router, expert, repository, library and service release identities, retains the selected workspace branch, and marks missing expert versions as unversioned.",
+      "files": [],
+      "assertions": [
+        "Identifies the router as omniverse-content-services@0.1.0 and states the release record's observation date instead of claiming it is a live latest-version check.",
+        "Reports ovstorage v0.4.0 and v0.3.0 and ovpackage 0.2.1 and 0.1.0, retaining the ovpackage prerelease labels.",
+        "Distinguishes ovstorage repository 0.4.0, library 0.3.0 and preview resolver 0.1.0 rather than prescribing a wheel version from the repository tag.",
+        "Retains workspace release/v0.1.0 and distinguishes that branch from GitHub Releases and guide/service release sets.",
+        "Records an expert with readable metadata but no declared version as unversioned, with its source revision separate, and does not claim runtime validation."
+      ]
+    },
+    {
+      "id": "prebuilds-and-cache-routing",
+      "prompt": "Use only the packaged Content Services references to point me to prebuilt Storage and Live Edit services, plus workstation, shared-content and derived-data caches. Explain each cache's role and where its documentation is. Do not download, install or deploy anything.",
+      "expected_output": "Official NGC and documentation routes for the requested services and Hub, OVCC and OVDC, with artifact versions kept distinct and access or runtime verification stated accurately.",
+      "files": [],
+      "assertions": [
+        "Provides official NGC collection or artifact links for Storage and Live Edit, with owning service documentation.",
+        "Identifies Hub Workstation Cache, Omniverse Content Cache (OVCC) and Omniverse Derived Cache (OVDC), with their different reuse roles and documentation links.",
+        "Routes placement and integration questions to usd-caches rather than treating a cache as an authoritative content store.",
+        "Distinguishes resource packages, charts and container images, and retains relevant incomplete or conflicting version evidence if giving versions.",
+        "Separates public catalog visibility, download entitlement and runtime compatibility, and performs no downloads or deployments."
+      ]
+    },
+    {
+      "id": "mesh-modeling-negative",
+      "prompt": "I am sculpting a stylized character and want advice on improving the silhouette of its nose. This is only a modeling question; I have no content storage, pipeline or collaboration problem.",
+      "expected_output": "Modeling guidance or a suitable modeling-specialist referral without activating the Content Services workflow or introducing storage architecture.",
+      "expected_skill": null,
+      "files": [],
+      "assertions": [
+        "Does not select omniverse-content-services as the workflow for this request.",
+        "Gives scoped modeling advice or refers to a relevant available specialist without inventing an installed skill.",
+        "Does not add content service deployment, cache placement, package publication or infrastructure discovery questions."
+      ]
+    },
+    {
+      "id": "simulation-algorithm-negative",
+      "prompt": "Explain how to tune the reward function for a robot reaching task. The simulation already has its assets, and I am not asking about data access, storage, versioning or a content pipeline.",
+      "expected_output": "A simulation or reinforcement-learning explanation that stays outside the Content Services workflow.",
+      "expected_skill": null,
+      "files": [],
+      "assertions": [
+        "Does not select omniverse-content-services for a simulation-algorithm question without a content workflow need.",
+        "Addresses reward design or routes to an appropriate available specialist.",
+        "Does not recommend storage adapters, caches, Live sessions or package infrastructure as prerequisites for answering."
+      ]
+    }
+  ]
+}
diff --git a/skills/omniverse-content-services/references/prebuilt-artifacts.md b/skills/omniverse-content-services/references/prebuilt-artifacts.md
new file mode 100644
index 000000000..401edc342
--- /dev/null
+++ b/skills/omniverse-content-services/references/prebuilt-artifacts.md
@@ -0,0 +1,65 @@
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
+# NGC prebuilds and documentation
+
+Checked **2026-10-20**. Use these links to find supported distribution artifacts
+and owning documentation. Read the [release record](releases.md) before selecting
+versions; source repositories, libraries, charts, images and API specifications
+have separate release identities. Fetch and deployment instructions belong to the
+[workspace and cache experts](repositories.md), not this router.
+
+## Services
+
+Start with the [NGC service collection](https://catalog.ngc.nvidia.com/orgs/nvidia/teams/omniverse/collections/storage_apis)
+and [Developer Guide](https://docs.omniverse.nvidia.com/ovstorage/ovstorage-guide/latest/index.html).
+The collection retains the catalog label “Omniverse Storage APIs.” It distributes
+service artifacts; the broad workflow expert here is Omniverse Content Services.
+The `ovstorage` client library is a separate component, not the Storage Service image.
+
+| Capability | Prebuilt entrypoints | Owning documentation |
+| --- | --- | --- |
+| Storage access through service adapters | [Storage image](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/containers/storage-service/-), [chart](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/helm-charts/storage-service/-) | [Storage configuration](https://docs.omniverse.nvidia.com/ovstorage/ovstorage-guide/latest/dev-journey/full-deployment/storage-service.html); follow its service reference for configuration authority |
+| Service discovery | [Legacy Discovery chart](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/helm-charts/discovery-service/-); locate Auto Discovery in the service collection | [Discovery guide](https://docs.omniverse.nvidia.com/ovstorage/ovstorage-guide/latest/dev-journey/full-deployment/discovery-service.html); ask the workspace expert to distinguish the static catalog from the operator |
+| Notifications and subscriptions | [Aggregation image](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/containers/event-aggregation-service/-), [chart](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/helm-charts/event-aggregation-service/-); [Consumer image](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/containers/event-consumer-service/-), [chart](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/helm-charts/event-consumer-service/-) | [Notifications guide](https://docs.omniverse.nvidia.com/ovstorage/ovstorage-guide/latest/dev-journey/full-deployment/notifications-services.html), including broker dependencies |
+| Permission policies | [Permission image](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/containers/permission-service/-), [chart](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/helm-charts/permission-service/-) | [Permissions guide](https://docs.omniverse.nvidia.com/ovstorage/ovstorage-guide/latest/dev-journey/full-deployment/permissions-service.html) |
+| Identity and User Info | Service collection: `microsoft-graph-userinfo-service` and authentication dependencies; verify exact coordinates using the workspace inventory | [User Info guide](https://docs.omniverse.nvidia.com/ovstorage/ovstorage-guide/latest/dev-journey/full-deployment/userinfo-service.html) |
+| Live USD sessions | [Live Edit image](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/containers/live-edit-service/-), [chart](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/helm-charts/live-edit-service/-) | [Live Edit deployment](https://docs.omniverse.nvidia.com/ovstorage/ovstorage-guide/latest/dev-journey/full-deployment/live-edit-service.html) and [ovlive client integration](https://github.com/nvidia-omniverse/ovlive/blob/v0.1.0/client/README.md) |
+| Thumbnail generation and retrieval | [Thumbnail image](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/containers/thumbnail-service/-), [chart](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/helm-charts/thumbnail-service/-) | Developer Guide's Thumbnail Service sections; verify the worker image as well as the service |
+
+Navigator, permission UI, API specification resources and supporting test artifacts
+are also in the workspace inventory. Load that inventory for those tasks instead
+of treating every artifact as a mandatory service. An API resource is not a
+running service. Custom adapters still require implementation and conformance
+checks; a prebuilt service does not prove support for an arbitrary backend.
+
+## Caches
+
+| Cache and purpose | Prebuilt distribution | Owning documentation |
+| --- | --- | --- |
+| Hub Workstation Cache: local reuse of content and derived data through supported clients | [Resource packages](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/resources/hub_workstation_cache), [container](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/containers/hub_workstation_cache/-) | [Hub guide](https://docs.omniverse.nvidia.com/utilities/latest/cache/hub-workstation.html) |
+| Omniverse Content Cache (OVCC): shared source-content caching | [Image `usd-content-cache`](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/containers/usd-content-cache/-), [chart `ovcontentcache`](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/helm-charts/ovcontentcache/-) | [OVCC guide](https://docs.omniverse.nvidia.com/ovcaches/ovcontentcache/latest/index.html) |
+| Omniverse Derived Cache (OVDC): shared reuse of computed/derived data | [Image](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/containers/ovderivedcache/-), [chart](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/helm-charts/ovderivedcache/-) | [OVDC guide](https://docs.omniverse.nvidia.com/ovcaches/ovderivedcache/latest/) |
+
+Ask the cache expert to select placement and compatible client integrations from
+the user's locality, reuse and retention constraints. These caches do not turn
+an arbitrary SMB/NFS client into a cache-aware application. Establish permission
+for managed local caching before recommending workstation persistence.
+
+## Artifact selection and access
+
+Catalog visibility, entitlement, download access and runtime behavior are separate
+checks. Some NGC entries require sign-in or subscription access. Container images
+and Helm charts use different registries and authentication; an NGC acquisition
+key is not a runtime service identity. Use the workspace expert's
+[artifact-access reference on release/v0.1.0](https://github.com/nvidia-omniverse/usd-content-workspace/blob/release/v0.1.0/skills/usd-content-workspace-expert/references/deploy/artifact-access.md)
+and the [NGC catalog guide](https://docs.nvidia.com/ngc/latest/ngc-catalog-user-guide.html)
+for the actual retrieval procedure. Never put credentials in a report.
+
+For a concrete deployment handoff, identify the selected chart version and every
+required image tag (including workers and test images), the relevant API/client
+versions and host support, then have the owning expert verify the rendered
+configuration and a representative workflow. Record immutable digests when
+available. If a source or catalog listing disagrees with a release inventory,
+report the discrepancy and verify the exact artifact instead of silently choosing
+a substitute. Documentation review alone does not verify a download or deployment.
diff --git a/skills/omniverse-content-services/references/releases.md b/skills/omniverse-content-services/references/releases.md
new file mode 100644
index 000000000..b89023bd7
--- /dev/null
+++ b/skills/omniverse-content-services/references/releases.md
@@ -0,0 +1,103 @@
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
+# Release record
+
+Checked **2026-10-20**. Router: **omniverse-content-services@0.1.0**.
+This is a dated source review, not a tested compatibility matrix or deployment
+lockfile. Use [repository routes](repositories.md) for expert entrypoints and
+[NGC prebuilds](prebuilt-artifacts.md) for downloads and service documentation.
+
+## Repository releases and source revisions
+
+GitHub releases below are ordered by publication date, excluding drafts and
+retaining prerelease labels. A source tag does not imply a GitHub Release or a
+matching NGC artifact. No second release is invented when only one tag exists.
+
+| Repository | Most recent published release | Previous published release | Interpretation |
+| --- | --- | --- | --- |
+| ovstorage | [v0.4.0](https://github.com/nvidia-omniverse/ovstorage/releases/tag/v0.4.0), 2026-10-15 | [v0.3.0](https://github.com/nvidia-omniverse/ovstorage/releases/tag/v0.3.0), 2026-09-22 | v0.4.0 adds the preview USD resolver and reorganizes the repository. v0.3.0 adds cloud URL aliases, Hugging Face access and experimental Hub integration. |
+| ovpackage | [0.2.1](https://github.com/nvidia-omniverse/ovpackage/releases/tag/0.2.1), 2026-08-14, **prerelease** | [0.1.0](https://github.com/nvidia-omniverse/ovpackage/releases/tag/0.1.0), 2026-06-02, **prerelease** | 0.2.1 expands connections and transfer handling; 0.1.0 provides the initial package CLI/API release. |
+| usd-content-workspace | No GitHub Releases or source tags found | None found | Selected source: [release/v0.1.0 branch](https://github.com/nvidia-omniverse/usd-content-workspace/tree/release/v0.1.0). A release branch is distinct from published GitHub Releases and the service release sets below. |
+| ovlive | No GitHub Releases; one [source tag v0.1.0](https://github.com/nvidia-omniverse/ovlive/tree/v0.1.0) | No second tag found | Client 0.1.0 is experimental. Live Edit Service 0.1.1 is a separate NGC artifact; neither number is its wire protocol version. |
+| usd-caches | No GitHub Releases; one [source tag v0.1.0](https://github.com/nvidia-omniverse/usd-caches/tree/v0.1.0) | No second tag found | Hub, OVCC and OVDC have independent artifact versions below. |
+
+The [ovstorage version manifest](https://github.com/nvidia-omniverse/ovstorage/blob/v0.4.0/VERSION.md)
+identifies repository 0.4.0, library 0.3.0 and preview resolver 0.1.0. Do not tell
+users to install an `ovstorage==0.4.0` wheel based on the repository release.
+
+| Inspected source | Exact revision | Declared expert version |
+| --- | --- | --- |
+| ovstorage v0.4.0 | `42270c5236008e76c0e356c8e5f350305138d7c2` | `ovstorage-expert`: **unversioned** |
+| ovpackage 0.2.1 | `fe7299fc206f30565a7a48ff100a9e4e98625f6b` | `ovpackage-cli` and `ovpackage-api`: **unversioned**; task-skill fallback |
+| usd-content-workspace `release/v0.1.0` branch | `748f472fe4c00a74368e416fa36469dbe5d82af4` | `usd-content-workspace-expert`: **unversioned** |
+| ovlive v0.1.0 | `1a7dfe65c1b5662c70d8a9320b32d8b08eb2ae4c` | **unknown**: no expert entrypoint found; documentation fallback |
+| usd-caches v0.1.0 | `019b30238a886026610748acc01e143390995c53` | `usd-caches-expert`: **unversioned** |
+
+Previous release revisions: ovstorage v0.3.0
+`8a8689c0f497ae9755052cce9ceb4cbb13378234`; ovpackage 0.1.0
+`7cd965abdeda9d6c014413604ae1865cda3dc9c7`. Read the expert at the version
+actually selected; the metadata above describes the inspected current revisions.
+An attribution to an older skill package is not a version declaration for the
+current expert.
+
+## Service release sets
+
+The [Developer Guide changelog](https://docs.omniverse.nvidia.com/ovstorage/ovstorage-guide/latest/changelog.html)
+lists **1.3.0** and **1.2.0** as its latest two release sets, reviewed here on
+2026-10-20; the page was updated 2026-10-07. These are guide/service release sets,
+not usd-content-workspace Git tags or a version of the whole Content Services portfolio.
+1.3.0 adds Live Edit, Thumbnails and migration tooling, and updates notifications
+and Navigator. 1.2.0 adds manifest/metadata support and User Info integration.
+
+For exact charts, images, API resources and upgrade boundaries, read the workspace
+expert's [released inventory on release/v0.1.0](https://github.com/nvidia-omniverse/usd-content-workspace/blob/release/v0.1.0/skills/usd-content-workspace-expert/references/versions/released-inventory.md).
+It records an NGC observation on **2026-10-07**, with a current 1.3.0 set and a
+previous `published` profile. The following is a routing summary of those profiles,
+not proof of the two most recent individual NGC uploads:
+
+| Service | Current inventory chart / image | Previous inventory chart / image |
+| --- | --- | --- |
+| Storage | 1.2.3 / 1.2.3 | 1.2.0 / 1.2.0 |
+| Auto Discovery | 1.1.1 / 1.1.1 | Absent; previous profile uses legacy Discovery |
+| Legacy Discovery | 2.3.11 / simple-nginx 1.1.0 | 2.3.11 / simple-nginx 1.1.0 |
+| Event Aggregation | 1.6.0 / 1.6.0 | 1.5.6 / 1.5.6 |
+| Event Consumer | 1.11.0 / 1.11.0 | 1.10.0 / 1.10.0 |
+| Permission | 0.0.53 / 0.0.53 | 0.0.52 / 0.0.52 |
+| Microsoft Graph User Info | 0.0.8 / 0.0.8 | 0.0.7 / 0.0.7 |
+| Live Edit | 0.1.1 / 0.1.1 | Absent |
+| Thumbnail | 0.1.0 / 0.1.0 | Absent |
+
+Evidence conflicts remain explicit: the guide lists Auto Discovery 1.1.0 while
+the inventory lists 1.1.1. Several anonymously visible NGC listings show older
+versions than the inventory. Verify the selected artifact through authorized NGC
+access before use; neither a successful catalog page load nor a source chart's
+`appVersion` proves that an image can be fetched or works with the host.
+
+## Cache artifact versions
+
+| Artifact | Latest evidenced version | Earlier evidenced version | Evidence and limits |
+| --- | --- | --- | --- |
+| Hub workstation resource packages | 2.3.0, 2026-08-31 | 2.2.0, 2026-07-07 | Latest two entries in [NGC resource history](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/resources/hub_workstation_cache/2.3.0/version-history). |
+| Hub container | 2.2.0 displayed | Previous container tag unverified | [Container listing](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/containers/hub_workstation_cache/-); do not infer a 2.3.0 image from the resource packages. |
+| OVCC chart `ovcontentcache` | 4.0.4 | Previous chart version unverified | [Chart listing](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/helm-charts/ovcontentcache/-). |
+| OVCC container `usd-content-cache` | 3.0.2 | 3.0.1 | [Container listing](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/containers/usd-content-cache/-) and [July manifest](https://docs.omniverse.nvidia.com/ov/ovs/26.07.0/manifest.html); the earlier manifest is not a complete tag history. |
+| OVDC chart `ovderivedcache` | 6.0.1 | 6.0.0 baseline; earlier history unverified | [Chart listing](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/helm-charts/ovderivedcache/-) identifies the naming change at 6.0.0. |
+| OVDC container `ovderivedcache` | 6.0.1 in October manifest | 6.0.0 displayed in catalog | [October manifest](https://docs.omniverse.nvidia.com/ov/ovs/latest/manifest.html) and [container listing](https://catalog.ngc.nvidia.com/orgs/nvidia/omniverse/containers/ovderivedcache/-) disagree on latest; verify the chosen tag through NGC. |
+
+The October manifest validates a particular reference architecture set; it is not
+a portfolio-wide latest-version index. It pairs OVCC chart 4.0.4 with image 3.0.2,
+although that chart defaults to 3.0.1. Follow the owning deployment guide's image
+override. Do not equate a chart version, its default image and its `appVersion`.
+
+## Refresh and handoff
+
+When refreshing this record, check all five GitHub release histories and tags,
+the guide changelog, workspace inventory and NGC histories. Retain up to two
+published releases for each component and state explicitly when a previous
+version or history is unavailable. Include publication dates when provided,
+prerelease status, exact source revision, expert version, artifact type and source
+link. Advance the checked date only after reviewing the sources; retain upstream
+observation dates. A moving `latest` page must not silently change an existing
+workflow's selected versions. Do not promote unreleased source changes into the
+release record. Record any fetch, compatibility or runtime checks separately.
diff --git a/skills/omniverse-content-services/references/repositories.md b/skills/omniverse-content-services/references/repositories.md
new file mode 100644
index 000000000..c89071fde
--- /dev/null
+++ b/skills/omniverse-content-services/references/repositories.md
@@ -0,0 +1,41 @@
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
+# Repository routes
+
+These are routing targets, not guarantees of public availability or compatibility.
+Read the entrypoint at the selected revision before relying on it. If a candidate
+path is absent, inspect the repository's skill index and report the gap.
+
+For each actual handoff, capture the expert's declared version separately from
+its Git revision and the component/API versions being discussed. Use the version
+rules in the router. The [release record](releases.md) records inspected revisions
+and version metadata; these routes do not establish runtime compatibility.
+
+| Need | Public source | Expert or documented entrypoint |
+| --- | --- | --- |
+| Access existing storage, configure client authentication, integrate USD resolution | [ovstorage](https://github.com/nvidia-omniverse/ovstorage) | [ovstorage expert](https://github.com/nvidia-omniverse/ovstorage/blob/v0.4.0/skills/ovstorage-expert/SKILL.md) |
+| Implement content service contracts or adapters; local-process or cluster services | [usd-content-workspace](https://github.com/nvidia-omniverse/usd-content-workspace/tree/release/v0.1.0) | [workspace expert on release/v0.1.0](https://github.com/nvidia-omniverse/usd-content-workspace/blob/release/v0.1.0/skills/usd-content-workspace-expert/SKILL.md) |
+| Publish and consume exact package versions and dependencies | [ovpackage](https://github.com/nvidia-omniverse/ovpackage) | Verified task-skill fallback: [CLI](https://github.com/nvidia-omniverse/ovpackage/blob/0.2.1/.agents/skills/ovpackage-cli/SKILL.md) or [API](https://github.com/nvidia-omniverse/ovpackage/blob/0.2.1/.agents/skills/ovpackage-api/SKILL.md); no dedicated expert found at this revision |
+| Concurrent USD edits, session integration and recovery | [ovlive](https://github.com/nvidia-omniverse/ovlive) | Documentation fallback: [client](https://github.com/nvidia-omniverse/ovlive/blob/v0.1.0/client/README.md), [support boundary](https://github.com/nvidia-omniverse/ovlive/blob/v0.1.0/client/docs/ovlive-support-boundary.md), [service](https://github.com/nvidia-omniverse/ovlive/blob/v0.1.0/service/README.md). No SKILL.md or AGENTS.md found at this revision; do not invent an expert handoff. |
+| Local/shared source-content or derived-data caching | [usd-caches](https://github.com/nvidia-omniverse/usd-caches) | [cache expert](https://github.com/nvidia-omniverse/usd-caches/blob/v0.1.0/skills/usd-caches-expert/SKILL.md) |
+
+Use `release/v0.1.0` for usd-content-workspace, including local checkout selection.
+Resolve and record the branch's current commit for each handoff; branch links can
+advance. Keep this branch selection when refreshing the release record.
+
+For prebuilt deployments, follow [NGC artifacts and owning documentation](prebuilt-artifacts.md).
+The workspace expert owns service deployment and release-inventory interpretation;
+the cache expert owns Hub, OVCC and OVDC placement and integration. The ovlive
+client and its separately versioned Live Edit Service require compatible hosts;
+a source tag alone does not demonstrate a runnable integration.
+
+Handoff example: “We have one developer on Linux, existing filesystem content,
+and want a plain local service process. Preserve the filesystem as authority.
+Using this source revision, identify the smallest runnable option, actual APIs,
+prerequisites, limitations and a disposable save/readback check. Cite source files;
+do not deploy anything.”
+
+A multi-region case should additionally give worker locations, source location,
+read reuse, derived-data generation and allowed retention. Request a topology and
+its evidence; do not guess cache counts, bucket replication or automatic failover.
diff --git a/skills/omniverse-content-services/references/workflow-discovery.md b/skills/omniverse-content-services/references/workflow-discovery.md
new file mode 100644
index 000000000..31de71948
--- /dev/null
+++ b/skills/omniverse-content-services/references/workflow-discovery.md
@@ -0,0 +1,170 @@
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
+# Discover the content workflow
+
+Start with what the user needs to create and who or what consumes it next. Then
+identify the authoritative sources, required handoff, and execution locations.
+Keep user requirements, proposed designs, and verified component behavior separate.
+These examples help discover requirements; they do not assert ready-made connectors,
+format conversion, domain correctness, or deployed integrations.
+
+## Recognize the industry and the content task
+
+| Context and example request | Content path to explore | Key qualification |
+| --- | --- | --- |
+| Manufacturing and factory planning: “Use our engineering data to compare production layouts.” | Parts and assemblies → task-suitable assets → equipment/cell/factory scenes → planning or simulation | Which dimensions, placements, engineering metadata and revisions must survive the handoff? |
+| Automotive: “Share vehicle variants between design, visualization and simulation.” | Design assemblies → geometry, materials and variant products → configured vehicle or road scene | Which configuration and source revision does each consumer accept? |
+| Architecture, engineering and construction: “Coordinate building and site content from several tools.” | CAD/BIM and survey sources → discipline contributions → coordinated building/site → review or simulation | How are coordinates, units, source authority and discipline updates reconciled? |
+| Operational digital twins: “Keep a deployed scene aligned with changes in our facility.” | Accepted scene baseline + asset changes and observations → reviewed update → consuming application | Which changes update content, which are live state, and what must remain reproducible? |
+| Media, entertainment and general 3D creation: “Let artists and agents build scenes together.” | Models, textures, materials, rigs and animation → asset products → layout, lighting and shots → rendering | Which role owns each output and when may downstream work adopt it? |
+| Robotics and physical AI: “Turn robot and environment assets into repeatable training runs.” | Robot/environment sources → simulation-ready representations → task scenes and configurations → training/evaluation outputs | Which content, physics assumptions, software/configuration and inputs identify a run? |
+| Fleet simulation and autonomy: “Run many vehicle or robot scenarios across a compute farm.” | Shared assets and environments + scenario variants → pinned job inputs → distributed runs and results | Which workers reuse which versions, and how are results linked to scenario inputs? |
+| Other fields, including logistics and immersive environments | Source content → owned contributions → accepted product → receiving task | Ask what the recipient must do; do not force an industry-specific pipeline. |
+
+Industry is context, not a deployment prescription. One project can combine several
+rows. Asset creation is often a dependency graph: a material, model, rig, layout
+and simulation configuration may advance independently. Do not force every project
+through a linear modeling-to-rendering sequence.
+
+Distinguish working edits, review previews, published versions and accepted
+configurations. A new version is not automatically approved for every consumer.
+Creators can continue working while downstream people and jobs consume an
+identified baseline; adopting a change is a separate decision.
+
+For conversion and handoff, ask what must survive: source and instance identities,
+units, coordinates, relationships, metadata, materials or behavior. Preserve the
+editable source and record intentional losses. Verify the required open, edit,
+save, export or simulation operation in the receiving tool.
+
+## Choose a workflow path, then the component expert
+
+Use the public links in [repository routes](repositories.md). Load only the expert
+needed for the current decision; ownership below is a routing guide.
+
+| User intent | Establish first | Route and first useful proof |
+| --- | --- | --- |
+| Use existing infrastructure with USD | Current file/object stores or asset systems, identity, native formats, protocols, and read/write needs | `ovstorage` for client access/resolution; `usd-content-workspace` for service contracts/adapters. Open one representative asset and its dependencies through the intended application. |
+| Create or refine content with people and agents | Native source versus derived USD, contribution ownership, required consumer semantics | Coordinate the creation/conversion specialist, then access and publication experts. Verify what the receiving task needs; opening a USD file alone does not establish simulation readiness. |
+| Version USD content and publish accepted work | Editable sources, complete output products, dependency versions, approval boundary and retention | `ovpackage` for publications and dependencies; `ovstorage` for file identity and conditional writes. Reopen an exact accepted scene after an upstream asset changes. |
+| Collaborate on an asset or scene | Explain live sessions and reviewed contributions, then qualify tools, ownership and desired interaction | `ovlive` for concurrent USD sessions and interactive feedback; access/publication experts for handoffs. Test ownership, conflict behavior and recovery in the actual host applications. |
+| Deliver USD to scale-out compute | Source and worker locations, job input versions, repeated reads, network limits and allowed caching | `usd-caches` with access/package experts. Compare cold and repeated runs while verifying identical input versions and complete dependencies on fresh workers. |
+| Feed results back into content refinement | Baseline scene, input versions, transformation/settings, produced outputs and acceptance decision | Publication/access experts with the domain specialist. Trace a result to its inputs and adopt a changed asset explicitly without altering the old baseline. |
+
+Treat PLM, BIM, asset-management systems, shares and object stores as possible
+sources, not prevalidated integrations. A new service may expose compatible
+contracts while those systems remain authoritative. Qualify native application
+access separately from USD reference resolution.
+
+For distributed jobs, distinguish scene/asset inputs from code, configuration and
+random seeds needed for repeatability. Record the inputs the job actually used,
+give outputs explicit ownership, and link results to that record. Content Services
+does not establish scheduler support, simulation fidelity or reproducibility of
+an entire training system by itself.
+
+## Explain collaboration options before qualifying
+
+A vague collaboration request is an opportunity to explain what the team could
+do. Offer [ovlive](https://github.com/nvidia-omniverse/ovlive) by name and explain
+its role in concurrent USD sessions before narrowing the workflow. Cover these
+complementary options in plain language:
+
+| Option | What it enables and why it helps |
+| --- | --- |
+| Live USD collaboration with `ovlive` | People and agents participate in a shared editing session through compatible integrations. Shared visibility lets a person inspect an agent's contributions as work progresses, gives collaborators common scene context, and can reduce repeated export/reload handoffs and feedback delays. Useful for interactive scene assembly, joint iteration and review while editing. |
+| Independent contributions with reviewed publication | People and agents own separate assets, layers or other outputs and publish identified versions. This supports asynchronous work and gives downstream consumers a stable baseline they can adopt explicitly. |
+| A combination | Use a live session to iterate together, then review and publish the accepted result for other teams or simulation jobs. Continued live work does not silently change a job's pinned inputs. |
+
+For example, propose a person adjusting a factory layout while an agent updates
+an assigned material contribution, with both inspecting the shared USD scene.
+Explain the intended benefit: the person can guide and correct the work during
+creation. Treat this as a workflow to qualify in their tools, not a verified
+integration or a claim that every agent harness can join without integration.
+
+After explaining the options, ask which applications and agent interfaces they
+use, and whether they want live work, reviewed handoffs or both. Route session
+integration, supported operations, overlapping edits, permissions and recovery to
+the ovlive expert at the selected revision. Do not promise automatic conflict-free
+editing, arbitrary native-file collaboration, approval, or version history from a
+live session alone. Keep the benefits clear even when implementation support still
+needs verification; disclose unavailable source evidence without inventing details.
+
+## Ask questions that change the next decision
+
+- Establish the current problem: synchronization delays, stale reads, concurrent
+  writes, reproducibility, or storage growth. “Consistency” needs an observable
+  expectation such as rejecting an outdated save or reopening an exact revision.
+- Separate the application-to-service connection from the service-to-storage
+  connection. A Linux service using a NAS mount does not establish how a Windows
+  or macOS application opens its native files.
+- For each first-test application, establish native source formats, USD exports,
+  runtime/OS support, and actual open/save integration. A USD resolver does not
+  make every native file operation service-aware.
+- “Several agents on one asset” leaves ownership unresolved. Distinguish separate
+  contributions/layers, serialized edits to one native file, and simultaneous
+  USD session edits. Explain ovlive and its benefits when offering these choices;
+  live collaboration can be useful even when contributors own different parts.
+- Ask whether the user accepts a managed store or needs ordinary folders that
+  applications edit directly. Do not initialize a managed backend over existing
+  source folders or promise transparent compatibility between those models.
+- Clarify local-copy policy: "Is managed local caching okay, provided your central
+  system remains authoritative, or do you need content never to persist on the
+  device? Are you mainly trying to avoid manual downloads and unmanaged copies?"
+  Record the answer before choosing cache placement or remote authoring. If caching
+  is acceptable, establish relevant retention, cleanup and lost-device protection
+  requirements with the cache expert; do not assume those controls are implemented.
+  Distinguish disposable read caches from writable working files, unsaved edits,
+  autosaves and offline replicas. Direct network access alone does not establish
+  that applications leave no local data. Avoid treating a ban on unmanaged copies
+  as a ban on all caching, or treating permission to cache as permission for offline
+  authoring or unrestricted duplication.
+
+## Return a capability map with evidence
+
+For each requested capability, state the owning repository, implementation at
+its selected revision, application/backend prerequisites, and one acceptance
+check. Label it as implemented, example-only, a build recipe, or unknown; record
+runtime evidence separately. Avoid presenting the whole portfolio as features
+already installed in a proposed single-host service.
+
+Version history, immutable asset releases, deduplication, conflict detection,
+Live collaboration and backup solve different problems. Ask the storage expert
+about file versions and conditional writes, the package expert about exact
+published dependencies, and the Live expert about concurrent USD sessions.
+Do not infer deduplication or transactions merely from package versioning.
+Whole-file deduplication reuses identical files; it does not imply block deltas
+for a changed large native document. Measure actual retained bytes.
+
+When source data, converters or assets change, identify affected consumers before
+adoption. Preserve the previous exact inputs and verify the proposed update with
+the receiving application. Package dependencies do not automatically establish
+the closure of every USD reference, texture or other resource a consumer needs.
+
+For NAS-backed services, ask the workspace expert to qualify where content,
+metadata databases, manifests, journals and locks live. Check persistence,
+rename/locking and failure behavior on the actual mount. Neither SMB nor NFS
+alone supplies version history, application conflict resolution or recovery.
+Do not promise one protocol is faster without a representative measurement.
+
+For cache advice, distinguish workstation caches, shared source-content caches,
+and caches of derived computation. Verify backend, client routing and host support. A local cache
+is not automatically a LAN cache, and a remote content cache is not necessarily
+an accelerator for an ordinary NAS mount. Distinguish examples tested against
+mocks from real cache-binary and application checks.
+
+## Small proof before expansion
+
+Choose one representative content handoff and receiving task. Agree on output
+ownership and success criteria before writing. For collaboration, use two
+contributors and test a stale save; for versioning, test exact old-version reads
+and publication; for compute, use a fresh worker and verify dependency closure.
+Add save/readback, storage-growth and interruption/restart checks where relevant.
+For a custom service, separate API conformance from authenticated application
+tests, permissions, recovery and performance. Skipped tests and pod readiness are
+not workflow passes. A small successful proof does not qualify production scale.
+
+When asked where to start with source, give the owning repository and the actual
+entrypoint at the selected revision. Follow with the smallest example and the
+implementation framework; explicitly label any recipe that requires new code.
+Verify the public source path and accessibility before recommending it. Do not
+turn a workstation-specific local path into release guidance.
diff --git a/skills/omniverse-content-services/skill-card.md b/skills/omniverse-content-services/skill-card.md
new file mode 100644
index 000000000..9a963bd69
--- /dev/null
+++ b/skills/omniverse-content-services/skill-card.md
@@ -0,0 +1,98 @@
+## Description: <br>
+Omniverse Content Services guides USD content collaboration and content access workflows on existing infrastructure, covering USD content versioning, 3D creation pipelines, and data access across distributed and scale-out compute, and routes implementation questions to the ovstorage, ovpackage, ovlive, usd-content-workspace, and usd-caches experts. <br>
+
+This skill is ready for commercial/non-commercial use. <br>
+
+## Owner
+NVIDIA <br>
+
+### License/Terms of Use: <br>
+Apache 2.0 <br>
+## Use Case: <br>
+Developers, engineers, and agent harnesses building USD workflows and 3D content pipelines use this skill to discover workflow requirements (source authority, collaboration, versioning, compute locality, permitted caching) and to plan integrations that keep existing systems as the source of truth across manufacturing, automotive, AEC, media, robotics, digital-twin, and physical AI simulation use cases. <br>
+
+### Deployment Geography for Use: <br>
+Global <br>
+
+## Requirements / Dependencies: <br>
+**Requires API Key or External Credential:** [Optional] <br>
+**Credential Type(s):** [API key] <br>
+
+Do not include secrets in prompts/logs/output; use least-privilege credentials; rotate keys as appropriate. <br>
+
+## Known Risks and Mitigations: <br>
+Risk: Review before execution as proposals could introduce incorrect or misleading guidance into skills. <br>
+Mitigation: Review and scan skill before deployment. <br>
+
+## Reference(s): <br>
+- [Repository routes](references/repositories.md) <br>
+- [Discover the content workflow](references/workflow-discovery.md) <br>
+- [Release record](references/releases.md) <br>
+- [NGC prebuilds and documentation](references/prebuilt-artifacts.md) <br>
+- [ovstorage](https://github.com/nvidia-omniverse/ovstorage) <br>
+- [usd-content-workspace (release/v0.1.0)](https://github.com/nvidia-omniverse/usd-content-workspace/tree/release/v0.1.0) <br>
+- [ovpackage](https://github.com/nvidia-omniverse/ovpackage) <br>
+- [ovlive](https://github.com/nvidia-omniverse/ovlive) <br>
+- [usd-caches](https://github.com/nvidia-omniverse/usd-caches) <br>
+
+
+## Skill Output: <br>
+**Output Type(s):** [Analysis, Configuration instructions] <br>
+**Output Format:** [Markdown] <br>
+**Output Parameters:** [1D] <br>
+**Other Properties Related to Output:** [Workflow plans and expert handoffs record expert name, expert version, source repository, revision, and entrypoint; credentials are never included in reports.] <br>
+
+## Evaluation Agents Used: <br>
+- Claude Code (`aws/anthropic/bedrock-claude-opus-5-5`) <br>
+- Codex (`openai/openai/gpt-6.1-sol`) <br>
+
+
+
+## Evaluation Tasks: <br>
+10 evaluation tasks (8 positive, 2 negative), 1 attempt per task, each run in an isolated sandbox pod in a `k8s-sandbox` environment and compared against a no-skill baseline. Evaluator version `1.5.6`; evaluated 2026-10-24. <br>
+
+## Evaluation Metrics Used: <br>
+Reported benchmark dimensions: <br>
+- Security: Is it safe to use? Scored from the `security` signal. <br>
+- Correctness: Is the answer correct? Scored from the `accuracy` signal. <br>
+- Discoverability: Was the right skill loaded when needed? Scored from the `skill_execution` signal. <br>
+- Effectiveness: Did the skill help complete the task? Equal-weight mean of `goal_accuracy` and `behavior_check`. <br>
+- Efficiency: Did it avoid wasted tool calls and token usage? Equal-weight mean of `skill_efficiency` and `token_efficiency`. <br>
+
+Underlying evaluation signals used in this run: <br>
+- `security`: Unsafe operations, secret leakage, and unauthorized access. <br>
+- `skill_execution`: Whether the expected skill was selected, decoys were avoided, and the workflow executed. <br>
+- `skill_efficiency`: Tool-call productivity. <br>
+- `accuracy`: Final-answer correctness against the reference answer. <br>
+- `goal_accuracy`: Whether the user's goal was achieved. <br>
+- `behavior_check`: Whether the expected workflow behavior was followed. <br>
+- `token_efficiency`: Actual uncached prompt plus completion token usage. <br>
+
+
+
+## Evaluation Results: <br>
+Overall verdict: PASS — Recommended for publication.
+
+| Measure | Claude Code (Baseline → Skill Uplift) | Codex (Baseline → Skill Uplift) |
+|---|---:|---:|
+| Overall | 88.2% (uplift unavailable) | 80.0% (uplift unavailable) |
+| Security | 100.0% → 85.0% (-15.0 points) | 100.0% → 85.0% (-15.0 points) |
+| Correctness | 64.0% → 100.0% (+36.0 points) | 74.0% → 92.0% (+18.0 points) |
+| Discoverability | 95.0% (uplift unavailable) | 83.1% (uplift unavailable) |
+| Effectiveness | 45.3% → 86.3% (+41.0 points) | 50.7% → 69.4% (+18.7 points) |
+| Efficiency | 74.6% (uplift unavailable) | 70.4% (uplift unavailable) |
+
+| Tier | Purpose | Status | Evidence |
+|---|---|---|---|
+| Tier 1 | Static validation | PASSED WITH OBSERVATIONS | 11 validator(s); 18 finding(s) |
+| Tier 2 | Semantic deduplication | PASSED | 2 validator(s); 0 finding(s) |
+| Tier 3 | Live agent evaluation | PASS | 2 agent(s); 10 task(s) |
+
+## Skill Version(s): <br>
+0.1.0 (source: frontmatter, pyproject.toml) <br>
+
+## Ethical Considerations: <br>
+NVIDIA believes Trustworthy AI is a shared responsibility and we have established policies and practices to enable development for a wide array of AI applications. When downloaded or used in accordance with our terms of service, developers should work with their internal team to ensure this skill meets requirements for the relevant industry and use case and addresses unforeseen product misuse. <br>
+
+(For Release on NVIDIA Platforms Only) <br>
+Please report quality, risk, security vulnerabilities or NVIDIA AI Concerns [here](https://app.intigriti.com/programs/nvidia/nvidiavdp/detail). <br>
diff --git a/skills/omniverse-content-services/skill.oms.sig b/skills/omniverse-content-services/skill.oms.sig
new file mode 100644
index 000000000..af233ae2f
--- /dev/null
+++ b/skills/omniverse-content-services/skill.oms.sig
@@ -0,0 +1 @@
+{"mediaType":"application/vnd.dev.sigstore.bundle.v0.3+json","verificationMaterial":{"x509CertificateChain":{"certificates":[{"rawBytes":"MIICgzCCAgmgAwIBAgIUKIyS7SxNteQIiWzK1dWj85E6520wCgYIKoZIzj0EAwMwVTELMAkGA1UEBhMCVVMxGzAZBgNVBAoMEk5WSURJQSBDb3Jwb3JhdGlvbjEpMCcGA1UEAwwgTlZJRElBIEFnZW50IENhcGFiaWxpdGllcyBJQ0EgMDEwHhcNMjYwNDAxMDAwMDAwWhcNMjgwNDIyMTUzMzA5WjBUMQswCQYDVQQGEwJVUzEbMBkGA1UECgwSTlZJRElBIENvcnBvcmF0aW9uMSgwJgYDVQQDDB9OVklESUEgQWdlbnQgU2tpbGxzIFNpZ25pbmcgMDAxMHYwEAYHKoZIzj0CAQYFK4EEACIDYgAEYoRM9bQl/dGlwSRNi6bTpIJUXH8Nv9GciP6LSflJYYMLCc296kpyuTSsk5ddbAWiDcFX3C/ydX3jwc+qCLYP6uHy9XphyLjOQ27Yb2J6rBLVtRBS1mgGco/Gr7fL6ODco4GaMIGXMB0GA1UdDgQWBBRQ/5ZW3nJ6lmo9SVk7I15o7UGmpTAfBgNVHSMEGDAWgBRPGpILxMBBleJSsBGjrMKsby1CgjAMBgNVHRMBAf8EAjAAMA4GA1UdDwEB/wQEAwIHgDA3BggrBgEFBQcBAQQrMCkwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLm5kaXMubnZpZGlhLmNvbTAKBggqhkjOPQQDAwNoADBlAjAUygu/GiOCIXrgGr4SmLgeEVDcEitfFUv7ALbvLVGVyMysB3mxmO/uInZfXzWcJZsCMQDxuoxj4ZmO30jhkPIcCxGFCOvnUsnfU3TfGcouYm4M6iRpbKvtVnHPiy4bi6pcKf0="},{"rawBytes":"MIICiDCCAg6gAwIBAgIUZsIuSv9NkpJCNqtYEfCouVv5BzowCgYIKoZIzj0EAwMwUTELMAkGA1UEBhMCVVMxGzAZBgNVBAoMEk5WSURJQSBDb3Jwb3JhdGlvbjElMCMGA1UEAwwcTlZJRElBIEFnZW50IENhcGFiaWxpdGllcyBDQTAgFw0yNjA0MDEwMDAwMDBaGA85OTk5MTIzMTIzNTk1OVowVTELMAkGA1UEBhMCVVMxGzAZBgNVBAoMEk5WSURJQSBDb3Jwb3JhdGlvbjEpMCcGA1UEAwwgTlZJRElBIEFnZW50IENhcGFiaWxpdGllcyBJQ0EgMDEwdjAQBgcqhkjOPQIBBgUrgQQAIgNiAASI72cR3ctKGg4VWnB3bNja6g1Z2PnOmFEopkPof+QeIcPk9rT+g9MjJnq51EQXL93a7C2GJ9J985G4o2V85VD7wJ1RaXhluHW2rf3y8bQGeAYaKMr5s/hUgn+M3/9WlWejgaAwgZ0wHQYDVR0OBBYEFE8akgvEwEGV4lKwEaOswqxvLUKCMB8GA1UdIwQYMBaAFItnoAjjfuCEUvzyvWyI2vOGvwPjMBIGA1UdEwEB/wQIMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgEGMDcGCCsGAQUFBwEBBCswKTAnBggrBgEFBQcwAYYbaHR0cDovL29jc3AubmRpcy5udmlkaWEuY29tMAoGCCqGSM49BAMDA2gAMGUCMQCeIMMfAbyzPDacw2MxG+Yt1cikrJX/DVxiGfXuHmkkXn6VgSzE79+lkqDErpVO2gYCMCNEColOyvUvkzZGUEI1hQ3PfMgi3FIo9tHoBKMw4/wGBLFpu/0ubtmbBXM6/UMOEw=="},{"rawBytes":"MIICRTCCAcygAwIBAgIUeJdY3rV86EdvFmG7L8LJBsyQFYkwCgYIKoZIzj0EAwMwUTELMAkGA1UEBhMCVVMxGzAZBgNVBAoMEk5WSURJQSBDb3Jwb3JhdGlvbjElMCMGA1UEAwwcTlZJRElBIEFnZW50IENhcGFiaWxpdGllcyBDQTAgFw0yNjA0MDEwMDAwMDBaGA85OTk5MTIzMTIzNTk1OVowUTELMAkGA1UEBhMCVVMxGzAZBgNVBAoMEk5WSURJQSBDb3Jwb3JhdGlvbjElMCMGA1UEAwwcTlZJRElBIEFnZW50IENhcGFiaWxpdGllcyBDQTB2MBAGByqGSM49AgEGBSuBBAAiA2IABAYpiXCDjJ9NT2eSDhyHJVSw1Tbze18cGG2F/578oWvHxg23eQAhNRYdq88i1iOshZSO6C29doKui5Xpmo/7Ctw9Sx4PP2RzOmIuOLCuTdNtKcTRwi4GEsd5BAFvWj42M6NjMGEwHQYDVR0OBBYEFItnoAjjfuCEUvzyvWyI2vOGvwPjMB8GA1UdIwQYMBaAFItnoAjjfuCEUvzyvWyI2vOGvwPjMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMAoGCCqGSM49BAMDA2cAMGQCMCwtAjWLaNwgGWNCgdyNoTyvNhqWRECRJV2r3+7w8g0PL6NHLOsbkgE09BH95h8XlgIwTaQmbbUh2ChAJ5TA1wRiVDnCcvbzHlZl2jM2FcwQQZlk19LOAbyGMRixbu2Ww/rj"}]},"tlogEntries":[]},"dsseEnvelope":{"payload":"ewogICJfdHlwZSI6ICJodHRwczovL2luLXRvdG8uaW8vU3RhdGVtZW50L3YxIiwKICAic3ViamVjdCI6IFsKICAgIHsKICAgICAgIm5hbWUiOiAib21uaXZlcnNlLWNvbnRlbnQtc2VydmljZXMiLAogICAgICAiZGlnZXN0IjogewogICAgICAgICJzaGEyNTYiOiAiYzc1MjQ1MWM4ZGViMmIwNGIxNWEyZDliZTJlYTg4MDY3ZTk5NzJjMzQ3M2RjZjMyZjlkNmEwZWEwZjdkYWM5NCIKICAgICAgfQogICAgfQogIF0sCiAgInByZWRpY2F0ZVR5cGUiOiAiaHR0cHM6Ly9tb2RlbF9zaWduaW5nL3NpZ25hdHVyZS92MS4wIiwKICAicHJlZGljYXRlIjogewogICAgInNlcmlhbGl6YXRpb24iOiB7CiAgICAgICJoYXNoX3R5cGUiOiAic2hhMjU2IiwKICAgICAgIm1ldGhvZCI6ICJmaWxlcyIsCiAgICAgICJpZ25vcmVfcGF0aHMiOiBbCiAgICAgICAgIi5naXRpZ25vcmUiLAogICAgICAgICIuZ2l0aHViIiwKICAgICAgICAiLmdpdGF0dHJpYnV0ZXMiLAogICAgICAgICIuZ2l0IgogICAgICBdLAogICAgICAiYWxsb3dfc3ltbGlua3MiOiBmYWxzZQogICAgfSwKICAgICJyZXNvdXJjZXMiOiBbCiAgICAgIHsKICAgICAgICAibmFtZSI6ICJCRU5DSE1BUksubWQiLAogICAgICAgICJhbGdvcml0aG0iOiAic2hhMjU2IiwKICAgICAgICAiZGlnZXN0IjogImYyZmY2OTIzOGQxOWJkNTJiZDc3NmZhOTM4ZTM0NGQ5ODIzNmVjMTVjNWE0N2QzNmIzYzZkZTllMmY4ZjliM2YiCiAgICAgIH0sCiAgICAgIHsKICAgICAgICAibmFtZSI6ICJSRUFETUUubWQiLAogICAgICAgICJhbGdvcml0aG0iOiAic2hhMjU2IiwKICAgICAgICAiZGlnZXN0IjogIjFmZGFkNWZjMGY5ODZiYzc2YmZmMDE5ZjNkZjM5ZGYyMDBhOWZmYTMyNGQ0NzI5NDUyZWYwZGE1M2NkYjUzYzAiCiAgICAgIH0sCiAgICAgIHsKICAgICAgICAibmFtZSI6ICJTS0lMTC5tZCIsCiAgICAgICAgImFsZ29yaXRobSI6ICJzaGEyNTYiLAogICAgICAgICJkaWdlc3QiOiAiMTM4OTE4MGMzNzM0ZTJmOTM5OTI3MTJhZGVjOThlZTZlOGFhNjI4OGQwN2QxNjNjMWY0MTIzMTc5NTMxNmY0ZSIKICAgICAgfSwKICAgICAgewogICAgICAgICJuYW1lIjogImV2YWxzL2V2YWxzLmpzb24iLAogICAgICAgICJhbGdvcml0aG0iOiAic2hhMjU2IiwKICAgICAgICAiZGlnZXN0IjogIjI3MTc3NTgyYWYzNzU3ZWNjMzc0YWNkYTNkZTQ2NDQ1ZjVkN2JjMzY2NjU5NGU5ZTlhZDMwNGI5MGVkNDM4M2YiCiAgICAgIH0sCiAgICAgIHsKICAgICAgICAibmFtZSI6ICJyZWZlcmVuY2VzL3ByZWJ1aWx0LWFydGlmYWN0cy5tZCIsCiAgICAgICAgImFsZ29yaXRobSI6ICJzaGEyNTYiLAogICAgICAgICJkaWdlc3QiOiAiZGNkMTI2YWQ5YWZjODQ2YWIyYzViOTYwODgwMmUzNmNjM2YwYzY4YjRhYWEyOGM2NjQ1MDhjZDdiZTBmYmQ5ZCIKICAgICAgfSwKICAgICAgewogICAgICAgICJuYW1lIjogInJlZmVyZW5jZXMvcmVsZWFzZXMubWQiLAogICAgICAgICJhbGdvcml0aG0iOiAic2hhMjU2IiwKICAgICAgICAiZGlnZXN0IjogIjk4NTM5NzNkZGZjY2E1YzIxOTk3MzFkMDg5ZDNjODQ4YWI5MTA4Y2NlYWI0MzZlMGZkZDJmNjY5ZTBkNTc3ZDAiCiAgICAgIH0sCiAgICAgIHsKICAgICAgICAibmFtZSI6ICJyZWZlcmVuY2VzL3JlcG9zaXRvcmllcy5tZCIsCiAgICAgICAgImFsZ29yaXRobSI6ICJzaGEyNTYiLAogICAgICAgICJkaWdlc3QiOiAiNjljMDk2ZDBjZTE3NGM4YjEwYzE5Zjg3NGVjNWI5MDAxOTgxZWQ0MzgzNmJhMTk1NTAzZGZjMGI2NmQ2MGE0MiIKICAgICAgfSwKICAgICAgewogICAgICAgICJuYW1lIjogInJlZmVyZW5jZXMvd29ya2Zsb3ctZGlzY292ZXJ5Lm1kIiwKICAgICAgICAiYWxnb3JpdGhtIjogInNoYTI1NiIsCiAgICAgICAgImRpZ2VzdCI6ICI1MDEzYjk3YjQ0ZjUwYTA4ZWM4YzU0YTc4OThkZDU3ZThkNzRjMDgzZGEyZjc1NDUyZTViZjIzZDZiMDZkZWNhIgogICAgICB9LAogICAgICB7CiAgICAgICAgIm5hbWUiOiAic2tpbGwtY2FyZC5tZCIsCiAgICAgICAgImFsZ29yaXRobSI6ICJzaGEyNTYiLAogICAgICAgICJkaWdlc3QiOiAiZDE1NjNjYzkxYzdkY2RhMWYxMDY3MzM5ZDc2ZWMwYzc3YjA2Njg0OGE4ODgwOGVhMzgyN2FjNWI1ZDQ0Y2M5MSIKICAgICAgfQogICAgXQogIH0KfQ==","payloadType":"application/vnd.in-toto+json","signatures":[{"sig":"MGUCMENpPH/Xoy9+O6LBSWyr8RN3qNi69LnHIjreeC2f7j2ITi5yiMY9UZHIiARuRxlmsQIxAOsdpB3TWmxT7LYkSCI3U7MHZtEDq602FhRjozfm/k0IcNbra4iXwre/gTpw2wd5yw==","keyid":""}]}}
\ No newline at end of file