Generated banner for Pva Spec
Generated logo for Pva Spec

Pva Spec

NVIDIAOfficialCreated by Venkat BalanDistributed by NVIDIA

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

From the author

Create and validate an NVIDIA PVA operator specification, test matrix, evidence manifest, and deterministic OpGen handoff. Use after Doctor for new operators, changes, or repairs, using requirements, a partial spec, reference code, or an existing operator. Accept text, files, and public URLs. Record unresolved requirements without inventing behavior.
— the description by Venkat Balan

AutoGineer summary

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

The pva-spec skill provides a structured workflow for defining the behavior contract of NVIDIA PVA operators. It guides users through collecting requirements, designing a comprehensive test matrix, and documenting evidence to ensure a deterministic handoff to the OpGen tool. The process requires a valid Doctor report and strictly adheres to predefined JSON templates for specifications, test matrices, and evidence, ensuring all requirements are linked to tests and all conflicts are resolved before finalization.

What it does

  • Generates operator specifications, test matrices, and evidence manifests based on requirements.
  • Validates inputs against a Doctor report to ensure reference consistency.
  • Enforces a strict precedence for resolving conflicting requirements.
  • Automates the finalization of OpGen inputs through a validation script.
  • Produces a configuration report summarizing the operator status and blocking issues.

When to use it

  • After running the Doctor skill for new PVA operators, changes, or repairs.
  • When you need to define a formal behavior contract before implementation.
  • When preparing operator specifications and test matrices for OpGen.
  • When you need to reconcile conflicting requirements or reference implementations.

Advantages

  • Ensures deterministic and consistent handoffs to OpGen.
  • Provides a clear, auditable trail of requirements and evidence.
  • Prevents implementation of ambiguous or conflicting operator behavior.
  • Standardizes the specification and testing process across different operators.

Usage examples

“Create a new PVA operator specification for a custom convolution operator using the provided requirements file.”
The agent initializes the workspace, validates the Doctor report, and generates the operator-spec.json, test-matrix.json, and evidence.json templates for the user to populate.
“Finalize the OpGen inputs for the updated image-resize operator.”
The agent runs the finalizer script to validate the JSON files against the Doctor report and project root, returning a status of CONFIGURED if all checks pass.

Install

  1. Download the skill as a ZIP:

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

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

Documentation by Venkat Balan

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

Specify a PVA operator

Define behavior before implementation. Spec owns the behavior contract and test matrix. It does not implement the operator or invoke OpGen.

Inputs

Accept one or more of these sources:

  • A plain-language description or local requirements file.

  • A public requirements URL.

  • A partial or complete specification.

  • A local or public reference implementation.

  • An existing operator name or path.

Resolve:

  • Task mode: new, change, or repair.

  • PVA generation: GEN2, GEN3, or both.

  • PVA SDK version and PVA Solutions version, when used.

  • Host API: C, C++, or both.

  • EMU policy: optional by default or required by user request.

  • Work directory (WORK_DIR) and project root (PROJECT_ROOT).

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

Default WORK_DIR to ./pva-operator/<operator-name>/. Resolve it and user-supplied relative paths against the invocation directory before changing directories. PROJECT_ROOT is the absolute supplied project directory. Work directly in that project. Do not overwrite an existing configuration.

SKILL_ROOT is the absolute directory containing this skill's SKILL.md, after resolving symlinks. Bundled files are relative to that directory. All command paths below use these absolute roots.

Verify references

Require Doctor's public-reference-corpus check to be PASS. Set SDK_REFERENCES to the 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 and request a fresh Doctor report. Do not fall back to an installed package or CWD path. Read the pva-spec 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 relevant API, requirement, architecture, and data-movement Markdown. Do not fetch the same NVIDIA product documentation. For each product fact, record the SDK documentation root, local Markdown path, packaged source path, source SHA-256, version, and section or PDF page.

