physical-ai-neural-reconstruction
Router for NVIDIA NuRec/NRE: USDZ rendering, NCore conversion, 3DGS, gRPC sensor sim, PhysicalAI HF datasets. Do NOT use for SimReady or infra setup.
Security Assessment
About physical-ai-neural-reconstruction
This is a thin "router" skill for NVIDIA's Neural Reconstruction (NuRec) ecosystem. Its job is not to run reconstruction workflows itself but to help an agent figure out which of NVIDIA's five upstream sibling skills — physical-ai-datasets, ncore, nre, asset-harvester, and nurec-fixer — answers a given request, then locate, clone, or refresh the canonical `nurec-skills` checkout from GitHub. It solves the discoverability and orchestration problem in a large, multi-repository toolchain by ordering multi-step NuRec pipelines (data conversion to training to rendering to cleanup) before the agent opens the upstream recipe. By design it never copies or reconstructs the actual commands, which live upstream.
The skill provides picker tables that map user intents to sibling skills, an upstream-fetch recipe that uses only `git`, workflow ordering guidance, a "mix-ups" reference clarifying easily-confused concepts (NuRec vs NRE, built-in Difix vs standalone DiffusionHarmonizer, ncore vs nre ordering), maintenance notes for keeping the router in sync, and safe secret-verification steps (checking that tokens are present without echoing their values). It ships a benchmark report (BENCHMARK.md) documenting NVSkills-Eval results across security, correctness, discoverability, effectiveness, and efficiency.
The intended users are teams working with NVIDIA Physical AI, autonomous-vehicle simulation, and novel-view-synthesis pipelines who need to navigate NuRec tooling. Downstream execution requires Docker, the NVIDIA Container Toolkit, a GPU, an NGC API key, a Hugging Face token with gated PhysicalAI licenses accepted, and Python 3.10+ with huggingface_hub; optional CARLA/Isaac Sim/AlpaSim integration is supported over gRPC.
FAQ
Does this skill actually run neural reconstruction?
No. It is explicitly a thin router. It only helps identify which upstream NVIDIA sibling skill answers a NuRec question and helps clone or refresh the canonical nurec-skills checkout. The real training, rendering, and conversion commands live in the upstream sibling skills.
What prerequisites do I need?
The router itself only needs git. Downstream sibling skills require Docker plus the NVIDIA Container Toolkit and a GPU, an NGC API key for pulling containers, a Hugging Face token with the gated PhysicalAI/DiffusionHarmonizer licenses accepted in advance, and Python 3.10+ with huggingface_hub installed.
When should I NOT use this skill?
Do not use it for SimReady packaging of CAD or meshes, generic USD performance tuning unrelated to NuRec, or AKS/OSMO/NIM infrastructure setup — the skill names dedicated alternatives for each of those.
How are secrets handled?
The skill verifies credentials safely by checking that tokens such as HF_TOKEN are present without echoing their values, and it references a dedicated secrets-handling guide. There is no exfiltration of credentials.
How do I keep the router accurate over time?
The maintenance reference treats the upstream nurec-index skill as authoritative and describes updating the picker tables, sibling-skills table, and workflow ordering whenever upstream adds or renames sibling skills.
All Files
11 filesInstall physical-ai-neural-reconstruction
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
nvidia/skills