Agent skill · nvidia
pva-setup
Install and configure the NVIDIA PVA SDK, NVVPU compiler, and L4T target runtime from the selected installation guide. Use when the user requests PVA environment setup on a development host and board.
What it needs
About 6k tokens when loaded.
What this skill does
Set up a PVA development environment <!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> Support regular x86-64 Ubuntu on the development host and Jetson Linux (L4T) on the Arm64 target. Run the agent and build tools on the development host. PVABUILDMODE=L4T cross-compiles for execution on the board; PVABUILDMODE=EMU builds for emulation on the development host. Use NVVPU for non-safety development. DriveOS and ASIP setup are outside this workflow. Workflow: Doctor → Setup when needed → Doctor → Spec → OpGen. Doctor checks readiness without installing software. The user invokes Setup when installation or configuration is needed. Resolve the inputs Use the user request and Doctor report to resolve: Doctor report and requested capabilities. Installation guide, supplied as a local file or URL; PVA generation. Optional SDK release or installation-path override supplied by the user. Development host and target SSH connection; expected BSP release, if supplied. Work directory (WORKDIR); use Doctor's work directory when supplied. Optional EMU, CUDA, NvSci, or PVA Solutions requirements and project path. When PVA Solutions is selected, use the supplied project path or default to $WORKDIR/source. Reuse an existing source tree. Otherwise clone https://github.com/nvidia/pva-solutions.git there, unless the user supplies another repository or source archive. Honor a requested Solutions tag, branch, or commit; without one, use the repository's default branch. Record the source URL, absolute project path, version, and resolved commit when available. Do not infer a Solutions version from the SDK version. Resolve the SDK release, installer URL, package names, and installation paths from the selected guide and package metadata before invoking Doctor. This includes SDK, NVVPU, CMake package, and target runtime paths. Do not hard-code package paths or construct names or paths from a version. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/pva-setup