Do not inspect the VPU ISA instruction-by-instruction reference during Spec (the Programmer's Guide chapter titled "Instruction Set Reference"). The architecture overview remains available for defining platform constraints.

Collect requirements

Inspect supplied implementations within the user's authorized scope and their license terms.

Use this precedence:

  1. Explicit user requirements.

  2. An approved supplied specification.

  3. The public API and independent CPU reference.

  4. Correctness tests, workloads, fixtures, and expected results.

  5. Public operator API documentation.

  6. Public algorithm and format documentation.

  7. Public SDK constraints.

  8. An assumption that the user must approve.

For a URL, record its title, URL, access date, license when available, and SHA-256 for downloaded source. Follow only links that resolve the contract.

For a change or repair, reconcile the existing API, CPU reference, tests, workloads, KPI cases, benchmark cases, and build wiring. Record each conflict. Do not silently select one conflicting source.

Do not copy source into the output. Do not use an example as proof for an unspecified case.

Write the three model outputs

Copy these templates into $WORK_DIR/configure/ and fill them according to the handoff requirements:

The templates own the field names. Write strict JSON. Do not write comments, duplicate keys, trailing commas, NaN, or infinity tokens. Use null for an unknown optional value.

Before finalizing, set the spec's status to CONFIGURED only when no blocking requirement remains. Set the matrix's operator to the spec's operator.name. Both coverage.uncovered_requirement_ids and coverage.unresolved_cases must be empty; resolve outstanding cases before creating the handoff.

For each requirement:

  1. Assign a stable ID.

  2. State the source and authority: public_nvidia, user_input, skill_workflow, or assumption.

  3. Define the observable API, resource, parameter, arithmetic, border, aliasing, execution, error, safety, and interoperability behavior that applies.

  4. Add an unresolved item when a missing value can change behavior.

  5. Mark the item as blocking only when implementation cannot proceed safely.

Record design constraints, not implementation choices. Mark a possible dataflow, tile, VMEM layout, vector-tail method, address generator, lookup method, or L2 use as candidate unless the contract requires it.

Define the test matrix

Require at least one correctness case with an independent expected result. Each requirement must have a test. Link every test to one or more requirement IDs. Include the cases that apply:

  • Each supported type, format, plane, and parameter family.

  • Minimum, maximum, odd, partial-tile, and vector-tail dimensions.

  • Tight and padded pitch.

  • Each border mode and corner.

  • Rounding, saturation, overflow, NaN, and infinity rules.

  • Structured and seeded-random input.

  • Valid and invalid aliasing.

  • Repeated submission and asynchronous execution.

  • Invalid resources, formats, dimensions, pitches, and parameters.

  • Required hardware correctness.

Set execution_policy.hardware to required. Set execution_policy.emulator to the selected EMU policy. Use the same approved correctness cases, inputs, references, and tolerances on EMU and hardware when EMU runs. EMU execution is an early aid. It is not hardware verification.

Add performance cases only when the user or source contract requires them. For each performance case, define the workload, metric, warm-up count, at least 1000 hardware samples, target conditions, and acceptance rule when one exists. Do not turn a public benchmark into a universal threshold. Do not derive a Speed-of-Light target from the implementation under test.

A missing performance target does not block correctness configuration. Use not_set for performance acceptance.

Record evidence

evidence.json records where requirements came from and which files support them. See the field purposes in the handoff requirements.

In evidence.json, record each used source once. For a project file, record only its category, path relative to PROJECT_ROOT, requirement IDs, and use. Do not calculate a hash, size, or absolute path. The finalizer calculates those values.

Record assumptions and conflicts in their named lists.

Create and check the handoff

ScriptCommandInputsOutputsExit codes
finalize_opgen_inputs.pypython3 "$SKILL_ROOT/scripts/finalize_opgen_inputs.py" --operator-spec "$WORK_DIR/configure/operator-spec.json" --test-matrix "$WORK_DIR/configure/test-matrix.json" --evidence "$WORK_DIR/configure/evidence.json" --doctor-report "$DOCTOR_REPORT" --workspace "$PROJECT_ROOT" --output "$WORK_DIR/configure/opgen-inputs.json"Spec, test matrix, evidence, Doctor report, and project root.opgen-inputs.json and a JSON validation summary.0: valid; 1: failed; 2: invalid command arguments.
finalize_opgen_inputs.pypython3 "$SKILL_ROOT/scripts/finalize_opgen_inputs.py" --check "$WORK_DIR/configure/opgen-inputs.json"Finalized handoff and its recorded inputs.JSON validation summary; read-only check.0: valid; 1: failed; 2: invalid command arguments.

After the three JSON files are final, resolve DOCTOR_REPORT to the absolute path of the supplied Doctor report and run:

python3 "$SKILL_ROOT/scripts/finalize_opgen_inputs.py" \
  --operator-spec "$WORK_DIR/configure/operator-spec.json" \
  --test-matrix "$WORK_DIR/configure/test-matrix.json" \
  --evidence "$WORK_DIR/configure/evidence.json" \
  --doctor-report "$DOCTOR_REPORT" \
  --workspace "$PROJECT_ROOT" \
  --output "$WORK_DIR/configure/opgen-inputs.json"

Do not create opgen-inputs.json with the model.

If this command reports a missing test for a requirement, add the test or link an existing test that checks the requirement. Run the command again.

Then run:

python3 "$SKILL_ROOT/scripts/finalize_opgen_inputs.py" \
  --check "$WORK_DIR/configure/opgen-inputs.json"

Do not modify a recorded input after finalization. Return BLOCKED if either command still fails. Give the files to OpGen only after both commands pass.

Output Format

Write $WORK_DIR/reports/configure-report.md with the report template.

Return one result:

  • CONFIGURED: No blocking question remains, and both finalizer commands pass.

  • NEEDS_INPUT: Missing behavior can change the API or required result.

  • INVALID_INPUT: Sources conflict, and no precedence rule resolves them.

  • BLOCKED: A required path, tool, or permission is unavailable.

Return:

Result: CONFIGURED | NEEDS_INPUT | INVALID_INPUT | BLOCKED
Operator: <name>
Task mode: <new | change | repair>
EMU policy: <optional | required>
Requirements: <count>
Correctness cases: <count>
Performance cases: <count>
Blocking questions: <count>
Specification: <absolute path>
Test matrix: <absolute path>
Evidence: <absolute path>
OpGen inputs: <absolute path>
Active workspace: <absolute path>

Stop after these outputs. Do not invoke OpGen.

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-spec · 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-spec.zip