Generated banner for Pva Opgen
Generated logo for Pva Opgen

Pva Opgen

NVIDIAOfficialCreated by Venkat BalanDistributed by NVIDIA

  • Skill
  • Workflow
  • Software development
  • Apache-2.0
  • Medium risk
  • Has scripts

From the author

Generate, change, or repair a complete vectorized NVIDIA PVA operator from a validated pva-spec handoff. Deliver the contract's API, host and VPU code, independent CPU reference, sample, build integration, tests, and documentation. Verify with pva-build-test and use pva-debug within the configured attempt limit.
— the description by Venkat Balan

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

pva-opgen is a workflow skill designed to implement NVIDIA Programmable Vision Accelerator (PVA) operators. It takes a validated specification handoff and generates the necessary components, including public APIs, host code, VPU code, independent CPU references, build integration, tests, and documentation. The skill incorporates an automated verification and repair loop, utilizing pva-build-test for validation and pva-debug for iterative fixes within a defined attempt limit.

What it does

  • Validates input specifications and project requirements.
  • Generates host and VPU code, APIs, and CPU reference implementations.
  • Integrates build configurations, samples, and test suites.
  • Executes automated verification using pva-build-test.
  • Performs iterative repairs on failed implementations using pva-debug.
  • Produces a final report detailing the implementation status and deliverables.

When to use it

  • When you need to implement a new PVA operator from an approved specification.
  • When modifying or repairing an existing PVA operator implementation.
  • When you have a validated pva-spec handoff and require a complete set of project deliverables.
  • When you need to verify operator correctness against a specified test matrix.

Advantages

  • Ensures consistency by following strict specification contracts.
  • Automates the repetitive aspects of operator implementation and build wiring.
  • Provides a structured repair loop to address verification failures.
  • Maintains traceability through recorded evidence and validation reports.

Usage examples

“Generate the PVA operator implementation based on the validated handoff in my current work directory.”
The agent validates the input, generates the required host/VPU code and tests, runs the build-test suite, and provides a final opgen-report.md.
“Repair the failed PVA operator implementation using the available debug budget.”
The agent invokes pva-debug to address the identified failures, then re-runs pva-build-test to verify the fix.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/nvidia/pva-opgen/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip pva-opgen.zip -d .agents/skills

Documentation by Venkat Balan

<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->

Generate a PVA operator

Implement the approved Spec contract. Do not redefine it.

Resolve paths

SKILL_ROOT 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. Set OPGEN_INPUTS to the absolute handoff path and WORK_DIR to the caller's report work directory. For a handoff at <work-directory>/configure/opgen-inputs.json, default WORK_DIR to that <work-directory>; otherwise require an explicit report work directory. Use only the validated handoff's workspace as the project root.

Inputs

Before changing source, require installed pva-build-test and, when PVA_OPERATOR_MAX_DEBUG_ATTEMPTS is greater than zero, pva-debug. Resolve them by name through the agent's skill discovery; their directories need not be adjacent. Return BLOCKED if a required skill is unavailable.

Run these skills using the agent's available skill mechanism. If no callable skill tool exists, load the named skill's SKILL.md and execute its complete workflow as the Build-Test or Debug phase. Save that phase's reports, then resume OpGen with its verdict. Reading instructions alone does not execute a phase.

Require:

  • Spec's opgen-inputs.json.

  • The recorded operator specification, test matrix, and evidence manifest.

  • A Doctor report that is ready for opgen, or accepted limitations.

  • Direct-Tegra inputs that Build-Test needs.

  • A writable report directory.

ScriptCommandInputsOutputsExit codes
finalize_opgen_inputs.pypython3 "$SKILL_ROOT/scripts/finalize_opgen_inputs.py" --check "$OPGEN_INPUTS"Spec handoff and its recorded inputs.JSON validation summary; read-only check.0: valid; 1: failed; 2: invalid command arguments.

Run this command before you inspect or change the workspace:

python3 "$SKILL_ROOT/scripts/finalize_opgen_inputs.py" \
  --check "$OPGEN_INPUTS"

Return BLOCKED if the command reports an invalid structure, unknown requirement link, unsafe path, missing evidence, changed input, stale hash or size, or mismatched count. Do not repair Spec-owned files or handoff metadata.

Use the project workspace recorded in the validated handoff.

Verify the recorded hashes before reading project evidence files. Use API, CPU-reference, test, workload, KPI, benchmark, and build files only as contracts. Do not copy CPU-reference or test code into the implementation.

Read the technical basis

Use the Doctor report recorded in the validated handoff. Require its public-reference-corpus check to be PASS. Set SDK_REFERENCES to that report's absolute sdk_reference_root. Require a readable index.md and reference-lock.json, a lock SHA-256 matching the report's sdk_reference_lock_sha256, and the reported SDK version matching this task. If these fields are absent or no longer match, return BLOCKED for a fresh Doctor report and regenerated Spec handoff. Do not edit a finalized report or fall back to an installed package or CWD path. Read the pva-opgen route in $SDK_REFERENCES/index.md. Before reading Markdown, check its SHA-256 against the lock outputs entry; return BLOCKED on a mismatch. Resolve links relative to each generated file.

Use rg to select only the programming, data-movement, build, tutorial, and API Markdown that applies. Read the relevant Orin GEN2 or Thor GEN3 guide chapters for the core, VMEM, address generation, vector operations, and programming examples.

Before use of an intrinsic or mnemonic, find its exact type and operation in the generated guide pages. Record the SDK documentation root, local Markdown path, packaged source path, source SHA-256, guide revision, generation, and section or PDF page.

Use supplied or public implementations within the user's authorized scope and their license terms.

