NVIDIA
- 962 skills
- 0 followers
- 2.2k repo stars
- 431 verified
- 2 weeks ago last updated
- ▌ Simready Foundation Add Profile · nvidia bundleUse for adding SimReady profile versions with feature bundles, docs, indexes, and validation notes.
- ▌ Simready Foundation Add Validator · nvidia bundleUse for adding executable SimReady validators that report requirement IDs with focused pass/fail coverage.
- ▌ Simready Foundation Add Capability · nvidia bundleAdd SimReady capability docs, requirement indexes, validation stubs, and registrations for new requirement families.
- ▌ Simready Foundation Create Package · nvidia bundleUse for creating SimReady packages with package sample scripts, WRAPP setup, root USD inputs, validation phases, and fallback modes.
- ▌ Simready Foundation Update Feature · nvidia bundleUse for updating SimReady features with new versions, requirement changes, manifests, docs, and profile notes.
- ▌ Simready Foundation Update Profile · nvidia bundleUse for updating SimReady profile versions, feature bundles, docs, and adapter notes.
- ▌ Simready Foundation Add Requirement · nvidia bundleUse for adding atomic SimReady requirements with stable IDs, docs, examples, indexes, and validator follow-up.
- ▌ Simready Foundation Add Runtime Test · nvidia bundleUse for adding SimReady runtime tests, runner expectations, batch/job/report notes, and validation evidence.
- ▌ Simready Foundation Update Validator · nvidia bundleUse for updating SimReady validators, failure messages, edge cases, and tests while preserving requirement semantics.
- ▌ Simready Foundation Update Capability · nvidia bundleUse for updating SimReady capability docs, requirement indexes, validation registration, and feature references.
- ▌ Simready Foundation Update Requirement · nvidia bundleUse for updating SimReady requirement docs, semantics, validator alignment, and profile impact notes.
- ▌ Simready Foundation Add Feature Adapter · nvidia bundleUse for adding SimReady feature adapters that mutate USD assets between exact feature or profile versions.
- ▌ Simready Foundation Conform Fet 000 Core · nvidia bundleUse for repairing SimReady Core naming, asset layout, unresolved paths, and undefined prim failures.
- ▌ Simready Foundation Update Feature Adapter · nvidia bundleUse for updating SimReady feature adapters, USD mutation logic, tests, and source/target metadata.
- ▌ Simready Foundation Conform Fet 001 Minimal · nvidia bundleUse for repairing SimReady Minimal assets: units, upAxis, defaultPrim, hierarchy, mesh quality, extents, and origin placement.
- ▌ Simready Foundation Conform Fet 006 Materials · nvidia bundleUse for repairing SimReady material bindings, USDPreview or MDL shaders, texture paths, sizes, and color spaces.
- ▌ Simready Foundation Conform Fet 021 Robot Core · nvidia bundleUse for repairing SimReady robot core layout, thumbnails, robot schema, relationships, and root joint pinning.
- ▌ Simready Foundation Validate Foundation Change · nvidia bundleUse for auditing SimReady requirement, validator, feature, profile, adapter, test, and skill consistency.
- ▌ Simready Foundation Conform Fet 023 Robot Materials · nvidia bundleUse for repairing SimReady robot material organization under the top-level Looks scope.
- ▌ Simready Foundation Conform Fet 024 Base Articulation · nvidia bundleUse for repairing SimReady base articulation roots and PhysX collision-clearance evidence.
- ▌ Simready Foundation Conform Fet 003 Rigid Body Physics · nvidia bundleUse for repairing SimReady rigid-body and collider conformance for neutral or PhysX prop assets.
- ▌ Simready Foundation Conform Fet 007 Nonvisual Materials · nvidia bundleUse for repairing SimReady nonvisual sensor material attributes on bound USD materials.
- ▌ Simready Foundation Conform Fet 005 Simulate Grasp Physics · nvidia bundleUse for vision-guided SimReady grasp repair, grasp_identifier curves, and physics-material triage.
- ▌ Simready Foundation Conform Fet 004 Simulate Multi Body Phys · nvidia bundleUse for repairing SimReady multibody physics: rigid bodies, joints, articulation roots, and PhysX variants.
- ▌ Sop Ddm Finetuning · nvidia bundleFine-tune DDM-Net temporal boundary detector for SOP monitoring. Use when you need to launch and monitor a DDM-Net training run with a given dataset ID.
- ▌ Sop Ft Orchestrate · nvidia bundleAutonomous end-to-end orchestrator for SOP fine-tuning. Runs the full Import → Augment → DDM Train → VLM Train → Evaluate → RCA loop. Interprets RCA findings across DDM, VLM and augment axes, applies config fixes autonomously, and iterates until success criteria are met or max_pipeline_iterations reached. Call with a path to an inputs.yaml or with natural language.
- ▌ Sop Data Augmentation · nvidia bundleUse when the user wants to run data augmentation on an annotated dataset, configure augmentation parameters, check augmentation status, or understand what each QA augmentation type does (BCQ, MCQ, GQA, DMCQ, DSQA, ENQA, WMCQ)
- ▌ Vss Sop Deploy · nvidia bundleBuild the DS-SOP Docker image and deploy the VSS SOP blueprint end-to-end. Use when asked to deploy SOP, build DS SOP, install SOP, set up the SOP pipeline, verify SOP models, start the SOP blueprint, simulate RTSP for SOP, run the SOP API test, or tear down SOP.
- ▌ Sop Rca · nvidia bundleRoot cause analysis for SOP monitoring pipeline failures. Analyzes end-to-end evaluation logs, DDM temporal segmentation, VLM action recognition, training data, and fine-tuning configs to identify failure patterns and produce an evidence-driven RCA report with actionable improvement recommendations.
- ▌ Vss Call Vios API · nvidia bundleInteract with the VIOS (Video IO & Storage) microservice in a running VSS profile — manage cameras/sensors, RTSP streams, recordings, snapshots, and storage. Use when asked to add a camera, add an RTSP stream, list sensors, show configured sensors/cameras/streams, what sources are available, check stream status, start/stop recording, get a snapshot, or manage video storage. Always query the VIOS API directly — do not navigate the UI to answer these questions.
- ▌ Sop E2e Inference · nvidia bundleUse when running the e2e evaluation pipeline (temporal segmentation + action recognition + accuracy) against the BP evaluation-ms HTTP API. Invoked as /sop-e2e-inference <inputs.yaml> [natural language parameter overrides]
- ▌ Sop By Action Eval · nvidia bundleUse when running by-action VLM evaluation (per-action-clip inference + accuracy metrics) against the BP evaluation-ms HTTP API. Invoked as /sop-by-action-eval <inputs.yaml> [natural language parameter overrides]
- ▌ Sop Cr Finetuning · nvidia bundleFine-tune Cosmos-Reason2 (CR2) VLM for SOP monitoring. Use when you need to launch and monitor a VLM training run with a given dataset ID.
- ▌ Sop Build · nvidia bundleOrchestrate the end-to-end SOP pipeline, including preflight prerequisite checks, verifying models and downloading assets, generating the DeepStream SOP microservice with RTSP output, evaluating the microservice, and building, deploying, and testing the VSS SOP blueprint. Use when asked to run the full SOP pipeline, set up the SOP pipeline from scratch, execute preflight checks, verify models, download assets, generate the SOP microservice, evaluate the microservice, build the VSS blueprint, deploy the VSS blueprint, test the VSS blueprint, or manage the complete build-evaluate-deploy-test cycle.
- ▌ Vss Sop Test · nvidia bundleRun post-deployment tests for the VSS SOP blueprint. Checks service health, ELK data pipeline, VIOS recording/livestream, and VSS agent (MCP, LLM, VLM, snapshot, video, report). Auto-debugs failures. Use when asked to test SOP, verify SOP deployment, check SOP services, validate SOP, run SOP health checks, or troubleshoot SOP after deploy.
- ▌ Vss Sop Build · nvidia bundleBuild a custom VSS SOP blueprint from the VSS 3.1 base, then deploy and test in a loop until fully operational. Use when asked to create the SOP blueprint structure, customize VSS compose for SOP, configure SOP services, set up the VSS agent for SOP, or scaffold the SOP app layer on top of met-blueprints 3.1.
- ▌ Tilegym Converting Cutile Triton To Cutile Rs · nvidia bundleUse this skill to convert, port, or translate Triton-TileIR or cuTile-Python GPU kernels to cutile-rs (Rust). The orchestrator runs scripts/preflight.sh, then drives a bounded Agent A -> B -> D -> E pipeline (Agent C is diagnostic, Agent F optional), delegating all kernel/host/correctness/perf work to sub-agents and routing by each stage's single-line VERDICT.
- ▌ Nat User Rules · nvidia bundleUse first for general NVIDIA NeMo Agent Toolkit coding-agent behavior, task routing, naming conventions, component discovery rules, and cross-skill guidance.
- ▌ Nat Path Checks · nvidiaUse when fixing NeMo Agent Toolkit documentation path-check failures, especially failed `ci/scripts/path_checks.py` output, slash-delimited text mistaken for paths, relative path references, Markdown code escaping, and path-check allowlist decisions.
- ▌ Skill Evolution · nvidiaUse before creating, editing, or deciding whether to update any AI coding agent skill in this repository, including corrections to existing skill behavior, references, or routing.
- ▌ Nat Optimization · nvidia bundleUse when configuring or running NeMo Agent Toolkit optimization with `nat optimize`, including Optuna parameter tuning, prompt evolution, optimizer sizing, output interpretation, and optimizer datasets.
- ▌ Nat Workflow Creation · nvidia bundleUse when creating, editing, validating, running, or troubleshooting NeMo Agent Toolkit workflow YAML, component discovery, LLM configuration, and common `nat` CLI commands.
- ▌ Generic Max Supply · nvidia bundleMulti-period supply chain planning model: data files, BOM structure, variable/constraint reference for the max-supply base model.
- ▌ Cuopt Model Mapper · nvidiaMap interpreted optimization problems into cuOpt-native models for the fast path with minimal clarifying questions.
- ▌ Optimization Mode Router · nvidiaChoose fast direct-to-cuOpt solve versus replayable or auditable model artifact mode.
- ▌ Optimization Intent Router · nvidiaClassify whether a data-backed request is LP, MILP, QP, routing, or non-optimization analytics.
- ▌ Tabular Optimization Ingestion · nvidiaInfer optimization structure from uploaded tables and identify minimal clarifications before cuOpt modeling.
- ▌ Optimization From Data Orchestrator · nvidiaCoordinate uploaded data plus a natural-language question into interpretation, clarification, cuOpt solve, and a user-facing answer.
- ▌ Cuopt Debugging · nvidia bundleTroubleshoot cuOpt LP/MILP problems including errors, wrong results, infeasible solutions, performance issues, and status codes. Use when the user says something isn't working, gets unexpected results, or needs help diagnosing issues.
- ▌ Cuopt Sandbox · nvidia bundleRun cuOpt in the NemoClaw sandbox — probe/smoke gates, prefer cancelable Python gRPC jobs, use legacy remote execution only when that API is unavailable, then vendored cuOpt skills.
- ▌ Physical AI Defect Image Generation V1 1 · nvidia bundleUse for NVIDIA Cosmos3-based AnomalyGen 1.1 defect image generation on OSMO; use the unversioned physical-ai-defect-image-generation skill for the original workflow. Orchestrates Day 0 USD-to-ROI, Qwen image-edit augmentation, LoRA finetuning, and generation, plus Day 1 checkpoint reuse, inference, and labeling for PCBA, metal surfaces, and glass. Trigger for AnomalyGen 1.1, Cosmos3 defects, DIG 1.1, Day 0 or Day 1 PCBA, manual ROI, real-photo alignment, setup_pcb, setup_metal, setup_glass, setup_pretrained, finetune checkpoint reuse, or the DIG image-edit endpoint.
- ▌ Osmo User · nvidia bundleDrive the OSMO CLI for cloud-robotics compute on behalf of an end user: check resources, submit/monitor/debug/explain workflows, fetch logs and Grafana/Kubernetes links, inspect direct data storage, manage workflow apps, and set workflow credentials. Use whenever the user asks about OSMO pools, quota, GPUs, or nodes, or about submitting, listing, querying, monitoring, or troubleshooting workflows — including failed, PENDING, queued, stuck, or image-pull-blocked workflows, or when they ask to inspect or transfer direct storage URIs such as `s3://...`, even when they describe a workflow, cluster resource, or storage URI without saying "OSMO". Do not use for Kubernetes admin, server-side `osmo config` changes, OSMO install/deploy, non-OSMO compute, or general NVIDIA hardware questions.
- ▌ Osmo Admin · nvidia bundleUse only for offline/local OSMO service-config admin requests involving explicit config roots or values files, or to ask for one when a file-specific config request omits it. Do not inspect the workspace to infer a root. Do not use for live workflow support, resource capacity, pod/node diagnostics, or cluster operations, except live service-config paths that must be refused.
- ▌ Osmo Deploy · nvidia bundleHow to deploy OSMO to a Kubernetes cluster on Azure (AKS), AWS (EKS), MicroK8s (single-node), or any kubectl-reachable cluster (BYO). Use this skill whenever the user asks to install, deploy, set up, or stand up OSMO; whenever they ask to provision an OSMO cluster; whenever they mention deploy-osmo-minimal.sh, deploy-k8s.sh, or "OSMO helm install"; whenever they ask to wire up workflow storage (MinIO / Azure Blob / S3); or whenever they ask to add a GPU pool to an OSMO cluster, install KAI scheduler, install the NVIDIA GPU Operator, or run the post-install smoke tests. Targets OSMO 6.3 (ConfigMap mode).
- ▌ Nemo Curator Docs · nvidiaMaintain the NeMo Curator Fern docs site — add, update, move, or remove pages under fern/. Use for any documentation changes.
- ▌ Mcore Cicd · nvidia bundleCI/CD reference for Megatron-LM. Covers CI pipeline structure, PR scope labels, triggering internal GitLab CI (which force-pushes the current branch to a pull-request/BRANCH ref — always dry-run and verify the destination first; never run against shared or protected branches), and CI failure investigation.
- ▌ Nightly Sync · nvidiaDomain knowledge for the nightly main-to-dev sync workflow. Covers merge strategy, CI architecture, failure investigation, and known issues.
- ▌ Respond To Issue · nvidiaResearch and draft a response to a GitHub issue or question from an external contributor.
- ▌ Update Golden Values · nvidiaRefresh golden values from a GitHub Actions workflow run (failing-only or all jobs), calculate signed per-model percentage changes, and produce a PR-ready summary. Use when the user asks to update goldens for a CI run, refresh golden values from a workflow ID, or generate a golden-value diff summary for a PR description.
- ▌ Mcore Bump Base Image · nvidia bundleBump the NVIDIA PyTorch base image (`nvcr.io/nvidia/pytorch:YY.MM-py3`) used by Megatron-LM CI. Covers the two pin sites (GitHub CI in `docker/.ngc_version.dev` and GitLab CI in `.gitlab/stages/01.build.yml`), the post-bump CI loop (re-run functional tests, refresh golden values, mark broken tests), and the gotchas that bit PRs
- ▌ Mcore Build And Dependency · nvidia bundleContainer-based dev environment setup and dependency management for Megatron-LM. Covers acquiring and launching the CI container, uv package management, and updating uv.lock.
- ▌ Mcore Migrate Gpt To Hybrid · nvidiaMigration guide for moving Megatron Core GPTModel checkpoints, model providers, training commands, and layer mappings to HybridModel, including the mechanical steps for transferring an existing pretrain_gpt.py launch script.
- ▌ Mcore Onboard Gb200 1node Tests · nvidia bundleOnboard 1-node GitHub MR functional tests for GB200 from existing mr-scoped 2-node tests.
- ▌ Sbom · nvidiaGenerate and manage Software Bill of Materials (SBOMs) for the OpenShell project. Covers SBOM generation with Syft, license resolution via public registries, and CSV export for compliance review. Trigger keywords - SBOM, sbom, bill of materials, license audit, license resolution, generate sbom, sbom csv, dependency license, supply chain, license scan.
- ▌ Openshell CLI · nvidiaGuide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, policy iteration, settings, service exposure, BYOC workflows, and inference routing. Covers basic through advanced multi-step workflows. Trigger keywords - openshell, sandbox create, sandbox exec, sandbox connect, logs, provider create, provider profile, provider refresh, policy set, policy get, settings, service expose, forward, port forward, BYOC, bring your own container, inference, use openshell, run openshell, CLI usage, manage sandbox, manage provider, gateway add, gateway select.
- ▌ Debug Inference · nvidiaDebug why inference.local, direct external inference, or supervisor-only system inference is failing. Use when the user cannot reach a local model server, has provider base URL issues, sees inference verification failures, hits protocol mismatches, or needs to diagnose inference on local vs remote gateways. Trigger keywords - debug inference, inference.local, system inference, sandbox-system, local inference, ollama, vllm, sglang, trtllm, NIM, inference failing, model server unreachable, failed to verify inference endpoint, host.openshell.internal.
- ▌ Create Rfc · nvidia bundleCreate OpenShell RFC proposals in rfc/ from a design request. Use when the user asks to write, draft, start, create, or update an RFC, Request for Comments, architecture proposal, API proposal, process proposal, or cross-cutting design proposal that should follow the OpenShell RFC process and template.
- ▌ Update Docs From Commits · nvidiaScan recent git commits for changes that affect user-facing behavior, then draft or update the corresponding documentation pages. Use when docs have fallen behind code changes, after a batch of features lands, or when preparing a release. Trigger keywords - update docs, draft docs, docs from commits, sync docs, catch up docs, doc debt, docs behind, docs drift.
- ▌ Create Spike · nvidiaInvestigate a plain-language problem description by deeply exploring the codebase, then create a structured GitHub issue with technical findings. Prequel to build-from-issue — maps vague ideas to concrete, buildable issues. Trigger keywords - spike, investigate, explore, research issue, technical investigation, create spike, new spike, feasibility, codebase exploration.
- ▌ Triage Issue · nvidiaAssess, validate, and route community-filed issues for human disposition and roadmap placement. Takes a specific issue number or processes a confirmed batch of issues labeled state:triage-needed. Investigates reported behavior, separates objective findings from product decisions, and prepares validated issues for a human yes/no decision. Trigger keywords - triage issue, triage, assess issue, review incoming issue, triage issues.
- ▌ Tui Development · nvidiaGuide for developing the OpenShell TUI — a ratatui-based terminal UI for the OpenShell platform. Covers architecture, navigation, data fetching, theming, UX conventions, and development workflow. Trigger keywords - term, TUI, terminal UI, ratatui, openshell-tui, tui development, tui feature, tui bug.
- ▌ Debug Openshell Cluster · nvidiaDebug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes. Use for gateway health failures, Docker/Podman runtime issues, Helm failures, Kubernetes scheduling, TLS or auth, gateway interceptors, supervisor middleware startup or runtime failures, external compute-driver sockets, VM drivers, or sandbox startup. Trigger keywords - debug gateway, gateway failing, deployment failing, helm install failing, cluster health, gateway health, gateway not starting, health check failed, sandbox pending, docker driver, podman driver, kubernetes driver, external driver, compute driver socket, gateway interceptor, supervisor middleware, middleware failed, vm driver.
- ▌ Generate Sandbox Policy · nvidia bundleGenerate sandbox security policies from plain-language requirements and optional REST API documentation. Produces L4 or fine-grained L7 network policies and ordered network middleware configuration. Use for API access rules, middleware host selection, failure behavior, or built-in and operator-run middleware attachment. Trigger keywords - generate policy, create policy, update policy, change policy, sandbox policy, network policy, API policy, security policy, allow API, restrict API, network middleware, supervisor middleware.
- ▌ Build From Issue · nvidiaGiven a GitHub issue number, plan and implement the work described in the issue. Supports direct user requests and unattended queue processing through the `agent:*` workflow labels. Includes tests, documentation updates, and PR creation. Trigger keywords - build from issue, implement issue, work on issue, build issue, start issue.
- ▌ Create Github Pr · nvidiaCreate GitHub pull requests using the gh CLI. Use when the user wants to create a new PR, submit code for review, or open a pull request. Trigger keywords - create PR, pull request, new PR, submit for review, code review.
- ▌ Review Github Pr · nvidiaReview a GitHub pull request by summarizing its diff and key design decisions. Use when the user wants to review a PR, understand changes in a branch, or get a code review summary. Trigger keywords - review PR, review pull request, summarize PR, summarize diff, code review, review branch, PR summary, diff summary.
- ▌ Sync Agent Infra · nvidiaDetect and fix drift across agent-first infrastructure files. Ensures skill inventories, workflow chains, architecture tables, issue/PR templates, and cross-references stay consistent when skills, crates, or workflows change. Run after adding, removing, or renaming skills or components. Trigger keywords - sync agent infra, sync skills, update agent docs, check agent consistency, agent infra drift, sync contributing, sync agents.
- ▌ Fix Security Issue · nvidiaImplement a fix for a reviewed security issue. Takes a directly requested issue number or scans for issues labeled `topic:security` and `agent:implementation-requested`. Reads the security review from the issue comments and implements the remediation plan. Trigger keywords - fix security issue, remediate security, implement security fix, patch vulnerability.
- ▌ Create Github Issue · nvidiaCreate GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue.
- ▌ Test Release Canary · nvidiaManually dispatch and iterate on the Release Canary workflow that smoke-tests published OpenShell artifacts (install.sh on macOS/Ubuntu/Fedora, Helm chart on kind) after each Release Dev publish. Use when changing `.github/workflows/release-canary.yml`, validating a release before tagging, debugging a canary failure, or reproducing a canary job locally. Trigger keywords - release canary, release-canary, canary failed, canary dispatch, test release canary, post-release smoke, install.sh canary, helm chart canary, kind canary, dispatch canary.
- ▌ Helm Dev Environment · nvidiaStart up, tear down, and configure the local Kubernetes development environment for OpenShell. Uses k3d (Docker-backed k3s) + Skaffold + Helm. Covers cluster lifecycle, optional add-ons (Keycloak OIDC, Envoy Gateway), HA testing, and port mappings. Trigger keywords - local k8s, local cluster, k3d, skaffold, helm dev, start cluster, stop cluster, tear down cluster, delete cluster, create cluster, helm:k3s, helm:skaffold, local dev environment, dev cluster, k8s dev, envoy gateway local, keycloak local, high availability, HA.
- ▌ Watch Github Actions · nvidiaWatch and monitor GitHub Actions workflow runs using the gh CLI. Use when the user wants to check workflow status, watch a running workflow, view CI/CD jobs, or monitor build progress. Trigger keywords - watch pipeline, pipeline status, CI status, check build, monitor CI, view pipeline, pipeline progress, workflow status, actions status.
- ▌ Review Security Issue · nvidiaGiven a GitHub issue, review the issue for security implications. You'll make a determination if the claim in the issue is legitimate and should be addressed or will be a "won't fix." Trigger keywords - security issue, review security ticket, review security issue.
- ▌ Launch Openshell Gator · nvidiaLaunch and supervise OpenShell gator agents. Use when starting gator on issues or PRs, checking gator sandboxes, building the gator sandbox image, restarting stuck gators, inspecting gator logs, or experimenting with gator harness/model overrides. Trigger keywords - launch gator, start gator, run gator, gator sandbox, supervised gator, gator logs, restart gator.
- ▌ Gator Gate · nvidia bundleValidate and monitor OpenShell GitHub issues and PRs using the gator:* state machine. Use when asked to triage issues/PRs for project validity, gate PRs, run gator, validate submissions, or monitor PRs toward merge readiness.
- ▌ Build Openshell Mxc Windows · nvidia bundleMaintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64. Use when working on Windows compilation, `windows:*` mise tasks, unsupported Windows compute-driver contracts, or Windows build reports. This skill does not implement Docker, Kubernetes, Podman, VM, MXC driver, policy translation, MSI, service, or supervisor runtime support on Windows.
- ▌ Developer Release Rebase · nvidiaPrepare a new minor alpha release of Earth2Studio by rebasing the release candidate branch onto main, bumping the version, updating the changelog, updating the README latest-news highlights, stripping example version tags, and pushing for PR. Use when releasing, cutting a release, preparing a release branch, rebasing a release, or bumping the version for a new development cycle.
- ▌ Developer Bump Version · nvidiaBump the Earth2Studio version on main to start a new development cycle. This unblocks commits on main after a release branch has been merged. Performs a CHANGELOG update (new blank section) and a hatch version bump. Use when main already has the release merge but still carries the old version string, or when the developer-release-rebase skill detects the version was already bumped during rebase and only the changelog/version housekeeping remains.
- ▌ Asset Harvester · nvidia bundleUse to install and run NVIDIA Asset Harvester (Apache-2.0) to extract per-object 3D Gaussian Splat assets (`gaussians.ply`) from AV NCore V4 clips or masked single images via SparseViewDiT + TokenGS, optionally producing `metadata.yaml` for NuRec object insertion. Do NOT use for full-scene reconstruction (use `nre`) or for inputs without per-object masks.
- ▌ Physical AI Datasets · nvidia bundleUse when the user wants to find, download, or pick a NVIDIA Physical AI dataset on Hugging Face for autonomous-vehicle, robotics, spatial intelligence, manipulation, or neural-reconstruction workflows. Catalog of every dataset under huggingface.co/nvidia with the `PhysicalAI-` prefix, organised by domain (AV, Robotics-Manipulation, Robotics-GR00T, Robotics-mindmap, Robotics-NuRec, Spatial Intelligence, Grasping, Healthcare, Sim-Ready, Material properties), with per-dataset size, format, gating, license, and the downstream sibling skill (`ncore`, `nre`, `asset-harvester`, `nurec-fixer`) or upstream tool (Isaac Sim, CARLA, Isaac-GR00T, Cosmos-*) that consumes it. Do NOT use as a runtime — it routes you elsewhere. Trigger keywords: nvidia physical ai dataset, PhysicalAI- dataset, hf nvidia dataset, NCore dataset, NuRec dataset, GR00T dataset, GraspGen, SimReady, Cosmos-Drive-Dreams, Lyra SDG, Open-H-Embodiment, huggingface-cli download, physical_ai_av, dataset gated, RDS-HQ.
- ▌ Nurec Index · nvidia bundleRouter for NVIDIA NuRec / NRE / 3DGUT / USDZ / NCore V4 / asset harvest / frame cleanup tasks — picks the right sibling (nre, ncore, asset-harvester, nurec-fixer, physical-ai-datasets). Use when the sub-skill is unclear or a multi-stage pipeline is needed; do NOT use for non-NuRec tasks or to run any pipeline itself.
- ▌ Ncore · nvidia bundleUse when converting any sensor dataset into NVIDIA NCore V4 format (and feeding it to NuRec or a robotics-to-sim "r2s" pipeline). Covers ingesting raw cameras, LiDARs, radars, IMUs, depth or stereo into V4 sequences; authoring a new converter from the template; adapting PAI / Waymo / PandaSet / NuScenes to V4; handling non-AV rigs (mono+depth, mono+lidar, stereo, multi-stereo, RGB-D, COLMAP / SfM, ROS2 bag); and diagnosing a broken converter against `validate.py`. Do NOT use to train reconstructions (use `nre`) or to extract per-object 3D assets (use `asset-harvester`). Trigger keywords: ncore, ncore v4, convert, ingest, zarr, itar, nurec, waymo, pandaset, nuscenes, pai, hyperion, colmap, scannetpp, stereo, multi-stereo, mono+depth, mono+lidar, kitti, sfm, camera, lidar, radar, imu, cuboid, poses, intrinsics, ego mask, ros2, rosbag, mcap, realsense, zed, rgb-d, r2s, robotics, sam2.
- ▌ Nurec Fixer · nvidia bundleUse to run NVIDIA DiffusionHarmonizer (public successor to the older Fixer recipes) to enhance, harmonize, evaluate, or fine-tune novel-view frames from NRE / NuRec / 3DGS / NeRF reconstructions. Do NOT use for training the 3D reconstruction itself (use `nre`) or for sensor-to-NCore conversion (use `ncore`).
- ▌ Nre · nvidia bundleUse to drive NVIDIA Omniverse NuRec / Neural Reconstruction Engine (NRE) via the public NGC containers nvcr.io/nvidia/nre/nre and nvcr.io/nvidia/nre/nre-tools (NGC_API_KEY required) — train 3DGUT Gaussian reconstructions from NCore clips, generate aux data, adapt an existing USDZ to an augmented target-vehicle rig (carline adaptation), render frames or LiDAR sweeps (local or warm `serve-grpc`), export PLY/depth/mesh/USDZ, edit actors, and evaluate metrics. Do NOT use for per-object asset capture (use `asset-harvester`) or sensor-to-NCore conversion (use `ncore`).
- ▌ Guardrails Developer Create Guardrails · nvidiaHelps developers create a NeMo Guardrails configuration for an LLM application. Use when users want to build, scaffold, configure, test, or iterate on input, output, retrieval, dialog, execution, Colang, or catalog-based guardrails. Trigger keywords - create guardrails, build guardrails, scaffold config, write rails, create config.yml, add input rails, add output rails, Colang flow, guardrails config, test guardrails.
- ▌ Guardrails Developer Guide · nvidiaRoutes NVIDIA NeMo Guardrails library product-usage questions to the canonical documentation. Use when users ask how to install, configure, integrate, evaluate, observe, deploy, troubleshoot, or use the NVIDIA NeMo Guardrails library. Trigger keywords - install guardrails, configure rails, guardrail catalog, Colang, Python API, LangChain, LangGraph, server, evaluate guardrails, tracing, metrics, Docker, troubleshooting.
- ▌ Harmonizer · nvidia bundleUse to run NVIDIA DiffusionHarmonizer (public successor to the older Fixer recipes) to enhance, harmonize, evaluate, or fine-tune novel-view frames from NuRec / 3DGS / NeRF reconstructions. Do NOT use for training the 3D reconstruction itself (use the `nurec` skills) or for sensor-to-NCore conversion (use `ncore`).
- ▌ Nemoclaw Maintainer Day · nvidia bundleRun one NemoClaw daytime maintainer pass. Prioritize items for the release version. Select a merge, salvage, security, test, conflict, or sequencing workflow and report progress. Use during the workday to land PRs and close issues. Designed for /loop, for example /loop 10m /nemoclaw-maintainer-day. Trigger keywords - maintainer day, work on PRs, land PRs, make progress, what's next, keep going, maintainer loop.
- ▌ Nemoclaw Maintainer E2e · nvidia bundleDispatches and reports trusted GitHub Actions E2E runs. Use for focused, full, staging Launchable, manual PR, and release-decision requests.
- ▌