[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FM7648SDZXFVAVX0Y2ZTP":3,"skill-same:01M79FM7648SDZXFVAVX0Y2ZTP":131},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":38,"commitSha":68,"skillDirectory":69,"forksCount":14,"repositoryHtmlUrl":70,"repositoryHomepageUrl":6,"ownerHtmlUrl":71,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":72,"install":73,"resources":86},"01M79FM7648SDZXFVAVX0Y2ZTP","physical-ai-neural-reconstruction",null,"Router for NVIDIA NuRec\u002FNRE: USDZ rendering, NCore conversion, 3DGS, gRPC sensor sim, PhysicalAI HF datasets. Do NOT use for SimReady or infra setup.","Elogic360\u002Fsoftware-factory","Elogic360","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F156535519?v=4","01M74NH3F0RB13PWB7JZDE2V80","elogic360","01M74NH3FPC65082MDZVMFHDM3",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: physical-ai-neural-reconstruction\ndescription: \"Router for NVIDIA NuRec\u002FNRE: USDZ rendering, NCore conversion, 3DGS, gRPC sensor sim, PhysicalAI HF datasets. Do NOT use for SimReady or infra setup.\"\nlicense: Apache-2.0\nversion: \"0.3.0\"\ntools:\n  - Read\n  - Shell\ncompatibility: >-\n  Router skill; downstream sibling skills require Docker, NVIDIA Container\n  Toolkit, GPU, NGC API key, Hugging Face token with PhysicalAI gated\n  licenses accepted, Python 3.10+, and `huggingface_hub`. Optional:\n  CARLA \u002F Isaac Sim 5.1 \u002F AlpaSim for simulator integration over\n  `serve-grpc`.\nmetadata:\n  author: NVIDIA Physical AI\n  tags:\n    - physical-ai\n    - nurec\n    - neural-reconstruction\n    - router\n    - sensor-sim\n  upstream:\n    repo: https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnurec-skills\n    branch: main\n    skills_dir: .agents\u002Fskills\u002F\n    skills_dir_alias: skills\u002F\n    index_skill: .agents\u002Fskills\u002FSKILL.md\n    index_skill_name: nurec-index\n    sibling_skills:\n      - name: physical-ai-datasets\n        folder: physical-ai-datasets\u002F\n        upstream: https:\u002F\u002Fhuggingface.co\u002Fnvidia\n      - name: ncore\n        folder: ncore\u002F\n        upstream: https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fncore\n      - name: nre\n        folder: nre\u002F\n        upstream: nvcr.io\u002Fnvidia\u002Fnre\u002Fnre\n      - name: asset-harvester\n        folder: asset-harvester\u002F\n        upstream: https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fasset-harvester\n      - name: nurec-fixer\n        folder: nurec-fixer\u002F\n        upstream: https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fharmonizer\n        hf_model: https:\u002F\u002Fhuggingface.co\u002Fnvidia\u002FDiffusionHarmonizer\n  upstream_clone_path: \"${PHYSICAL_AI_SKILL_HUB_UPSTREAM_ROOT:-$HOME\u002F.physical-ai-skill-hub\u002Fupstreams}\u002Fnurec-skills\"\n  upstream_override_env: NUREC_SKILLS_UPSTREAM_ROOT\n---\n\n# Physical AI Neural Reconstruction (NuRec) Router\n\n## Purpose\n\nThis is a **thin router** for NVIDIA Neural Reconstruction (NuRec)\nrequests. It points at the upstream `nurec-index` skill at\n`https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnurec-skills` and its five sibling skills\n(`physical-ai-datasets`, `ncore`, `nre`, `asset-harvester`,\n`nurec-fixer`). Use this skill to:\n\n- Identify which upstream sibling skill answers a NuRec question.\n- Locate, clone, or refresh the canonical `nurec-skills` checkout.\n- Order multi-step NuRec workflows (data → conversion → train →\n  render → cleanup) before opening the upstream recipe.\n\nThe canonical recipes (training, rendering, data conversion, dataset\ndownloads, object harvesting, frame cleanup) live in the upstream\nsibling skills. **Never copy or reconstruct their commands here.**\n\n**Do NOT use this skill for:**\n\n- SimReady packaging of CAD or source meshes → use\n  `omniverse-cad-to-simready`.\n- Generic USD performance tuning unrelated to NuRec → use\n  `omniverse-usd-performance-tuning`.\n- AKS \u002F OSMO \u002F NIM Operator infrastructure setup → use\n  `physical-ai-infrastructure-setup-and-resilient-scaling`.\n\n## When to Use\n\nRead this skill **first** whenever a user mentions any of:\n\n`nurec`, `nurec router`, `nurec index`, `neural reconstruction`,\n`neural reconstruction engine`, `NRE`, `3DGUT`, `3DGRT`, `USDZ`,\n`NCore V4`, `sensor sim`, `novel view synthesis`,\n`PhysicalAI-Autonomous-Vehicles-NuRec`, `PhysicalAI-NuRec-PPISP`,\n`Cosmos-Drive-Dreams`, `asset harvester`, `nurec fixer`,\n`DiffusionHarmonizer`, `harmonizer`, `difix`, `difix3d`, `serve-grpc`,\n`render-grpc`, `warm serve-grpc`, `nre thin client`, `batch_render_rgb`,\n`nurec teardown`, \"where do I start with NuRec\", \"which NuRec skill\nshould I use for X?\".\n\nDecide which upstream sibling skill answers the question, fetch it\n(see [Locate and fetch the upstream skills](#locate-and-fetch-the-upstream-skills)),\nthen follow that skill's body.\n\n## Prerequisites\n\nRouter skill itself has no runtime prerequisites beyond `git` for\nfetching the upstream. Downstream sibling skills require:\n\n- **Docker + NVIDIA Container Toolkit + GPU** — for `nre`, `nre-tools`,\n  and `nurec-fixer` containers\n  (`nvcr.io\u002Fnvidia\u002Fnre\u002Fnre`, `nvcr.io\u002Fnvidia\u002Fnre\u002Fnre-tools`,\n  `nvcr.io\u002Fnvidia\u002Fcosmos\u002Fcosmos-predict2-container:1.2`).\n- **NGC API key** (`NGC_API_KEY`) — for pulling NGC containers.\n- **Hugging Face token** (`HF_TOKEN`) with the\n  `nvidia\u002FPhysicalAI-*`, `nvidia\u002FDiffusionHarmonizer`, and\n  `nvidia\u002Fasset-harvester` gated licenses **accepted in advance** on\n  Hugging Face.\n- **Python 3.10+** with `huggingface_hub` installed.\n- **(Optional)** CARLA, Isaac Sim 5.1, or AlpaSim for simulator\n  integration over `serve-grpc`.\n\nVerify secrets safely (do not echo values):\n\n```bash\nhf auth whoami\n[ -n \"${HF_TOKEN:-}\" ]      && echo \"HF_TOKEN length=${#HF_TOKEN}\"      || echo \"HF_TOKEN unset\"\n[ -n \"${NGC_API_KEY:-}\" ]   && echo \"NGC_API_KEY length=${#NGC_API_KEY}\" || echo \"NGC_API_KEY unset\"\n```\n\nSee [`references\u002Fsecrets-handling.md`](references\u002Fsecrets-handling.md)\nfor the bash anti-patterns to avoid.\n\n## What is NuRec?\n\n**NuRec** (NVIDIA Omniverse Neural Reconstruction) takes camera, LiDAR,\nradar, or stereo recordings — typically from a self-driving car or a\nrobot — and turns them into a 3D scene you can re-render from any\nviewpoint. Names that come up a lot:\n\n- **NRE** — \"Neural Reconstruction Engine\". NuRec is the product; NRE\n  is the engine that trains and renders. Both route to the upstream\n  `nre` skill.\n- **USDZ** — the file format of a trained scene. A zip archive that\n  Omniverse, Isaac Sim, and CARLA can open.\n- **NCore V4** — the input format NRE consumes. Raw recordings must be\n  converted to NCore V4 before training.\n- **3DGUT \u002F 3DGRT** — the two 3D Gaussian Splatting flavours used\n  internally by NRE. The default Hydra recipe picks one; most users\n  never set it manually.\n\nA typical NuRec project has three stages:\n\n1. **Get the input** — convert your own recording to NCore V4\n   (`ncore`), or download a pre-converted dataset\n   (`physical-ai-datasets`).\n2. **Train the reconstruction** — feed NCore V4 to NRE; out comes a\n   USDZ (`nre`).\n3. **Render new views** — render images, videos, or LiDAR sweeps from\n   the USDZ (`nre`).\n\nProjects that just want to *use* an existing NVIDIA-published scene\nskip step 2.\n\n## Pick a skill\n\nMatch the user's goal in the left column and open the named upstream\nskill on the right. Arrows mean \"do these in order\".\n\n| I want to… | Upstream skill |\n|------------|----------------|\n| Find or download a NuRec dataset NVIDIA has published | `physical-ai-datasets` |\n| Convert my own camera \u002F LiDAR \u002F radar \u002F depth \u002F stereo recording into NCore V4 | `ncore` |\n| Write a new converter for an unsupported sensor setup (drone, RGB-D, ROS 2 bag, COLMAP, ScanNet++) | `ncore` |\n| Train a 3D reconstruction from an NCore clip | `ncore` → `nre` |\n| Generate the extra inputs NRE needs (segmentation masks, depth, ego mask) | `nre` (uses the `nre-tools` container) |\n| Render a USDZ along the original camera positions | `nre` |\n| Render at full resolution \u002F highest quality | `nre` (see \"Quality presets\") |\n| Render along a shifted trajectory (e.g. car moved 3 m left) | `nre` |\n| Render through a server so CARLA \u002F Isaac Sim \u002F AlpaSim \u002F a custom simulator can ask for frames | `nre` (`serve-grpc`) |\n| Render the same USDZ many times back-to-back from Python with minimal per-call latency | `nre` (warm `serve-grpc` + thin Python client \u002F `batch_render_rgb`) |\n| Render LiDAR sweeps (point clouds) from a USDZ | `nre` (`render-grpc --lidar`) |\n| Skip training and just render a NuRec scene NVIDIA already built | `physical-ai-datasets` → `nre` |\n| Extract individual 3D objects (cars, pedestrians) from a driving clip | `asset-harvester` |\n| Add, remove, or replace cars \u002F pedestrians in a NuRec scene | `asset-harvester` → `nre` |\n| Clean up or harmonize rendered frames (ghosting, floaters, flicker, lighting\u002Fshadows) | `nurec-fixer`, **or** `--enable-difix` inside `nre` for inline rendering |\n| Export the scene as a PLY, mesh, depth maps, ego mask, etc. | `nre` |\n| Upgrade an old USDZ so newer NRE versions load it faster | `nre` (`upgrade-artifact`) |\n| Open a USDZ or PLY in a browser viewer | `nre` (`viewer` \u002F `ply_viewer`) |\n| Measure rendering quality (PSNR, SSIM, LPIPS) against ground truth | `nre` (`eval-rendering-metrics`) |\n| Benchmark different reconstruction methods on the same scenes | `physical-ai-datasets` (`PhysicalAI-NuRec-PPISP`) → `nre` |\n| Train on multiple GPUs or on SLURM | `nre` (Workflow D) |\n\n## Common workflows\n\nSix end-to-end workflows are documented in\n[`references\u002Fworkflows.md`](references\u002Fworkflows.md):\n\n- **A.** Make a NuRec scene from your own recording.\n- **B.** Use a NuRec scene NVIDIA has already trained.\n- **C.** Add, remove, or replace 3D objects in a scene.\n- **D.** Clean up rendered frames.\n- **E.** Benchmark reconstruction quality.\n- **F.** Connect NuRec to a simulator.\n\nOpen that file when the user's task spans more than one sibling skill.\n\n## Sibling skills (upstream)\n\n| Name | Upstream folder | What it does |\n|------|-----------------|--------------|\n| `physical-ai-datasets` | `.agents\u002Fskills\u002Fphysical-ai-datasets\u002F` | Catalog and download recipes for every NVIDIA Physical AI dataset on Hugging Face (driving, robotics, manipulation, NuRec scenes, benchmarks). |\n| `ncore` | `.agents\u002Fskills\u002Fncore\u002F` | Converts any sensor recording to NCore V4 (the format NRE needs). Also covers writing a new converter. |\n| `nre` | `.agents\u002Fskills\u002Fnre\u002F` | The Neural Reconstruction Engine itself. Trains, renders (locally, via warm `serve-grpc` + thin Python client \u002F `batch_render_rgb`, or to an external simulator), exports meshes \u002F point clouds \u002F depth, edits actors, evaluates quality. |\n| `asset-harvester` | `.agents\u002Fskills\u002Fasset-harvester\u002F` | Open-source Apache-2.0 pipeline that extracts individual 3D objects from sparse views in a driving clip and saves them as `.ply` Gaussian splats with metadata. |\n| `nurec-fixer` | `.agents\u002Fskills\u002Fnurec-fixer\u002F` | Standalone NVIDIA **DiffusionHarmonizer** workflow — public successor to the older Fixer \u002F Difix3D+ recipes — that cleans rendered frames, harmonizes inserted actors, evaluates PSNR\u002FLPIPS, and optionally fine-tunes the model. |\n\nFor naming overlaps (NRE vs Fixer, ncore vs nre, AV-NuRec vs\nCosmos-Drive-Dreams, NuRec vs SimReady) see\n[`references\u002Fmix-ups.md`](references\u002Fmix-ups.md).\n\n## Locate and fetch the upstream skills\n\nQuick recipe (full version in\n[`references\u002Fupstream-fetch.md`](references\u002Fupstream-fetch.md)):\n\n```bash\nUPSTREAM_ROOT=\"${NUREC_SKILLS_UPSTREAM_ROOT:-${PHYSICAL_AI_SKILL_HUB_UPSTREAM_ROOT:-$HOME\u002F.physical-ai-skill-hub\u002Fupstreams}}\"\nmkdir -p \"$UPSTREAM_ROOT\"\nif [ -d \"$UPSTREAM_ROOT\u002Fnurec-skills\u002F.git\" ]; then\n  git -C \"$UPSTREAM_ROOT\u002Fnurec-skills\" fetch --tags\n  git -C \"$UPSTREAM_ROOT\u002Fnurec-skills\" checkout main\n  git -C \"$UPSTREAM_ROOT\u002Fnurec-skills\" pull --ff-only\nelse\n  git clone --depth 1 https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnurec-skills.git \\\n    \"$UPSTREAM_ROOT\u002Fnurec-skills\"\nfi\ntest -f \"$UPSTREAM_ROOT\u002Fnurec-skills\u002F.agents\u002Fskills\u002FSKILL.md\"\n```\n\nThen read the upstream skill before running any mutating command:\n\n```bash\ncat \"$UPSTREAM_ROOT\u002Fnurec-skills\u002F.agents\u002Fskills\u002FSKILL.md\"          # router\ncat \"$UPSTREAM_ROOT\u002Fnurec-skills\u002F.agents\u002Fskills\u002F\u003Cfolder>\u002FSKILL.md\" # sibling\n```\n\nLocal lookup order (try in order before the upstream clone):\n\n1. `.agents\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (Cursor, Codex, NemoClaw)\n2. `.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (Claude Code)\n3. `.cursor\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (project-scoped)\n4. `~\u002F.cursor\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (personal skills)\n\n## Hard Rules\n\n- Router only — do not duplicate upstream NuRec recipes here. Read\n  the upstream sibling skill body before running any mutating command.\n- Refer to sibling skills by their `name:` (e.g. `nre`), not by repo\n  path. Folder layouts can change; the name is portable.\n- Clone or refresh `https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnurec-skills` under the\n  shared upstream root\n  (`${NUREC_SKILLS_UPSTREAM_ROOT:-${PHYSICAL_AI_SKILL_HUB_UPSTREAM_ROOT:-$HOME\u002F.physical-ai-skill-hub\u002Fupstreams}}\u002Fnurec-skills`).\n  Do not scan broad developer workspaces such as `~\u002FCodes` or reuse\n  unrelated old clones.\n- `physical-ai-datasets` covers gated Hugging Face datasets. Do not\n  bypass dataset license terms; the user must accept the\n  `PhysicalAI-*` gated licenses on Hugging Face and provide a token\n  before downloading.\n- Asset Harvester runs **before** packaging into a USDZ. Do not call\n  `nre`'s `export-external-assets` on hand-rolled `.ply` files unless\n  the user explicitly asks to skip Asset Harvester.\n- For artifact cleanup, prefer the built-in `--enable-difix` path in\n  `nre`. Route to the standalone `nurec-fixer` only when the user\n  needs the public code\u002Fmodel card, paired evaluation, fine-tuning,\n  or fixes on previously rendered frames.\n- Do not invent NRE \u002F NCore \u002F DiffusionHarmonizer commands from\n  memory. Re-read the upstream sibling skill — versions move fast\n  (NRE `release_26.04` is the current pinned tag).\n- This router does not deploy infrastructure. Route AKS \u002F OSMO \u002F\n  NIM Operator setup to\n  `physical-ai-infrastructure-setup-and-resilient-scaling`.\n\n## Limitations\n\n- **Router only.** This skill never executes mutating NuRec commands.\n  All training, rendering, conversion, and harmonization happens in\n  upstream sibling skills.\n- **Upstream-pinned.** Recipes live in\n  `https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnurec-skills`, which evolves outside\n  this repo. Stale clones can drift; always `git pull` the upstream\n  before relying on a sibling skill.\n- **Gated content.** `nvidia\u002FPhysicalAI-*`, `nvidia\u002FDiffusionHarmonizer`,\n  and `nvidia\u002Fasset-harvester` require the user to accept license\n  terms on Hugging Face first. The router cannot bypass this.\n- **Heavy footprint.** A complete NuRec workflow can leave 150 GB+\n  on disk. See [`references\u002Fteardown.md`](references\u002Fteardown.md).\n- **NVIDIA-only stack.** Requires an NVIDIA GPU plus the NVIDIA\n  Container Toolkit. AMD \u002F Intel \u002F Apple Silicon are not supported.\n- **Not a SimReady pipeline.** NuRec produces a renderable USDZ from\n  a recording; SimReady packaging of CAD or source meshes is a\n  different pipeline (see `omniverse-cad-to-simready`).\n\n## Troubleshooting\n\n| Error \u002F symptom | Likely cause | Solution |\n|-----------------|--------------|----------|\n| `nurec-skills` clone missing or empty | Upstream not fetched yet | Run the clone block in [Locate and fetch the upstream skills](#locate-and-fetch-the-upstream-skills) |\n| `403`\u002F`401` pulling `nvidia\u002FPhysicalAI-*` from HF | Gated license not accepted, or `HF_TOKEN` unset \u002F wrong scope | Accept the gated license on Hugging Face, then `hf auth login` with a token that has `read` access |\n| `denied: requested access to the resource is denied` from `nvcr.io\u002Fnvidia\u002Fnre\u002F*` | Missing or expired `NGC_API_KEY` | `docker login nvcr.io` with `$oauthtoken` \u002F `NGC_API_KEY`; rotate the key at `org.ngc.nvidia.com\u002Fsetup\u002Fapi-key` if needed |\n| NRE refuses to load a clip (\"not valid NCore V4\") | Recording was not converted | Run the `ncore` skill before invoking `nre` |\n| `serve-grpc` cold-start latency dominates a Python loop | One-shot Docker invocation per render | Use the `nre` warm `serve-grpc` + thin Python client (`batch_render_rgb`) recipe |\n| Output files are owned by `root` after a `docker run` | `-u $(id -u):$(id -g)` was missing | `sudo chown -R \"$(id -u):$(id -g)\" \u003Coutput_dir>`; add the `-u` flag next time |\n| Frames have ghosting \u002F floaters \u002F flicker after rendering | Inline cleanup not enabled | Re-render with `nre --enable-difix`, or post-process with `nurec-fixer` (DiffusionHarmonizer) |\n| Stale skill names (`ncore-data-conversion`, old `nvidia\u002FFixer`) in agent output | Out-of-date cached skill | Update references to `ncore` and `nurec-fixer` (DiffusionHarmonizer); see [`references\u002Fmaintenance.md`](references\u002Fmaintenance.md) |\n| Bash anti-pattern `${HF_TOKEN:+yes}${HF_TOKEN:-no}` echoed token value | Misuse of bash parameter expansion | Rotate the token; use `hf auth whoami` or length-only checks (see [`references\u002Fsecrets-handling.md`](references\u002Fsecrets-handling.md)) |\n\n## Cross-skill teardown\n\nA complete NuRec workflow can leave **150 GB+** on disk between\ncontainer images, model weights, code clones, conda envs, and output\ndirectories. Each sibling skill has its own dedicated `Teardown`\nsection — read them in the order documented in\n[`references\u002Fteardown.md`](references\u002Fteardown.md) when the user no\nlonger needs the workflow.\n\n## Keeping this router up to date\n\nProcedure for adding new sibling skills, renames, or upstream URL\nchanges lives in [`references\u002Fmaintenance.md`](references\u002Fmaintenance.md).\nTreat the upstream `nurec-index` at\n\u003Chttps:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnurec-skills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002FSKILL.md>\nas authoritative; this skill mirrors only the picker tables, the\nworkflow ordering, and the upstream fetch recipe.\n","# Physical AI Neural Reconstruction (NuRec) Router\n\n## Purpose\n\nThis is a **thin router** for NVIDIA Neural Reconstruction (NuRec)\nrequests. It points at the upstream `nurec-index` skill at\n`https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnurec-skills` and its five sibling skills\n(`physical-ai-datasets`, `ncore`, `nre`, `asset-harvester`,\n`nurec-fixer`). Use this skill to:\n\n- Identify which upstream sibling skill answers a NuRec question.\n- Locate, clone, or refresh the canonical `nurec-skills` checkout.\n- Order multi-step NuRec workflows (data → conversion → train →\n  render → cleanup) before opening the upstream recipe.\n\nThe canonical recipes (training, rendering, data conversion, dataset\ndownloads, object harvesting, frame cleanup) live in the upstream\nsibling skills. **Never copy or reconstruct their commands here.**\n\n**Do NOT use this skill for:**\n\n- SimReady packaging of CAD or source meshes → use\n  `omniverse-cad-to-simready`.\n- Generic USD performance tuning unrelated to NuRec → use\n  `omniverse-usd-performance-tuning`.\n- AKS \u002F OSMO \u002F NIM Operator infrastructure setup → use\n  `physical-ai-infrastructure-setup-and-resilient-scaling`.\n\n## When to Use\n\nRead this skill **first** whenever a user mentions any of:\n\n`nurec`, `nurec router`, `nurec index`, `neural reconstruction`,\n`neural reconstruction engine`, `NRE`, `3DGUT`, `3DGRT`, `USDZ`,\n`NCore V4`, `sensor sim`, `novel view synthesis`,\n`PhysicalAI-Autonomous-Vehicles-NuRec`, `PhysicalAI-NuRec-PPISP`,\n`Cosmos-Drive-Dreams`, `asset harvester`, `nurec fixer`,\n`DiffusionHarmonizer`, `harmonizer`, `difix`, `difix3d`, `serve-grpc`,\n`render-grpc`, `warm serve-grpc`, `nre thin client`, `batch_render_rgb`,\n`nurec teardown`, \"where do I start with NuRec\", \"which NuRec skill\nshould I use for X?\".\n\nDecide which upstream sibling skill answers the question, fetch it\n(see [Locate and fetch the upstream skills](#locate-and-fetch-the-upstream-skills)),\nthen follow that skill's body.\n\n## Prerequisites\n\nRouter skill itself has no runtime prerequisites beyond `git` for\nfetching the upstream. Downstream sibling skills require:\n\n- **Docker + NVIDIA Container Toolkit + GPU** — for `nre`, `nre-tools`,\n  and `nurec-fixer` containers\n  (`nvcr.io\u002Fnvidia\u002Fnre\u002Fnre`, `nvcr.io\u002Fnvidia\u002Fnre\u002Fnre-tools`,\n  `nvcr.io\u002Fnvidia\u002Fcosmos\u002Fcosmos-predict2-container:1.2`).\n- **NGC API key** (`NGC_API_KEY`) — for pulling NGC containers.\n- **Hugging Face token** (`HF_TOKEN`) with the\n  `nvidia\u002FPhysicalAI-*`, `nvidia\u002FDiffusionHarmonizer`, and\n  `nvidia\u002Fasset-harvester` gated licenses **accepted in advance** on\n  Hugging Face.\n- **Python 3.10+** with `huggingface_hub` installed.\n- **(Optional)** CARLA, Isaac Sim 5.1, or AlpaSim for simulator\n  integration over `serve-grpc`.\n\nVerify secrets safely (do not echo values):\n\n```bash\nhf auth whoami\n[ -n \"${HF_TOKEN:-}\" ]      && echo \"HF_TOKEN length=${#HF_TOKEN}\"      || echo \"HF_TOKEN unset\"\n[ -n \"${NGC_API_KEY:-}\" ]   && echo \"NGC_API_KEY length=${#NGC_API_KEY}\" || echo \"NGC_API_KEY unset\"\n```\n\nSee [`references\u002Fsecrets-handling.md`](references\u002Fsecrets-handling.md)\nfor the bash anti-patterns to avoid.\n\n## What is NuRec?\n\n**NuRec** (NVIDIA Omniverse Neural Reconstruction) takes camera, LiDAR,\nradar, or stereo recordings — typically from a self-driving car or a\nrobot — and turns them into a 3D scene you can re-render from any\nviewpoint. Names that come up a lot:\n\n- **NRE** — \"Neural Reconstruction Engine\". NuRec is the product; NRE\n  is the engine that trains and renders. Both route to the upstream\n  `nre` skill.\n- **USDZ** — the file format of a trained scene. A zip archive that\n  Omniverse, Isaac Sim, and CARLA can open.\n- **NCore V4** — the input format NRE consumes. Raw recordings must be\n  converted to NCore V4 before training.\n- **3DGUT \u002F 3DGRT** — the two 3D Gaussian Splatting flavours used\n  internally by NRE. The default Hydra recipe picks one; most users\n  never set it manually.\n\nA typical NuRec project has three stages:\n\n1. **Get the input** — convert your own recording to NCore V4\n   (`ncore`), or download a pre-converted dataset\n   (`physical-ai-datasets`).\n2. **Train the reconstruction** — feed NCore V4 to NRE; out comes a\n   USDZ (`nre`).\n3. **Render new views** — render images, videos, or LiDAR sweeps from\n   the USDZ (`nre`).\n\nProjects that just want to *use* an existing NVIDIA-published scene\nskip step 2.\n\n## Pick a skill\n\nMatch the user's goal in the left column and open the named upstream\nskill on the right. Arrows mean \"do these in order\".\n\n| I want to… | Upstream skill |\n|------------|----------------|\n| Find or download a NuRec dataset NVIDIA has published | `physical-ai-datasets` |\n| Convert my own camera \u002F LiDAR \u002F radar \u002F depth \u002F stereo recording into NCore V4 | `ncore` |\n| Write a new converter for an unsupported sensor setup (drone, RGB-D, ROS 2 bag, COLMAP, ScanNet++) | `ncore` |\n| Train a 3D reconstruction from an NCore clip | `ncore` → `nre` |\n| Generate the extra inputs NRE needs (segmentation masks, depth, ego mask) | `nre` (uses the `nre-tools` container) |\n| Render a USDZ along the original camera positions | `nre` |\n| Render at full resolution \u002F highest quality | `nre` (see \"Quality presets\") |\n| Render along a shifted trajectory (e.g. car moved 3 m left) | `nre` |\n| Render through a server so CARLA \u002F Isaac Sim \u002F AlpaSim \u002F a custom simulator can ask for frames | `nre` (`serve-grpc`) |\n| Render the same USDZ many times back-to-back from Python with minimal per-call latency | `nre` (warm `serve-grpc` + thin Python client \u002F `batch_render_rgb`) |\n| Render LiDAR sweeps (point clouds) from a USDZ | `nre` (`render-grpc --lidar`) |\n| Skip training and just render a NuRec scene NVIDIA already built | `physical-ai-datasets` → `nre` |\n| Extract individual 3D objects (cars, pedestrians) from a driving clip | `asset-harvester` |\n| Add, remove, or replace cars \u002F pedestrians in a NuRec scene | `asset-harvester` → `nre` |\n| Clean up or harmonize rendered frames (ghosting, floaters, flicker, lighting\u002Fshadows) | `nurec-fixer`, **or** `--enable-difix` inside `nre` for inline rendering |\n| Export the scene as a PLY, mesh, depth maps, ego mask, etc. | `nre` |\n| Upgrade an old USDZ so newer NRE versions load it faster | `nre` (`upgrade-artifact`) |\n| Open a USDZ or PLY in a browser viewer | `nre` (`viewer` \u002F `ply_viewer`) |\n| Measure rendering quality (PSNR, SSIM, LPIPS) against ground truth | `nre` (`eval-rendering-metrics`) |\n| Benchmark different reconstruction methods on the same scenes | `physical-ai-datasets` (`PhysicalAI-NuRec-PPISP`) → `nre` |\n| Train on multiple GPUs or on SLURM | `nre` (Workflow D) |\n\n## Common workflows\n\nSix end-to-end workflows are documented in\n[`references\u002Fworkflows.md`](references\u002Fworkflows.md):\n\n- **A.** Make a NuRec scene from your own recording.\n- **B.** Use a NuRec scene NVIDIA has already trained.\n- **C.** Add, remove, or replace 3D objects in a scene.\n- **D.** Clean up rendered frames.\n- **E.** Benchmark reconstruction quality.\n- **F.** Connect NuRec to a simulator.\n\nOpen that file when the user's task spans more than one sibling skill.\n\n## Sibling skills (upstream)\n\n| Name | Upstream folder | What it does |\n|------|-----------------|--------------|\n| `physical-ai-datasets` | `.agents\u002Fskills\u002Fphysical-ai-datasets\u002F` | Catalog and download recipes for every NVIDIA Physical AI dataset on Hugging Face (driving, robotics, manipulation, NuRec scenes, benchmarks). |\n| `ncore` | `.agents\u002Fskills\u002Fncore\u002F` | Converts any sensor recording to NCore V4 (the format NRE needs). Also covers writing a new converter. |\n| `nre` | `.agents\u002Fskills\u002Fnre\u002F` | The Neural Reconstruction Engine itself. Trains, renders (locally, via warm `serve-grpc` + thin Python client \u002F `batch_render_rgb`, or to an external simulator), exports meshes \u002F point clouds \u002F depth, edits actors, evaluates quality. |\n| `asset-harvester` | `.agents\u002Fskills\u002Fasset-harvester\u002F` | Open-source Apache-2.0 pipeline that extracts individual 3D objects from sparse views in a driving clip and saves them as `.ply` Gaussian splats with metadata. |\n| `nurec-fixer` | `.agents\u002Fskills\u002Fnurec-fixer\u002F` | Standalone NVIDIA **DiffusionHarmonizer** workflow — public successor to the older Fixer \u002F Difix3D+ recipes — that cleans rendered frames, harmonizes inserted actors, evaluates PSNR\u002FLPIPS, and optionally fine-tunes the model. |\n\nFor naming overlaps (NRE vs Fixer, ncore vs nre, AV-NuRec vs\nCosmos-Drive-Dreams, NuRec vs SimReady) see\n[`references\u002Fmix-ups.md`](references\u002Fmix-ups.md).\n\n## Locate and fetch the upstream skills\n\nQuick recipe (full version in\n[`references\u002Fupstream-fetch.md`](references\u002Fupstream-fetch.md)):\n\n```bash\nUPSTREAM_ROOT=\"${NUREC_SKILLS_UPSTREAM_ROOT:-${PHYSICAL_AI_SKILL_HUB_UPSTREAM_ROOT:-$HOME\u002F.physical-ai-skill-hub\u002Fupstreams}}\"\nmkdir -p \"$UPSTREAM_ROOT\"\nif [ -d \"$UPSTREAM_ROOT\u002Fnurec-skills\u002F.git\" ]; then\n  git -C \"$UPSTREAM_ROOT\u002Fnurec-skills\" fetch --tags\n  git -C \"$UPSTREAM_ROOT\u002Fnurec-skills\" checkout main\n  git -C \"$UPSTREAM_ROOT\u002Fnurec-skills\" pull --ff-only\nelse\n  git clone --depth 1 https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnurec-skills.git \\\n    \"$UPSTREAM_ROOT\u002Fnurec-skills\"\nfi\ntest -f \"$UPSTREAM_ROOT\u002Fnurec-skills\u002F.agents\u002Fskills\u002FSKILL.md\"\n```\n\nThen read the upstream skill before running any mutating command:\n\n```bash\ncat \"$UPSTREAM_ROOT\u002Fnurec-skills\u002F.agents\u002Fskills\u002FSKILL.md\"          # router\ncat \"$UPSTREAM_ROOT\u002Fnurec-skills\u002F.agents\u002Fskills\u002F\u003Cfolder>\u002FSKILL.md\" # sibling\n```\n\nLocal lookup order (try in order before the upstream clone):\n\n1. `.agents\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (Cursor, Codex, NemoClaw)\n2. `.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (Claude Code)\n3. `.cursor\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (project-scoped)\n4. `~\u002F.cursor\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (personal skills)\n\n## Hard Rules\n\n- Router only — do not duplicate upstream NuRec recipes here. Read\n  the upstream sibling skill body before running any mutating command.\n- Refer to sibling skills by their `name:` (e.g. `nre`), not by repo\n  path. Folder layouts can change; the name is portable.\n- Clone or refresh `https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnurec-skills` under the\n  shared upstream root\n  (`${NUREC_SKILLS_UPSTREAM_ROOT:-${PHYSICAL_AI_SKILL_HUB_UPSTREAM_ROOT:-$HOME\u002F.physical-ai-skill-hub\u002Fupstreams}}\u002Fnurec-skills`).\n  Do not scan broad developer workspaces such as `~\u002FCodes` or reuse\n  unrelated old clones.\n- `physical-ai-datasets` covers gated Hugging Face datasets. Do not\n  bypass dataset license terms; the user must accept the\n  `PhysicalAI-*` gated licenses on Hugging Face and provide a token\n  before downloading.\n- Asset Harvester runs **before** packaging into a USDZ. Do not call\n  `nre`'s `export-external-assets` on hand-rolled `.ply` files unless\n  the user explicitly asks to skip Asset Harvester.\n- For artifact cleanup, prefer the built-in `--enable-difix` path in\n  `nre`. Route to the standalone `nurec-fixer` only when the user\n  needs the public code\u002Fmodel card, paired evaluation, fine-tuning,\n  or fixes on previously rendered frames.\n- Do not invent NRE \u002F NCore \u002F DiffusionHarmonizer commands from\n  memory. Re-read the upstream sibling skill — versions move fast\n  (NRE `release_26.04` is the current pinned tag).\n- This router does not deploy infrastructure. Route AKS \u002F OSMO \u002F\n  NIM Operator setup to\n  `physical-ai-infrastructure-setup-and-resilient-scaling`.\n\n## Limitations\n\n- **Router only.** This skill never executes mutating NuRec commands.\n  All training, rendering, conversion, and harmonization happens in\n  upstream sibling skills.\n- **Upstream-pinned.** Recipes live in\n  `https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnurec-skills`, which evolves outside\n  this repo. Stale clones can drift; always `git pull` the upstream\n  before relying on a sibling skill.\n- **Gated content.** `nvidia\u002FPhysicalAI-*`, `nvidia\u002FDiffusionHarmonizer`,\n  and `nvidia\u002Fasset-harvester` require the user to accept license\n  terms on Hugging Face first. The router cannot bypass this.\n- **Heavy footprint.** A complete NuRec workflow can leave 150 GB+\n  on disk. See [`references\u002Fteardown.md`](references\u002Fteardown.md).\n- **NVIDIA-only stack.** Requires an NVIDIA GPU plus the NVIDIA\n  Container Toolkit. AMD \u002F Intel \u002F Apple Silicon are not supported.\n- **Not a SimReady pipeline.** NuRec produces a renderable USDZ from\n  a recording; SimReady packaging of CAD or source meshes is a\n  different pipeline (see `omniverse-cad-to-simready`).\n\n## Troubleshooting\n\n| Error \u002F symptom | Likely cause | Solution |\n|-----------------|--------------|----------|\n| `nurec-skills` clone missing or empty | Upstream not fetched yet | Run the clone block in [Locate and fetch the upstream skills](#locate-and-fetch-the-upstream-skills) |\n| `403`\u002F`401` pulling `nvidia\u002FPhysicalAI-*` from HF | Gated license not accepted, or `HF_TOKEN` unset \u002F wrong scope | Accept the gated license on Hugging Face, then `hf auth login` with a token that has `read` access |\n| `denied: requested access to the resource is denied` from `nvcr.io\u002Fnvidia\u002Fnre\u002F*` | Missing or expired `NGC_API_KEY` | `docker login nvcr.io` with `$oauthtoken` \u002F `NGC_API_KEY`; rotate the key at `org.ngc.nvidia.com\u002Fsetup\u002Fapi-key` if needed |\n| NRE refuses to load a clip (\"not valid NCore V4\") | Recording was not converted | Run the `ncore` skill before invoking `nre` |\n| `serve-grpc` cold-start latency dominates a Python loop | One-shot Docker invocation per render | Use the `nre` warm `serve-grpc` + thin Python client (`batch_render_rgb`) recipe |\n| Output files are owned by `root` after a `docker run` | `-u $(id -u):$(id -g)` was missing | `sudo chown -R \"$(id -u):$(id -g)\" \u003Coutput_dir>`; add the `-u` flag next time |\n| Frames have ghosting \u002F floaters \u002F flicker after rendering | Inline cleanup not enabled | Re-render with `nre --enable-difix`, or post-process with `nurec-fixer` (DiffusionHarmonizer) |\n| Stale skill names (`ncore-data-conversion`, old `nvidia\u002FFixer`) in agent output | Out-of-date cached skill | Update references to `ncore` and `nurec-fixer` (DiffusionHarmonizer); see [`references\u002Fmaintenance.md`](references\u002Fmaintenance.md) |\n| Bash anti-pattern `${HF_TOKEN:+yes}${HF_TOKEN:-no}` echoed token value | Misuse of bash parameter expansion | Rotate the token; use `hf auth whoami` or length-only checks (see [`references\u002Fsecrets-handling.md`](references\u002Fsecrets-handling.md)) |\n\n## Cross-skill teardown\n\nA complete NuRec workflow can leave **150 GB+** on disk between\ncontainer images, model weights, code clones, conda envs, and output\ndirectories. Each sibling skill has its own dedicated `Teardown`\nsection — read them in the order documented in\n[`references\u002Fteardown.md`](references\u002Fteardown.md) when the user no\nlonger needs the workflow.\n\n## Keeping this router up to date\n\nProcedure for adding new sibling skills, renames, or upstream URL\nchanges lives in [`references\u002Fmaintenance.md`](references\u002Fmaintenance.md).\nTreat the upstream `nurec-index` at\n\u003Chttps:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnurec-skills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002FSKILL.md>\nas authoritative; this skill mirrors only the picker tables, the\nworkflow ordering, and the upstream fetch recipe.\n",{"name":5,"tools":24,"license":15,"version":27,"metadata":28,"description":7,"compatibility":67},[25,26],"Read","Shell","0.3.0",{"tags":29,"author":35,"upstream":36,"upstream_clone_path":65,"upstream_override_env":66},[30,31,32,33,34],"physical-ai","nurec","neural-reconstruction","router","sensor-sim","NVIDIA Physical AI",{"repo":37,"branch":38,"skills_dir":39,"index_skill":40,"sibling_skills":41,"index_skill_name":63,"skills_dir_alias":64},"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnurec-skills","main",".agents\u002Fskills\u002F",".agents\u002Fskills\u002FSKILL.md",[42,46,50,54,58],{"name":43,"folder":44,"upstream":45},"physical-ai-datasets","physical-ai-datasets\u002F","https:\u002F\u002Fhuggingface.co\u002Fnvidia",{"name":47,"folder":48,"upstream":49},"ncore","ncore\u002F","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fncore",{"name":51,"folder":52,"upstream":53},"nre","nre\u002F","nvcr.io\u002Fnvidia\u002Fnre\u002Fnre",{"name":55,"folder":56,"upstream":57},"asset-harvester","asset-harvester\u002F","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fasset-harvester",{"name":59,"folder":60,"hf_model":61,"upstream":62},"nurec-fixer","nurec-fixer\u002F","https:\u002F\u002Fhuggingface.co\u002Fnvidia\u002FDiffusionHarmonizer","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fharmonizer","nurec-index","skills\u002F","${PHYSICAL_AI_SKILL_HUB_UPSTREAM_ROOT:-$HOME\u002F.physical-ai-skill-hub\u002Fupstreams}\u002Fnurec-skills","NUREC_SKILLS_UPSTREAM_ROOT","Router skill; downstream sibling skills require Docker, NVIDIA Container Toolkit, GPU, NGC API key, Hugging Face token with PhysicalAI gated licenses accepted, Python 3.10+, and `huggingface_hub`. Optional: CARLA \u002F Isaac Sim 5.1 \u002F AlpaSim for simulator integration over `serve-grpc`.","c475fc64e94e803b50d14a791dfee8853fbb2c5c","skills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory","https:\u002F\u002Fgithub.com\u002FElogic360","2026-11-08 22:21:22",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add Elogic360\u002Fsoftware-factory --skill physical-ai-neural-reconstruction",{"tool":79,"command":80},"bunx","bunx skills add Elogic360\u002Fsoftware-factory --skill physical-ai-neural-reconstruction",{"tool":82,"command":83},"pnpm","pnpm dlx skills add Elogic360\u002Fsoftware-factory --skill physical-ai-neural-reconstruction","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction\u002FSKILL.md",true,[87,93,97,101,105,109,113,117,121,125],{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"BENCHMARK.md","REFERENCE","参考文档",3090,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction\u002FBENCHMARK.md",{"path":94,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":95,"sourceHtmlUrl":96},"evals\u002Fevals.json",4976,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction\u002Fevals\u002Fevals.json",{"path":98,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fmaintenance.md",1240,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction\u002Freferences\u002Fmaintenance.md",{"path":102,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fmix-ups.md",2197,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction\u002Freferences\u002Fmix-ups.md",{"path":106,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fsecrets-handling.md",1065,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction\u002Freferences\u002Fsecrets-handling.md",{"path":110,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fteardown.md",1614,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction\u002Freferences\u002Fteardown.md",{"path":114,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fupstream-fetch.md",2318,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction\u002Freferences\u002Fupstream-fetch.md",{"path":118,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fworkflows.md",4268,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction\u002Freferences\u002Fworkflows.md",{"path":122,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":123,"sourceHtmlUrl":124},"skill-card.md",2998,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction\u002Fskill-card.md",{"path":126,"resourceType":127,"resourceTypeDesc":128,"sizeBytes":129,"sourceHtmlUrl":130},"skill.oms.sig","OTHER","其他",5809,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fphysical-ai-neural-reconstruction\u002Fskill.oms.sig",[132,139,146,153,160,167],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":19},"01M79G206MT3J6S0GY3C45P2KV","vss-summarize-video","Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback. Not for report generation or live RTSP captioning.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-summarize-video\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":19},"01M79G1WN63PGRE8CKD47WEBQ5","vss-setup-video-analytics-api","Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":19},"01M79G1S9F7VY3EF6H53PRP5AN","vss-setup-behavior-analytics","Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-behavior-analytics\u002FSKILL.md",[],[],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":19},"01M79G1N1S1Y27PFZPYMNK1MTQ","vss-search-archive","Use this skill to run top-level VSS fusion search on archived video, or to ingest video files \u002F RTSP streams for search. Do NOT use for ad-hoc visual Q&A (use vss-ask-video), live captioning (use vss-deploy-dense-captioning), or video summarization and reports (use vss-summarize-video).","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-search-archive\u002FSKILL.md",[],[],{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":19},"01M79G1H6WN0Q6C0VCAXCZX6B7","vss-query-analytics","Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-query-analytics\u002FSKILL.md",[],[],{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":19},"01M79G1DYPNXQS7QHZ0AAF5FX5","vss-manage-video-io-storage","Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add\u002Fdelete sensors and streams). Not for VLM inference or search.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-manage-video-io-storage\u002FSKILL.md",[],[]]