quark-workspace-validate

Validate workspace paths, model references, and output directories before Quark workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents downstream Quark workflows from failing due to missing model paths, invalid output directories, or incorrect repository assumptions. It validates workspace facts first so quantization and export steps can proceed with confidence.

Core Features & Use Cases

  • Model Path Validation: Checks whether a reference is a local model directory, a HuggingFace-style model ID, or an ambiguous path that needs clarification.
  • Output Directory Validation: Confirms the output location exists or can be created, and verifies the parent directory is writable.
  • Repository Sanity Check: Confirms the expected Quark source layout when running from repository source.
  • Use Case: Before starting a PTQ or export job, use this Skill to verify the model location, output folder, and disk readiness.

Quick Start

Use the quark-workspace-validate skill to check my model path, output directory, and repository locations before I run quantization.

Frequently Asked Questions about quark-workspace-validate

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

FAQPage Schema
How do I validate model paths before running Quark quantization?

To validate model paths before Quark quantization, use a workspace validation skill to confirm whether your reference is a local directory or HuggingFace ID, checking filesystem existence and permissions.

Why does my quantization export fail due to an invalid output directory?

Quantization exports fail when the output directory does not exist or lacks write permissions. Workspace validation confirms the output location can be created and verifies the parent directory is writable before execution.

How do I check disk space and permissions for a PTQ workflow setup?

Checking disk space and permissions for a PTQ workflow involves validating filesystem readiness. This ensures the target directories are writable and have sufficient disk space to support reliable quantization execution inputs.

Can I use HuggingFace model identifiers directly for Quark workspace validation?

HuggingFace model identifiers can be used directly for Quark workspace validation. The validation process distinguishes between local model directories and HuggingFace-style IDs to resolve ambiguous paths before quantization.

What is the best way to verify Quark source repository layout before running PTQ tasks?

The best way to verify a Quark source repository layout is a repository sanity check. This confirms the expected source structure is correct before running downstream post-training quantization or export jobs.