quark-onnx-doc-drift-check

Compare Quark ONNX skill guidance against upstream docs and source.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers verify that Quark ONNX user guidance still matches the current upstream documentation and source code, preventing stale advice from breaking installs, workflows, or generated scripts.

Core Features & Use Cases

  • Documentation drift detection: Checks whether preset names, calibration methods, algorithm configs, QConfig fields, custom ops, and AutoSearchPro presets still exist upstream.
  • Install and runtime validation: Compares ORT package/version guidance, execution provider names, and deployment-target rules against authoritative Quark files.
  • Workflow accuracy review: Helps confirm that example invocations and contract schemas still align with the actual ONNX quantization APIs and docs.

Quick Start

Ask the Skill to compare the current Quark ONNX documentation and source against the ONNX skill guidance and report any drift.

Frequently Asked Questions about quark-onnx-doc-drift-check

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

FAQPage Schema
How do I detect documentation drift in Quark ONNX quantization guides?

Detect documentation drift by comparing Quark ONNX skill guidance against upstream documentation and source code to find stale presets, configs, and install instructions.

What is documentation drift in ONNX quantization workflows?

Documentation drift occurs when Quark ONNX user guidance loses alignment with upstream source, causing outdated preset names, incorrect install instructions, and broken example scripts.

How to validate Quark ONNX install instructions against upstream source?

Validate Quark ONNX install instructions by performing read-only inspection of ORT package versions, execution provider names, and deployment rules against authoritative upstream source files.

Does this documentation drift check inspect Quark ONNX source code directly?

Yes, the drift check performs read-only inspection of Quark ONNX source entry points to confirm technical accuracy of workflow assumptions, example scripts, and custom ops.

Can I verify AutoSearchPro presets and custom ops still exist upstream?

Yes, you can verify AutoSearchPro presets and custom ops by comparing current Quark ONNX skill guidance against upstream documentation to confirm these configurations still exist.

When should I check for stale Quark ONNX quantization documentation?

Check for stale Quark ONNX quantization documentation during release-driven changes when preset names, algorithm configs, or deployment-target rules may have shifted in the upstream source.