pto-gym-vpto-validation

Validate PTO-Gym cases using the PTOAS VPTO backend with A5 flags.

30|74|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/hw-native-sys/PTOAS --skill pto-gym-vpto-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pto-gym-vpto-validation
Source: https://github.com/hw-native-sys/PTOAS/tree/main/.codex/skills/pto-gym-vpto-validation
Command: npx skills add https://github.com/hw-native-sys/PTOAS --skill pto-gym-vpto-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents PTO-Gym validation runs from accidentally using the repository default PTOAS backend instead of the required VPTO LLVM path.

Core Features & Use Cases

  • VPTO Backend Enforcement: Applies the required PTOAS flags for VPTO compilation and A5 architecture targeting.
  • Validation Execution: Runs individual PTO-Gym cases or parallel micro-operation sweeps with canonical workspace and simulator settings.
  • Result Reporting: Captures PASS/FAIL totals, identifies the first failing case, and points to the relevant summary and case directories.
  • Use Case: Run a PTO-Gym micro-operation validation sweep and inspect the generated summary for failures under the repository-local work directory.

Quick Start

Use the PTO-Gym VPTO validation skill to run the requested exercise cases with the required VPTO backend flags and report the results.

Frequently Asked Questions about pto-gym-vpto-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate PTO-Gym cases using the VPTO backend?

To validate PTO-Gym cases using the VPTO backend, execute the PTOAS simulator with the --pto-backend=vpto and --pto-arch a5 flags. This configuration runs individual exercises or parallel micro-operation sweeps while recording outputs under the .work directory.

Why do my PTO-Gym validation runs use the wrong PTOAS backend?

PTO-Gym validation runs use the wrong PTOAS backend when the required VPTO LLVM path flags are not explicitly applied. Enforce the VPTO backend by setting --pto-backend=vpto and --pto-arch a5 during execution to prevent falling back to repository defaults.

How do I run a parallel micro-operation sweep for PTOAS on A5 architecture?

Running a parallel micro-operation sweep for PTOAS on A5 architecture requires setting the --pto-arch a5 flag alongside the --pto-backend=vpto flag. This executes the simulator-based validation sweep and captures the resulting PASS/FAIL summaries in the repository-local work directory.

Where are PTO-Gym simulator validation summaries recorded?

PTO-Gym simulator validation summaries are recorded under the .work directory in the repository. This workspace captures temporary outputs and validation totals, pointing to the relevant summary files and directories for any identified first failing case.

Can I use the repository default PTOAS backend for PTO-Gym exercise validation?

You cannot use the repository default PTOAS backend for PTO-Gym exercise validation if VPTO is required. This Skill enforces the VPTO LLVM backend and A5 architecture targeting to ensure cases are validated correctly and prevent accidental default backend usage.

What PTOAS flags are required to target the A5 architecture with VPTO?

Targeting the A5 architecture with VPTO requires applying the --pto-backend=vpto and --pto-arch a5 flags. These settings ensure PTO-Gym exercise cases are processed through the correct VPTO LLVM path during simulator validation.