Inspect the project

Record:

  • Public API and ownership conventions.

  • Host and device target patterns.

  • Registration, sample, test, and documentation patterns.

  • Installed SDK version and PVA generation.

  • Files that OpGen will add or change.

Do not require Git metadata or a fixed repository layout.

Design the implementation

Use the behavior and test contracts from Spec.

  1. Select an algorithm that gives the specified result.

  2. Separate parallel work from reductions and dependencies.

  3. Select the PVA dataflow and transfer plan.

  4. Select a tile and VMEM layout that fit the target generation.

  5. Define vector-tail, alignment, border, and scratch handling.

  6. Estimate compute and transfer work when the required facts exist.

  7. Record unavailable facts as limitations. Do not invent a Speed-of-Light value.

Use RasterDataFlow for suitable raster tiles. Use another documented dataflow only when the access pattern needs it.

Create the deliverables

Create or update all items that the Spec contract requires:

DeliverableRequirement
Public APIUse project naming, ownership, validation, and error conventions. Preserve asynchronous behavior.
Host codeCreate resources, load VPU code, configure dataflows, submit work, check status, synchronize as required, and release owned resources.
VPU codeUse documented device APIs and vector intrinsics. Keep the main data path vectorized. Use a correct predicated or scalar tail only where required.
CPU referencePreserve an approved independent reference. For a new operator, create independent scalar logic that implements the contract.
Build wiringAdd host, device, sample, test, and optional performance targets. Add a complete install target or deployment manifest.
SampleShow one valid lifecycle, check the result, and release resources.
TestsImplement the approved Spec test matrix without weakening expected results or tolerances.
DocumentationDocument the API, formats, shapes, parameters, arithmetic, borders, limits, build steps, and sample.

Do not reuse a VMEM buffer before its transfer or compute use is complete. Do not replace a documented vector operation with scalar work in the main data path. Record each necessary scalar region and its reason.

Do not derive an expected result from PVA output.

Verify with Build-Test

Run pva-build-test using the child-skill mechanism defined above.

Pass:

  • Caller identity OpGen, WORK_DIR, and the Debug calls used and maximum.

  • The validated Doctor report and Spec handoff.

  • The active project root.

  • The complete correctness matrix and EMU policy.

  • SKIPPED_OPTIONAL evidence when optional EMU support is unavailable.

  • L4T build, install, target, and direct-SSH inputs.

  • build-test-opgen as the report label.

  • An absolute result directory under $WORK_DIR for each Build-Test call.

Use correctness-only when the matrix has no performance case. Use correctness-and-performance when it has one or more performance cases. Pass performance targets, clock inputs, filters, and sample policy only in the second scope.

Build-Test owns all build, EMU, hardware, profiling, evidence, and verdict rules. Follow its instructions without skipping or weakening checks.

After every Build-Test call, resume OpGen and inspect its returned verdict and report. A child skill's final response does not complete OpGen. Follow the repair rules below, then write the final OpGen report before ending the run.

Repair a failed implementation

Start with zero Debug calls used and read the maximum from PVA_OPERATOR_MAX_DEBUG_ATTEMPTS. Check the budget before every Debug call; 0 means no automatic repair. The next attempt number is calls used plus one. Count each execution of the Debug workflow as one Debug call, regardless of the invocation mechanism, including one that returns without a repair.

If Build-Test returns FAILED and an attempt remains, run pva-debug using the same child-skill mechanism with the complete failure report, failing source identity, command, logs, case, expected result, tolerance, next attempt number, and maximum attempts. Pass the same WORK_DIR for Debug reports.

After Debug returns, resume OpGen. For each REPAIRED result, invoke Build-Test again on the changed source using a new result directory and the complete original matrix. Choose the next action from the returned result:

ResultOpGen action
Build-Test PASSEDWrite the final PASSED report.
Build-Test FAILED, calls used below maximumInvoke Debug, then resume OpGen.
Build-Test FAILED, zero or exhausted budgetWrite the final FAILED report with the failed stage, reason, evidence, and calls used. Do not attempt a repair.
Build-Test or Debug BLOCKEDWrite the final BLOCKED report with the exact unavailable prerequisite.
Debug NOT_REPRODUCEDWrite the final FAILED report, retaining the original failure and Debug's reproduction result.

Record one attempt entry per Debug invocation, with its result and source identity. Do not reset or discount calls used when a failure remains unchanged.

Do not invoke Debug for an external BLOCKED result. Do not invoke Doctor or Spec.

Output Format

Write $WORK_DIR/reports/opgen-report.md with the result template. Write it for every terminal outcome, including zero or exhausted debug budget, before returning the final response. Report zero calls explicitly when Debug was not invoked. If the report directory is unavailable, identify the exact path and write error in the final response.

Return one verdict:

  • PASSED: All deliverables exist, and Build-Test passed the current source.

  • FAILED: An executed implementation or verification stage produced a negative result that the bounded repair loop did not repair.

  • BLOCKED: A required input, dependency, permission, corpus, or target is unavailable.

Report the changed files, API, supported matrix, vectorization, dataflow, VMEM plan, build targets, deployment method, Build-Test result, Debug attempts, evidence paths, hashes, and limitations.

Do not claim hardware verification from EMU execution. Stop after the OpGen result.

Files

LICENSE

Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python

Security

What our scanner noticed· Medium risk

  • Large base64-encoded blobs
  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Venkat Balan
Publisher
NVIDIA (Official)
Distributed by
NVIDIA
Source
NVIDIA/skills · skills/pva-opgen · commit fce3cca
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE-APACHE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Venkat Balan or NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download pva-opgen.zip