quark-onnx-install

Install and verify ONNX Runtime stacks for AMD Quark workflows.

154|27|Updated Jun 19, 2024
One-click install
npx skills add https://github.com/amd/Quark --skill quark-onnx-install
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quark-onnx-install
Source: https://github.com/amd/Quark/tree/main/.claude/skills-impl/l1-atomic/onnx/quark-onnx-install
Command: npx skills add https://github.com/amd/Quark --skill quark-onnx-install

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from setting up ONNX Runtime for AMD Quark’s ONNX-to-ONNX workflow, helping you avoid provider mismatches, missing execution providers, and import failures before quantization begins.

Core Features & Use Cases

  • Backend-specific installation planning: Chooses the correct ONNX Runtime variant for CPU, CUDA, or ROCm environments.
  • Compatibility verification: Checks ONNX, ONNX Runtime, and related package versions against Quark’s supported ranges.
  • Custom ops readiness: Ensures Quark’s ONNX custom operators can compile and load correctly in the local environment.
  • Use case: If a user reports that import onnxruntime fails or the wrong execution provider is available, this Skill guides the exact reinstall and verification path.

Quick Start

Ask the skill to diagnose your accelerator backend and produce the exact ONNX Runtime installation and verification steps for Quark.

Frequently Asked Questions about quark-onnx-install

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

FAQPage Schema
How do I fix ONNX Runtime import failures before running AMD Quark quantization?

To fix ONNX Runtime import failures, diagnose your accelerator backend and reinstall the correct runtime variant for your CPU, CUDA, or ROCm environment. This ensures version compatibility and resolves execution provider mismatches before quantization begins.

Why does ONNX Runtime show the wrong execution provider for my CUDA or ROCm setup?

The wrong execution provider appears due to package conflicts or version mismatches between ONNX Runtime and your CUDA or ROCm environment. Version-aware package selection and provider validation are required to align the runtime with your specific backend.

What's the best way to verify ONNX Runtime compatibility with AMD Quark?

The best way to verify ONNX Runtime compatibility is to check ONNX, ONNX Runtime, and related package versions against Quark’s supported ranges. This compatibility verification prevents import failures and custom-ops compilation issues during quantization.

Do I need to compile custom ops for Quark ONNX workflows?

Yes, you need to ensure Quark’s ONNX custom operators can compile and load correctly in your local environment. Custom ops readiness checks validate that the installed runtime stack supports the specific operations required for quantization.

How to install the correct ONNX Runtime stack for ROCm environments?

To install ONNX Runtime for ROCm environments, apply backend-specific installation planning to choose the correct ROCm-compatible runtime variant. This approach avoids execution provider mismatches and package conflicts that block AMD Quark quantization.