Agent skill · nvidia
pva-build-test
Build and verify an NVIDIA PVA operator with the public PVA SDK. Use alone or from OpGen. Run optional EMU correctness, a fresh L4T build with the NVVPU or ASIP/Chess backend that Doctor proved, direct-SSH Tegra hardware correctness, and optional hardware performance. Return PASSED, FAILED, or BLOCKED with exact evidence.
What it needs
About 6k tokens when loaded.
What this skill does
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. --> Build and test a PVA operator Build the current source. Test it on a directly connected Tegra. Do not change source code, expected results, or tolerances. Build-Test owns verification stages, evidence, and verdicts. Resolve paths SKILLROOT is the absolute directory containing this skill's SKILL.md, after resolving symlinks. Bundled files are relative to that directory. Resolve supplied relative paths against the invocation directory before changing directories. PROJECTROOT is the active source workspace; RESULTDIR is the caller's result directory. All build directories, reports, logs, and manifests below are under RESULTDIR, not the shell's CWD. Get the inputs Require these inputs for all scopes: Caller identity: OpGen for an OpGen call; otherwise the direct user. A Doctor report that is ready for build-test, or accepted limitations. Absolute project (PROJECTROOT) and result (RESULTDIR) paths. Operator name and PVA generation. Test scope: correctness-only or correctness-and-performance. Report label. Use build-test when none is supplied. SDK version, safety variant, and Doctor's proved compiler backend. EMU policy; when EMU execution is available or required, Doctor's proved EMU build mode and configure options, plus test commands. L4T configure command and hardware system-test target and filter. Correctness cases, independent references, and tolerances. Complete install target or deployment manifest. Tegra address, user, port, and persistent known-hosts file. For correctness-and-performance, also require: KPI or profiling target and case filter. Profiling method, metric, warm-up count, and at least 1000 samples. User-approved clock and clock-verification commands. Expected clock values and target power mode. Performance target and acceptance rule when the caller requests a comparison. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/pva-build-test