Agent skill · nvidia
pva-doctor
Check whether a host is ready for requested NVIDIA PVA work. Use before Spec, OpGen, Build-Test, or Debug. Verify references to the installed SDK documentation, inspect only the requested capabilities, and prove that either NVVPU or ASIP/Chess can compile target VPU code when L4T compilation is required. Report READY, READY_WITH_LIMITATIONS, or NOT_READY. Do not install or configure software.
What it needs
About 9k tokens when loaded.
What this skill does
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> Check a PVA development environment Check only the capabilities that the user requests. Record other capabilities as notes. Do not let them lower the verdict. Do not install software. Do not change host or target settings. Do not print a license value, credential, token, or private key. Get the inputs Resolve these inputs: Requested capabilities: one or more of spec, opgen, build-test, or debug. PVA SDK root and requested version; record the installed version separately. An absent installation is a check failure, not a missing user input. PVA generation: GEN2, GEN3, or both. Project type: PVA SDK application or PVA Solutions source. Project path and version, when a project is in scope. EMU policy: optional by default, or required when the user requires it. Work directory (WORKDIR). Default to ./pva-operator/. Optional features, such as CUDA or NvSci interoperability. For direct target work, also resolve the target address, user, port, known-hosts file, and PVA generation. An expected BSP release is optional. Do not guess a credential, user, proxy, or transport. Use this scope table: Capability Required checks --- --- spec References, SDK identity, project read access, and Python. opgen References, writable project, build tools, L4T compiler, target access, and PVAOPERATORMAXDEBUGATTEMPTS. build-test References, build tools, L4T compiler, transfer tools, and target access. debug References and only the tools, source access, and target access needed for the supplied failure. Resolve paths SKILLROOT is the absolute directory containing this skill's SKILL.md, after resolving symlinks. Bundled files are relative to that directory. Resolve user-supplied relative paths, including WORKDIR and PVASDKROOT, against the invocation directory before changing directories. Set SDKREFERENCES to $WORKDIR/references/sdk. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/pva-doctor