MiniMax H3量化兼容检查

Use this skill before running a local MiniMax H3 checkpoint or a quantized derivative. It validates a redacted runtime contract offline and prevents mixing task families, precision assumptions, or incompatible VAE metadata.

Prerequisites

• - Python 3.9 or newer.
• A UTF-8 JSON contract with task_family, checkpoint_format, precision, vae_variant, framework, gpu_count, vram_gb, ram_gb, and disk_gb.
• The buyer\'s own checkpoint manifest and machine inventory. This skill does not inspect or download weights.

Inputs and outputs

Run python scripts/check_compat.py examples/pass_contract.json --out compatibility.json --report compatibility.md.

The checker verifies a recognized H3 task family, a declared format and precision, matching VAE metadata, non-negative resource values, a local checkpoint path label without a secret, and a completed license/weight-source review. It emits JSON and Markdown reports with an explicit run_authorized: false boundary.

Execution and acceptance

1. 1. Copy the redacted example and replace inventory values with facts from the buyer\'s environment.
2. Run the checker. Exit code 0 means the metadata is internally consistent; exit code 1 means hold the run.
3. Separately confirm the current H3 repository, framework version, quantization implementation, device topology, model license, and required VAE components before loading anything.

This is a compatibility gate, not a performance or quality guarantee. It cannot prove that weights exist, fit in memory, preserve quality, or support every optimization.

Privacy and recovery

Do not place account tokens, private model URLs, real customer data, or full local paths in examples. If precision, VAE, task family, hardware, or license facts are unknown, stop and obtain an authoritative manifest instead of guessing.

Standalone use

The checker is independently useful for a local runbook or handoff to SGLang, vLLM, diffusers, or ComfyUI operators. The companion auditor is optional.