NVIDIA
- 962 skills
- 0 followers
- 2.2k repo stars
- 431 verified
- last week last updated
- ▌ Skill Card Generator 2 · nvidia bundleUse only to generate or update a governance skill card for a specified existing agent skill directory. Do not use for explaining, listing, comparing, or discussing skill capabilities.
- ▌ Physicsnemo Discover 2 · nvidia bundleOfficial NVIDIA-authored guidance for navigating PhysicsNeMo — pick the model, datapipe, or example for a SciML/AI4Science task (surrogates, forecasting, downscaling, physics-informed, inverse, generative). Points at existing files via live repo search; never writes code. Do NOT use for installation or environment setup, training-loop or other code authoring/scaffolding, contributor/CI/packaging questions, repo-specific questions in physicsnemo-sym/-cfd/-curator, or general (non-physics) ML/PyTorch.
- ▌ Nemoclaw User Guide 2 · nvidia bundleGuides human users' AI agents to the NemoClaw docs MCP server and canonical Fern documentation in Markdown form. Use when users ask how to install, configure, operate, troubleshoot, secure, or learn NemoClaw with an AI coding assistant. Trigger keywords - nemoclaw docs, use nemoclaw with ai agent, nemoclaw mcp docs, nemoclaw install help, nemoclaw quickstart, nemoclaw markdown docs, llms.txt, agent skills.
- ▌ Guardrails Developer Guide 2 · 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.
- ▌ Guardrails Developer Create Guardrails 2 · 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.
- ▌ Nemoclaw Nvteam 2 · nvidia bundleRoute product, program, engineering, data and ML, quality, SRE, security, and developer-community work through the eight local role lenses packaged with the developer-community-chief-of-staff recipe in nemoclaw-community. Use for explicit NVTeam or persona activation, cross-functional readiness, developer relations, community enablement, technical-enablement work, or automatic specialist routing within this recipe. Do not use for a standalone question about core NemoClaw product capabilities unless the user explicitly requests NVTeam. This skill is Community-recipe behavior, not a built-in NemoClaw capability.
- ▌ Nemoclaw Autoheal 2 · nvidiaGuide users through Hermes availability checks and the optional host-side auto-heal setup without crossing the sandbox-to-host boundary.
- ▌ Outlook Email Search 2 · nvidia bundleSearch the Outlook mailbox via Microsoft Graph to find and read emails that help answer user questions.
- ▌ Warp Closing Issue 2 · nvidia bundleUse when the user provides Warp commit SHA(s) and GitHub issue number(s) to assess, draft issue comments, post progress updates, or recommend whether issue threads should stay open or close.
- ▌ Warp Release Audit 2 · nvidia bundleUse when generating a Warp pre-release or release-candidate audit report from Towncrier fragments and release history.
- ▌ Warp Release Notes 2 · nvidia bundleUse when drafting GitHub release notes for a Warp feature or bugfix release from Towncrier fragments or a tagged final changelog.
- ▌ Warp Changelog Audit 2 · nvidia bundleUse when auditing and recovering Warp changelog fragments, finalizing a release changelog, or synchronizing a tagged release back to main.
- ▌ Tilegym Cutile Python 2 · nvidia bundleExpert cuTile programming assistant. Write high-performance GPU kernels using cuTile's tile-based programming model with proper validation and optimization. Supports deep agent orchestration for complex multi-kernel tasks.
- ▌ Tilegym Cutile Autotuning 2 · nvidia bundleUse when adding, modifying, optimizing, or debugging CuTile autotuning code. Trigger signals: `exhaustive_search` / `replace_hints` / `hints_fn` / `cuda.tile.tune` in code, `autotune` in filenames, or correctness/performance issues in autotuned CuTile kernels. Covers: tune-once/cache/launch pattern, per-architecture configs (sm80–sm120), parameter space design (tile sizes, occupancy, num_ctas), and 7 common pitfalls with solutions.
- ▌ Tilegym Adding Cutile Kernel 2 · nvidia bundleAdd a new cuTile GPU kernel operator to TileGym. Covers dispatch registration in ops.py, cuTile backend implementation, __init__.py exports, test creation, and benchmark in tests/benchmark. Use when adding, creating, or implementing a new cuTile operator/kernel in TileGym, or when asking how to register a new cuTile op.
- ▌ Cicd 2 · nvidiaCI/CD reference for NeMo-RL. Covers GitHub Actions pipeline structure, CI triggering via /ok to test, and CI failure investigation.
- ▌ Testing 2 · nvidiaTesting conventions for NeMo-RL. Covers Ray actor coverage pragmas, nightly test requirements, and recipe naming rules.
- ▌ Copyright 2 · nvidiaNVIDIA copyright header requirements for NeMo-RL. Covers which files need headers and the exact header text.
- ▌
- ▌ Contributing 2 · nvidiaContribution conventions for NeMo-RL. Covers PR title format, commit sign-off, and CI triggering.
- ▌ Error Handling 2 · nvidiaError handling guidelines for NeMo-RL. Covers exception specificity, minimal try bodies, and else blocks.
- ▌ Review Pr Team 2 · nvidiaAgent-team-based parallel code review for NVIDIA-NeMo/RL pull requests. Spawns specialized agents (RL expert, submodule experts, bug finder, design reviewer, test agent, devil's advocate, comment reviewer) that coordinate via shared task list and direct messaging. Leader orchestrates, collates ALL findings, and presents to user for approval before posting.
- ▌ Config Conventions 2 · nvidiaConfiguration conventions for NeMo-RL. YAML is the single source of truth for defaults. Covers BaseModel/TypedDict usage, dataclass for internal classes, exemplar YAML updates, and forbidden default patterns.
- ▌ Build And Dependency 2 · nvidiaBuild and dependency management for NeMo-RL. Covers Docker image building and running, uv usage, venv setup, and adding dependencies.
- ▌ Linting And Formatting 2 · nvidiaCode style guidelines for NeMo-RL (Python and shell). Covers naming, indentation, comments, docstrings, reflection avoidance, and uv usage.
- ▌ Simready Foundation Add Feature 2 · nvidia bundleUse for adding SimReady feature docs, manifests, requirement mappings, validation strategy, and index entries.
- ▌ Simready Foundation Add Profile 2 · nvidia bundleUse for adding SimReady profile versions with feature bundles, docs, indexes, and validation notes.
- ▌ Simready Foundation Add Validator 2 · nvidia bundleUse for adding executable SimReady validators that report requirement IDs with focused pass/fail coverage.
- ▌ Simready Foundation Add Capability 2 · nvidia bundleAdd SimReady capability docs, requirement indexes, validation stubs, and registrations for new requirement families.
- ▌ Simready Foundation Create Package 2 · nvidia bundleUse for creating SimReady packages with package sample scripts, WRAPP setup, root USD inputs, validation phases, and fallback modes.
- ▌ Simready Foundation Update Feature 2 · nvidia bundleUse for updating SimReady features with new versions, requirement changes, manifests, docs, and profile notes.
- ▌ Simready Foundation Update Profile 2 · nvidia bundleUse for updating SimReady profile versions, feature bundles, docs, and adapter notes.
- ▌ Simready Foundation Add Requirement 2 · nvidia bundleUse for adding atomic SimReady requirements with stable IDs, docs, examples, indexes, and validator follow-up.
- ▌ Simready Foundation Add Runtime Test 2 · nvidia bundleUse for adding SimReady runtime tests, runner expectations, batch/job/report notes, and validation evidence.
- ▌ Simready Foundation Update Validator 2 · nvidia bundleUse for updating SimReady validators, failure messages, edge cases, and tests while preserving requirement semantics.
- ▌ Simready Foundation Update Capability 2 · nvidia bundleUse for updating SimReady capability docs, requirement indexes, validation registration, and feature references.
- ▌ Simready Foundation Update Requirement 2 · nvidia bundleUse for updating SimReady requirement docs, semantics, validator alignment, and profile impact notes.
- ▌ Simready Foundation Add Feature Adapter 2 · nvidia bundleUse for adding SimReady feature adapters that mutate USD assets between exact feature or profile versions.
- ▌ Simready Foundation Conform Fet 000 Core 2 · nvidia bundleUse for repairing SimReady Core naming, asset layout, unresolved paths, and undefined prim failures.
- ▌ Simready Foundation Update Feature Adapter 2 · nvidia bundleUse for updating SimReady feature adapters, USD mutation logic, tests, and source/target metadata.
- ▌ Simready Foundation Conform Fet 001 Minimal 2 · nvidia bundleUse for repairing SimReady Minimal assets: units, upAxis, defaultPrim, hierarchy, mesh quality, extents, and origin placement.
- ▌ Simready Foundation Conform Fet 006 Materials 2 · nvidia bundleUse for repairing SimReady material bindings, USDPreview or MDL shaders, texture paths, sizes, and color spaces.
- ▌ Simready Foundation Conform Fet 021 Robot Core 2 · nvidia bundleUse for repairing SimReady robot core layout, thumbnails, robot schema, relationships, and root joint pinning.
- ▌ Simready Foundation Validate Foundation Change 2 · nvidia bundleUse for auditing SimReady requirement, validator, feature, profile, adapter, test, and skill consistency.
- ▌ Simready Foundation Conform Fet 023 Robot Materials 2 · nvidia bundleUse for repairing SimReady robot material organization under the top-level Looks scope.
- ▌ Simready Foundation Conform Fet 024 Base Articulation 2 · nvidia bundleUse for repairing SimReady base articulation roots and PhysX collision-clearance evidence.
- ▌ Simready Foundation Conform Fet 003 Rigid Body Physics 2 · nvidia bundleUse for repairing SimReady rigid-body and collider conformance for neutral or PhysX prop assets.
- ▌ Simready Foundation Conform Fet 007 Nonvisual Materials 2 · nvidia bundleUse for repairing SimReady nonvisual sensor material attributes on bound USD materials.
- ▌ Simready Foundation Conform Fet 005 Simulate Grasp Physi 2 · nvidia bundleUse for vision-guided SimReady grasp repair, grasp_identifier curves, and physics-material triage.
- ▌ Simready Foundation Conform Fet 004 Simulate Multi Body 2 · nvidia bundleUse for repairing SimReady multibody physics: rigid bodies, joints, articulation roots, and PhysX variants.
- ▌ Amc Run Video Calibration 2 · nvidia bundleCalibrates pre-recorded `cam_*.mp4` datasets through the AutoMagicCalib REST API. Use for user-supplied local MP4s; route live RTSP streams to `amc-run-rtsp-calibration`.
- ▌ Nemotron Policy Generator 2 · nvidia bundleGenerates BYO custom safety policies for NVIDIA Nemotron content-safety guardrails — Nemotron-Content-Safety-Reasoning-4B (text) and multimodal Nemotron-3-Content-Safety. Produces a Markdown policy, JSON taxonomy, and drop-in inference prompts. Maps rough words or an existing policy to V2 categories, adding custom categories or topic-following rules.
- ▌ Amc Run Sample Calibration 2 · nvidia bundleRun end-to-end calibration on the shipped sample dataset (sdg_08_2_sample_data_010926.zip) against a running AMC microservice. Use when user says 'test sample dataset', 'run sample calibration', 'verify AMC install', or 'launch and test'.
- ▌ Holoscan Install Container 2 · nvidia bundleInstall Holoscan SDK via the NGC Docker container. Use for container-based installs; not for native apt/pip/Conda installs.
- ▌ Nemotron Retrieval Recipes 2 · nvidia bundleUse when planning, debugging, tuning, evaluating, exporting, or deploying public Nemotron `embed`/`rerank` retrieval recipes.
- ▌ Deepstream Profile Pipeline 2 · nvidia bundleProfile a DeepStream pipeline with Nsight Systems and derive its configs from the measurement. Use when the user asks for an efficient, performant, or profiled pipeline — or to benchmark, tune, or measure FPS.
- ▌ Vss Manage Video Io Storage 2 · nvidia bundleUse to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add/delete sensors and streams). Not for VLM inference or search.
- ▌ Deepstream Generate Pipeline 2 · nvidia bundleBuild DeepStream GStreamer pipelines interactively. Use when the user asks about pipelines for video/image inference, detection, tracking, or streaming — including natural phrases like 'pipeline to infer on image', 'run inference on video', 'detect objects in stream', 'save inference output', 'deepstream pipeline', 'gst-launch pipeline', 'process video with detection', 'build a pipeline', or any request involving GStreamer/DeepStream elements (nvinfer, nvstreammux, nvtracker, etc.).
- ▌ Mcore Linting And Formatting 2 · nvidia bundleLinting and formatting for Megatron-LM. Covers running autoformat.sh, tools (ruff, black, isort, pylint, mypy), and code style rules.
- ▌ Vss Setup Behavior Analytics 2 · nvidia bundleUse to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.
- ▌ Nv Generate Mr Brain Finetune 2 · nvidia bundleUsed for finetuning NV-Generate-CTMR MR-Brain v1 for T1, T2, FLAIR, SWI, or MRA data from a NIfTI datalist. Not for clinical or production data approval.
- ▌ Vss Setup Video Analytics API 2 · nvidia bundleUse to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.
- ▌ Cupynumeric Parallel Data Load 2 · nvidia bundleLoad a sharded, on-disk dataset (sharded .npy, Parquet/Arrow, raw binary, sharded HDF5, custom layouts) into a distributed cuPyNumeric ndarray via a manual partition + leaf @task launch with CPU/OMP/GPU variants. Use when no single-call loader fits, including when per-shard row counts differ across files. Prefer cupynumeric.load or legate.io.hdf5.from_file when they apply.
- ▌ Deepstream Import Vision Model 2 · nvidia bundleUse this skill to bring a supported object-detection vision model from HuggingFace or NVIDIA NGC into an NVIDIA DeepStream pipeline with end-to-end automation: ONNX download, SafeTensors export, TRT engine build, custom nvinfer bbox parser, multi-stream benchmark, and PDF report. Object detection models only.
- ▌ Earth2studio Create Datasource 2 · nvidia bundleCreate and validate Earth2Studio data source wrappers (DataSource, ForecastSource, DataFrameSource, ForecastFrameSource) from remote stores. Do NOT use for fetching data with existing sources, model inference, or installation tasks.
- ▌ Earth2studio Create Diagnostic 2 · nvidia bundleCreate Earth2Studio diagnostic model wrappers for single-step data transformations, including simple derived diagnostics, packaged AutoModel diagnostics, and generative or diffusion diagnostics. Do NOT use for prognostic time-stepping models, data sources, or installation.
- ▌ Earth2studio Create Prognostic 2 · nvidia bundleCreate Earth2Studio prognostic (time-stepping forecast) model wrappers. Do NOT use for diagnostic models, data sources, or installation.
- ▌ Nemo Automodel Launcher Config 2 · nvidia bundleConfigure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
- ▌ Cupynumeric Migration Readiness 2 · nvidia bundlePre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
- ▌ Nemo Mbridge Perf Memory Tuning 2 · nvidia bundleTechniques for reducing peak GPU memory in Megatron Bridge — expandable segments, PEFT + SP input re-gather, parallelism resizing, activation recompute, CPU offloading constraints, and common OOM fixes.
- ▌ Cuopt Numerical Optimization API 2 · nvidia bundleLP, MILP, and QP (beta) with cuOpt — Python, C, and CLI. Use when the user is solving LP, MILP, or QP with any cuOpt interface.
- ▌ Digital Health Clinical Asr Eval 2 · nvidia bundleStage 3 of Clinical ASR Flywheel. Score a NeMo manifest, produce the five-section KER leaderboard (by-ipa_source diagnostic). Not for ASR auth (/riva-asr).
- ▌ Nemo Mbridge Mlm Bridge Training 2 · nvidia bundleRun Megatron-LM (MLM) and Megatron Bridge training with mock or real data. Covers correlation testing, available recipes, and multi-GPU examples.
- ▌ Cuopt Multi Objective Exploration 2 · nvidia bundleTrace, complete, and interpret the Pareto frontier across competing objectives using repeated single-objective cuOpt solves (weighted-sum and ε-constraint).
- ▌ Digital Health Clinical Asr Build 2 · nvidia bundleStage 2 of the Clinical ASR Flywheel. Use when curating clinical terms, tagging IPA, and synthesizing a NeMo manifest. NOT for scoring (use /digital-health-clinical-asr-eval).
- ▌ Digital Health Clinical Asr Setup 2 · nvidia bundleStage 1 of Clinical ASR Flywheel. Use when bootstrapping a cycle: NVCF+MW disclosure, NVIDIA_API_KEY check, deps install, TTS+ASR smoke test.
- ▌ Nemo Automodel Recipe Development 2 · nvidia bundleCreate and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.
- ▌ Nemo Mbridge Perf Moe Comm Overlap 2 · nvidia bundleMoE expert-parallel communication overlap in Megatron Bridge. Covers dispatch/combine overlap, flex dispatcher backends, and expert wgrad scheduling.
- ▌ Nemo Mbridge Perf Moe Long Context 2 · nvidia bundleLong-context MoE training guidance for Megatron Bridge. Covers CP sizing, selective recompute, dispatcher choices, and practical patterns from DSV3, Qwen3, and Qwen3-Next long-context experiments.
- ▌ Nemo Mbridge Perf Moe Vlm Training 2 · nvidia bundlePractical guidance for training MoE VLMs in Megatron Bridge. Compares FSDP and 3D-parallel approaches, using rounded lessons from Qwen3-VL, Qwen3-Next, and other multimodal experiments.
- ▌ Nemo Mbridge Perf Sequence Packing 2 · nvidia bundleValidate and use packed sequences and long-context training in Megatron-Bridge, including offline LLM packing, collate-time VLM packing, Energon online packing, and CP constraints.
- ▌ Hsb Test 2 · nvidia bundleExecute QA test plans on Holoscan Sensor Bridge hardware. Reads a user-provided test document, filters tests by the user's setup, determines which tests can run automatically, executes them with pass/fail evaluation, and produces a structured test results report.
- ▌ Hsb Flash 2 · nvidia bundleFlash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must never be mixed.
- ▌ Hsb Setup 2 · nvidia bundleClone the latest NVIDIA Holoscan Sensor Bridge repo, ask which supported devkit is being used, configure the host per platform, build the correct demo container, run it, and verify HSB connectivity by pinging 192.168.0.2. Use for Holoscan Sensor Bridge setup, build, container launch, and first-connectivity bring-up.
- ▌ Cudaq Guide 2 · nvidia bundleCUDA-Q onboarding guide for installation, test programs, GPU simulation, QPU hardware, and quantum applications.
- ▌ Cuopt Install 2 · nvidia bundleInstall cuOpt for Python, C, or server via pip, conda, or Docker; verify the install. For building cuOpt from source, see cuopt-developer.
- ▌ Mcore Testing 2 · nvidia bundleTest system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.
- ▌ Nv Reason Cxr 2 · nvidia bundleUsed for command-shape or live NV-Reason-CXR chest X-ray reasoning smoke tests. Not for diagnosis or clinical reporting.
- ▌ Nv Segment Ct 2 · nvidia bundleUsed for running NV-Segment-CT VISTA3D on CT NIfTI volumes and recording label-map evidence.
- ▌ Vss Ask Video 2 · nvidia bundleUse this skill to ask the VSS agent's video_understanding tool a fresh visual question about a recorded clip. Not for prior tool output, search hits, or metadata-answerable questions.
- ▌ Deepstream Dev 2 · nvidia bundleNVIDIA DeepStream SDK development with Python pyservicemaker API. Use when building video analytics pipelines, GStreamer-based video processing, TensorRT inference integration, object detection/tracking, or Kafka/message broker integration.
- ▌ Deepstream Sop 2 · nvidia bundleUse this skill when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP Inference Microservice — a GPU-accelerated FastAPI service that detects whether operators perform assembly-line steps in order via event boundary detection (GEBD) plus VLM classification. Trigger even if the user does not name it: verify operator step sequence, detect missing or out-of-order SOP steps, score factory/work-cell video for procedure compliance, run VLM-based SOP checking on industrial cameras, or call /v1/chat/completions with a file, RTSP, or Basler camera. Also trigger for its internals: SOPVideoProcessor, DeepStream GEBD model (e.g. DDM) via Triton CAPI, nvds_custom_postprocess, Cosmos Reason 1/2 vLLM, SSE streaming, Kafka NvProto/JSON output, Basler/Pylon camera + emulation, Docker compose, chunk-level latency. Do NOT trigger for generic DeepStream pipelines, object detection/tracking, NIM imports, or video summarization.
- ▌ Holoscan Setup 2 · nvidia bundleGuides Holoscan SDK installation: inspects the host, assesses platform compatibility, recommends an install method, and delegates to the matching install skill.
- ▌ Mcore Split Pr 2 · nvidia bundleSplit a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
- ▌ Nemo Retriever 2 · nvidia bundleUse when the user wants to search, query, extract, transcribe, describe, quote, filter, or aggregate across documents — PDFs, scanned forms / images (`.jpg` `.png` `.tiff`), Office (`.docx` `.pptx`), text (`.html` `.txt`), audio (`.mp3` `.wav` `.m4a`), or video (`.mp4` `.mov`). Prefer this over native Read / Grep for multi-file or non-PDF corpora. Not for: editing files, web browsing, single-file plain-text lookups, fine-tuning.
- ▌ Nv Generate Mr 2 · nvidia bundleUsed for generating synthetic body MRI volumes with NV-Generate-CTMR rflow-mr. Not for paired masks or production training data.
- ▌ Cuopt Developer 2 · nvidia bundleModify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions.
- ▌ Nemotron Speech 2 · nvidia bundleRoutes NVIDIA Nemotron Speech (Riva) NIM tasks — deploys, runs, and tests ASR, TTS, and NMT NIMs on build.nvidia.com or self-hosted.
- ▌ Nv Segment Ctmr 2 · nvidia bundleUsed for running NV-Segment-CTMR on CT or MRI NIfTI volumes and recording label-map evidence. Not for clinical interpretation.
- ▌ Cupynumeric Hdf5 2 · nvidia bundleRead and write large cuPyNumeric arrays to HDF5 with Legate's parallel, distributed HDF5 I/O (legate.io.hdf5: to_file, from_file, from_file_batched). Use when a developer needs to save a cuPyNumeric array to an .h5/.hdf5 file, load an HDF5 dataset into a distributed cuPyNumeric array, read a large HDF5 dataset in chunks, hand arrays to an HPC pipeline as a single file, or accelerate HDF5 disk I/O with GPUDirect Storage (GDS). Do not use it for Parquet/cuDF/raw-binary or other sharded/custom layouts (see the cupynumeric-parallel-data-load skill), Zarr or object-store/S3 output, .npz or pickled archives, plain h5py without cuPyNumeric, or pure array compute such as FFT, matmul, or reductions.