Agent skill

Quark Workspace Validate

by amd in amd/Quark

Validate workspace shape, model paths, output directories, and repo structure before downstream Quark skills proceed.

MITAuto-check passedAI & LLM Engineering

Install Quark Workspace Validate

skills CLI
$ npx skills add amd/Quark --skill quark-workspace-validate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install amd/Quark quark-workspace-validate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/amd/Quark.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills-impl/l0-foundation/shared/quark-workspace-validate .claude/skills/quark-workspace-validate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
quark-workspace-validate
GitHub stars
181
Token cost
~1.3k tokens
SKILL.md length
497 words
Files
1
Skills in repo
37
Repo updated
First seen
Licence
MIT

At a glance

Validate workspace shape, model paths, output directories, and repo structure before downstream Quark skills proceed.

  • Works in 3 steps: Local directory — contains config.json,… → HuggingFace ID — format org/model-name… → Ambiguous — could be either (e.g.,…
  • A skill needs confirmed file paths
  • SKILL.md covers Purpose, Inputs, Outputs: workspace_context.json and What to Validate, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Quark Workspace Validate is an agent skill from amd/Quark. Validate workspace shape, model paths, output directories, and repo structure before downstream Quark skills proceed. Use this skill whenever a skill needs confirmed file paths, when the user provides a model path or output directory, when you need to distinguish a local model from a HuggingFace ID, or when any path assumption is unverified. Also trigger for "where should I put outputs", "is my model path right", or before model-intake/export steps.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering, covering Model hubs and datasets. It works with Hugging Face and Qwen. The licence is MIT.

When your agent uses it

  • A skill needs confirmed file paths
  • The user provides a model path
  • Output directory
  • You need to distinguish a local model from a HuggingFace ID

Example prompts

  • “where should I put outputs”
  • “is my model path right”
  • “/quark-workspace-validate”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Local directory — contains config.json, *.safetensors or *.bin files (e.g., /models/Llama-2-7b-hf/)
  2. HuggingFace ID — format org/model-name (e.g., Qwen/Qwen3-8B)
  3. Ambiguous — could be either (e.g., ./qwen3-8b might be a local dir or a typo)

What it can do on your machine

Read from SKILL.md and the folder at commit 313cb0b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json and bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quark Workspace Validate loads about 1.3k tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 497 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~120
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from amd/Quark at commit 313cb0b, republished under its MIT licence (© amd). 497 words, ~1,290 tokens.

Download SKILL.mdSave it as .claude/skills/quark-workspace-validate/SKILL.md (or your agent's skills folder).
name
quark-workspace-validate
description
Validate workspace shape, model paths, output directories, and repo structure before downstream Quark skills proceed. Use this skill whenever a skill needs confirmed file paths, when the user provides a model path or output directory, when you need to distinguish a local model from a HuggingFace ID, or when any path assumption is unverified. Also trigger for "where should I put outputs", "is my model path right", or before model-intake/export steps.
layer
l0-foundation
primary_artifact
workspace_context.json
source_knowledge
examples/torch/language_modeling/llm_ptq/README.md, examples/torch/language_modeling/llm_ptq/quantize_quark.py

quark-workspace-validate

Purpose

Validate that file paths, model references, and output locations actually exist and are accessible before a downstream skill depends on them. This prevents silent failures where a PTQ run starts, spends time loading a model, and then crashes because the output directory does not exist or the model path has a typo.

Inputs

  • Model path and output directory from the user (typically forwarded by quark-torch-router)

Outputs: workspace_context.json

Records validated model paths, output directory, and repo locations.

Schema: workspace_context.schema.json

json
{
  "model_path": "/models/Qwen3-8B",
  "model_source": "local",
  "trust_remote_code_required": false,
  "output_dir": "./output/qwen3-8b-fp8",
  "output_dir_exists": false,
  "output_dir_parent_writable": true,
  "disk_space_gb_free": 250,
  "quark_script_path": null
}

workspace_context.json is for path facts only. Unresolved questions (e.g., ambiguous local-vs-HuggingFace reference) belong in session_context.json (owned by quark-torch-router).

What to Validate

Model Path

A model reference can be one of three things:

  1. Local directory — contains config.json, *.safetensors or *.bin files (e.g., /models/Llama-2-7b-hf/)
  2. HuggingFace ID — format org/model-name (e.g., Qwen/Qwen3-8B)
  3. Ambiguous — could be either (e.g., ./qwen3-8b might be a local dir or a typo)

For local paths, check:

  • Directory exists
  • config.json is present (minimum requirement for HuggingFace-compatible model)
  • At least one weight file exists (.safetensors, .bin, or .pth)
  • Read permissions are adequate

For HuggingFace IDs, note:

  • Cannot fully validate without network access
  • Check format: should contain / separator
  • Record whether trust_remote_code will be needed (some models like DeepSeek VL v2 require it)
Output Directory
  • Check that the parent directory exists and is writable
  • If the output directory itself does not exist, note that it will be created (not an error)
  • Warn if the directory already contains files (risk of overwriting previous results)
Quark Repository (if applicable)
  • If the user is running from source, check for quantize_quark.py at the expected location: examples/torch/language_modeling/llm_ptq/quantize_quark.py
  • Check that requirements.txt dependencies are likely installed

Validation Commands

bash
# Check model directory
ls -la /path/to/model/config.json 2>/dev/null
ls /path/to/model/*.safetensors 2>/dev/null

# Check output directory parent
test -d /path/to/output/.. && echo "parent exists"
test -w /path/to/output/.. && echo "parent writable"

# Check disk space (rough)
df -h /path/to/output/..
Show full SKILL.md (227 more words)Show less

Rules

  • Only validate existence, accessibility, and shape. Do not analyze model internals (that is quark-torch-model-intake) or choose install paths (that is quark-install).
  • Never invent replacement paths. If /data/models/llama does not exist, say so — do not suggest /data/models/llama-2 as an alternative unless the user asks.
  • Preserve ambiguity explicitly. When a reference like meta-llama/Llama-2-7b could be local or remote, say: "This looks like a HuggingFace model ID. If you meant a local directory, the path does not exist at ./meta-llama/Llama-2-7b."
  • Check disk space when the downstream task is PTQ or export — quantized models can be large.

Interaction Flow

  1. Collect: Gather the paths the downstream skill needs — model path, output directory, any referenced config files.
  2. Validate: Run existence and permission checks. Present results as a checklist with pass/fail for each item.
  3. Clarify: For ambiguous references, ask the user. For missing paths, report the exact issue.
  4. Emit: Write confirmed facts to workspace_context.json. Hand any unresolved items back to quark-torch-router so they land in session_context.json's open_questions.

Recovery

  • If a required path is missing, report the exact path tested and what was expected. Suggest the smallest fix: "Directory /data/models/llama does not exist. Did you mean /data/models/Llama-2-7b-hf?"
  • If a model reference is ambiguous between local and HuggingFace, keep it unresolved and ask — do not guess.
  • If disk space is low for the intended output, warn with the estimated size needed.

© amd, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills-impl/l0-foundation/shared/quark-workspace-validate of amd/Quark.

Open the folder on GitHubat commit 313cb0b

Compare with similar skills

Quark Workspace Validate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quark Workspace Validate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quark Workspace Validate this skillamd/Quark181—~1.3kAutomated safety check: PassMIT
Qwen Mtp GgufR6410418/Jackrong-llm-finetuning-guide1.7k—~1.7kAutomated safety check: PassMIT
Veomni New ModelByteDance-Seed/VeOmni2.2k—~2kAutomated safety check: PassApache-2.0
Add Modelguoqingbao/xinfer333—~4.2kAutomated safety check: NotesMIT
Resolvealexziskind1/model-shelf130—~792Automated safety check: PassMIT
Check Modelguoqingbao/xinfer333—~3.8kAutomated safety check: PassMIT

Similar skills

  • Qwen Mtp Gguf

    R6410418/Jackrong-llm-finetuning-guide

    Complete agent-ready workflow for Qwen-family MTP or nextn GGUF conversion and release.

    1.7k GitHub stars~1.7k tokensUpdated 2 mo ago
    AI & LLM EngineeringAuto-check passed
  • Veomni New Model

    ByteDance-Seed/VeOmni

    A skill your agent uses when adding support for a new model to VeOmni.

    2.2k GitHub stars~2k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Add Model

    guoqingbao/xinfer

    Adapt and port new LLM model architectures to this xinfer project.

    333 GitHub stars~4.2k tokensUpdated 29 days ago
    AI & LLM EngineeringAuto-check: notes
  • Resolve

    alexziskind1/model-shelf

    Always resolve Hugging Face models via model-shelf before any download.

    130 GitHub stars~792 tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check passed
  • Check Model

    guoqingbao/xinfer

    Check model compatibility with xinfer before loading. An agent skill from guoqingbao/xinfer.

    333 GitHub stars~3.8k tokensUpdated 29 days ago
    AI & LLM EngineeringAuto-check passed
  • Test Model

    guoqingbao/xinfer

    Test LLM models served by xinfer for correctness, output quality, and performance.

    333 GitHub stars~2.6k tokensUpdated 29 days ago
    AI & LLM EngineeringAuto-check passed

More from amd/Quark

All 37 skills in this repo
  • Author or restructure a Quark Agent Skill so it conforms to this project's template, contracts, and layer rules.

    181 GitHub stars~3.1k tokensUpdated 10 days ago
    Auto-check passed
  • Run, resume, monitor, diagnose, and report Quark Quant-Perf workflows for PyTorch and HuggingFace transformers models.

    181 GitHub stars~3k tokensUpdated 10 days ago
    Auto-check passed
  • Author a new ShapeShifter graph-transformation pass for AMD Quark (ONNX or PyTorch) so it conforms to the pass framework's conventions and auto-registers.

    181 GitHub stars~2.9k tokensUpdated 10 days ago
    Auto-check passed
  • Collect and normalize environment facts (OS, Python, GPU, CUDA/ROCm, container state) before Quark installation or PTQ planning.

    181 GitHub stars~1.4k tokensUpdated 10 days ago
    Auto-check passed
  • Quark Install

    amd/Quark

    Install or verify the AMD Quark package and its dependencies.

    181 GitHub stars~1.8k tokensUpdated 10 days ago
    Auto-check: notes
  • L3 recipe that runs quark.onnx.AutoSearchPro end-to-end on a user .onnx model: intake → preset selection (or custom search space) → calibration / eval data reader → standalone autosearch script…

    181 GitHub stars~3.4k tokensUpdated 10 days ago
    Auto-check passed

Questions about Quark Workspace Validate

What does Quark Workspace Validate do?

Validate workspace shape, model paths, output directories, and repo structure before downstream Quark skills proceed. Quark Workspace Validate is an agent skill from amd/Quark. Validate workspace shape, model paths, output directories, and repo structure before downstream Quark skills proceed.

When should I use Quark Workspace Validate?

Quark Workspace Validate fits situations like: A skill needs confirmed file paths; the user provides a model path; output directory; you need to distinguish a local model from a HuggingFace ID.

How do I install Quark Workspace Validate in Claude Code?

Run `npx skills add amd/Quark --skill quark-workspace-validate -a claude-code`. Or copy the skill folder (.claude/skills-impl/l0-foundation/shared/quark-workspace-validate in amd/Quark) into .claude/skills/quark-workspace-validate in your project. Claude Code loads it when a task matches its description.

How do I install Quark Workspace Validate in Codex?

Run `npx skills add amd/Quark --skill quark-workspace-validate -a codex`. Or copy the skill folder (.claude/skills-impl/l0-foundation/shared/quark-workspace-validate in amd/Quark) into .agents/skills/quark-workspace-validate in your project. Codex loads it when a task matches its description.

Can I use Quark Workspace Validate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add amd/Quark --skill quark-workspace-validate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quark-workspace-validate, .gemini/skills/quark-workspace-validate, .github/skills/quark-workspace-validate and .opencode/skills/quark-workspace-validate in your project.

What does Quark Workspace Validate need to run?

SKILL.md names no scripts, command-line tools or credentials: Quark Workspace Validate is instructions for the agent only.

Does Quark Workspace Validate access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Quark Workspace Validate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Quark Workspace Validate use?

Quark Workspace Validate is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quark Workspace Validate use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Quark Workspace Validate?

Skills that share tags, products or a category with Quark Workspace Validate: Qwen Mtp Gguf (R6410418/Jackrong-llm-finetuning-guide, 1.7k stars), Veomni New Model (ByteDance-Seed/VeOmni, 2.2k stars), Add Model (guoqingbao/xinfer, 333 stars) and Resolve (alexziskind1/model-shelf, 130 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quark Workspace Validate?

amd (a GitHub organization) maintains it in amd/Quark, which has 181 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on September 28, 2026.

Source: amd/Quark on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.