Skip to content

Manually stage 5 Physical AI Skill Hub skills (one-time content bridge)#150

Merged
mosheabr merged 1 commit into
mainfrom
moshea/physical-ai-manual-bridge
May 29, 2026
Merged

Manually stage 5 Physical AI Skill Hub skills (one-time content bridge)#150
mosheabr merged 1 commit into
mainfrom
moshea/physical-ai-manual-bridge

Conversation

@mosheabr
Copy link
Copy Markdown
Collaborator

Summary

One-time content bridge to land 5 Physical AI Skill Hub skills into the catalog while the sync workflow's `GITHUB_TOKEN` gains cross-org read scope for internal NVIDIA-dev repos.

Why manual

The catalog sync currently logs `Clone failed for NVIDIA-dev/physical-ai-skill-hub-dev` on every run (the source repo is `visibility: internal`, default token can't reach it). Components.d/physical-ai-skill-hub.yml is correctly registered (PR #125) but no content has ever landed via the normal mirror path. The 5 skills are all fully 5/5 compliant in source — staging them manually here gets them into the catalog for Computex 6/1 without waiting for token-access fix.

Skills staged

All five with the full artifact set (sig + skill-card + evals + BENCHMARK + SKILL.md) copied directly from `NVIDIA-dev/physical-ai-skill-hub-dev@main`:

Skill sig card evals BENCHMARK
omniverse-cad-to-simready
omniverse-realtime-viewer
omniverse-usd-performance-tuning
physical-ai-infrastructure-setup-and-resilient-scaling
physical-ai-neural-reconstruction

Intentionally excluded from the catalog

Two source skills are excluded by policy and NOT staged:

  • `physical-ai-defect-image-generation`
  • `physical-ai-video-data-augmentation`

Forward-compatibility with the sync workflow

The sync workflow's behavior when its clone fails: it logs the failure and `continue`s to the next component without removing existing catalog content. So this manually-staged content persists across syncs. Once cross-org token access lands, the next sync will overwrite this content with the live source state — which is desirable, since the source is the canonical version.

Test plan

  • DCO + Verify Authors
  • After merge: confirm 5 `skills//` directories visible in catalog
  • Trigger sync — confirm sync still logs "Clone failed" for the source but doesn't drop the manually-staged content

🤖 Generated with Claude Code

One-time content bridge while the catalog sync workflow's GITHUB_TOKEN
gains cross-org read scope for internal NVIDIA-dev repos. Without that
access, the sync logs "Clone failed for NVIDIA-dev/physical-ai-skill-hub-dev"
on every run and these skills cannot land via the normal mirroring path,
despite being fully 5/5 compliant in source.

Skills staged (all sig + skill-card + evals + BENCHMARK + SKILL.md from
the source repo's main branch):

  - omniverse-cad-to-simready
  - omniverse-realtime-viewer
  - omniverse-usd-performance-tuning
  - physical-ai-infrastructure-setup-and-resilient-scaling
  - physical-ai-neural-reconstruction

Two source skills are intentionally excluded from the catalog and NOT
staged here:

  - physical-ai-defect-image-generation (excluded by policy)
  - physical-ai-video-data-augmentation (excluded by policy)

Behavior of the sync workflow with this manual content in place: the
sync will continue to log "Clone failed" for this component and skip
the source-side refresh, but the existing catalog content under
skills/<skill-name>/ is preserved (the sync only writes for successful
clones — it does not remove orphaned content). Once cross-org token
access lands, the next sync will overwrite this manually-staged
content with the live source-of-truth state.

components.d/physical-ai-skill-hub.yml registered the same 5 skills in
PR #125; no yml changes here.

Signed-off-by: Moshe Abramovitch <moshea@nvidia.com>
@mosheabr mosheabr requested a review from sayalinvidia as a code owner May 29, 2026 16:44
@mosheabr mosheabr merged commit 6c6fc09 into main May 29, 2026
4 checks passed
@mosheabr mosheabr deleted the moshea/physical-ai-manual-bridge branch May 29, 2026 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant