quark-torch-model-intake

Analyze HuggingFace model architectures for Quark PTQ planning readiness.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you inspect a target model before quantization so you can avoid downstream failures from incompatible architectures, missing config details, or unsupported loading requirements.

Core Features & Use Cases

  • Model validation: Confirm whether a model path is local or remote and gather the facts needed for Quark planning.
  • Architecture analysis: Detect model family, hidden layer counts, MoE status, and quantizable layer structure.
  • Compatibility checks: Identify transformers version constraints, custom loading needs, and risk factors that affect PTQ readiness.
  • Use case: Before running Quark PTQ on a new LLM, use this Skill to determine whether the model needs trust_remote_code, special template handling, or extra preparation for MoE layers.

Quick Start

Ask the assistant to analyze your model path and return a Quark-ready summary of architecture, quantization targets, compatibility requirements, and risks.

Frequently Asked Questions about quark-torch-model-intake

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

FAQPage Schema
How do I validate a HuggingFace model for Quark PTQ quantization readiness?

Model validation for Quark PTQ checks architecture, layer counts, and quantization readiness without loading full model weights. It inspects model configurations to identify transformer compatibility constraints, custom loading needs like trust_remote_code, and risk factors affecting post-training quantization.

Can I check MoE status and layer counts before running LLM quantization?

Architecture analysis detects model family, hidden layer counts, and MoE status by inspecting the model path. This identifies the quantizable layer structure and determines whether MoE layers require extra preparation before applying post-training quantization.

Does Quark PTQ require trust_remote_code for custom transformer architectures?

Compatibility checks identify transformers version constraints and whether custom loading needs like trust_remote_code are required. This validation assesses risk factors and special template handling needs to ensure the model architecture is ready for post-training quantization.

What are common limitations when analyzing local model directories for quantization?

Analyzing local model directories for quantization faces limitations from missing config details and unsupported loading requirements. The assessment extracts structural facts without loading full model weights, so incomplete configurations can prevent accurate risk evaluation and quantization readiness checks.

How do I assess quantization risks for a target LLM without loading full model weights?

Risk assessment for quantization validates transformer compatibility and checks configuration details without loading full model weights. It extracts structural facts like architecture and MoE status to identify risk factors that could cause downstream failures during post-training quantization.