Matlab Use Visual Inspection
matlab/matlab-agentic-toolkit
Build machine vision inspection systems with MATLAB Visual Inspection Toolbox.
Route Quark ONNX user goals to the correct atomic skill. An agent skill from amd/Quark.
$ npx skills add amd/Quark --skill quark-onnx-router -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install amd/Quark quark-onnx-router --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/amd/Quark.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills-impl/l1-atomic/onnx/quark-onnx-router .claude/skills/quark-onnx-router && rm -rf skills-srcUse ~/.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/
Install the "quark-onnx-router" agent skill from https://github.com/amd/Quark/tree/release%2F0.13/.claude/skills-impl/l1-atomic/onnx/quark-onnx-router into .claude/skills/quark-onnx-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quark-onnx-router", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/amd/Quark/tree/release%2F0.13/.claude/skills-impl/l1-atomic/onnx/quark-onnx-routerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add amd/Quark --skill quark-onnx-router -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install amd/Quark quark-onnx-router --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amd/Quark.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills-impl/l1-atomic/onnx/quark-onnx-router .agents/skills/quark-onnx-router && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "quark-onnx-router" agent skill from https://github.com/amd/Quark/tree/release%2F0.13/.claude/skills-impl/l1-atomic/onnx/quark-onnx-router into .agents/skills/quark-onnx-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quark-onnx-router", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add amd/Quark --skill quark-onnx-router -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install amd/Quark quark-onnx-router --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amd/Quark.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills-impl/l1-atomic/onnx/quark-onnx-router .cursor/skills/quark-onnx-router && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "quark-onnx-router" agent skill from https://github.com/amd/Quark/tree/release%2F0.13/.claude/skills-impl/l1-atomic/onnx/quark-onnx-router into .cursor/skills/quark-onnx-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quark-onnx-router", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/amd/Quark.git --path .claude/skills-impl/l1-atomic/onnx/quark-onnx-router--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add amd/Quark --skill quark-onnx-router -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install amd/Quark quark-onnx-router --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amd/Quark.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills-impl/l1-atomic/onnx/quark-onnx-router .gemini/skills/quark-onnx-router && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "quark-onnx-router" agent skill from https://github.com/amd/Quark/tree/release%2F0.13/.claude/skills-impl/l1-atomic/onnx/quark-onnx-router into .gemini/skills/quark-onnx-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quark-onnx-router", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install amd/Quark quark-onnx-routerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add amd/Quark --skill quark-onnx-router -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/amd/Quark.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills-impl/l1-atomic/onnx/quark-onnx-router .github/skills/quark-onnx-router && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "quark-onnx-router" agent skill from https://github.com/amd/Quark/tree/release%2F0.13/.claude/skills-impl/l1-atomic/onnx/quark-onnx-router into .github/skills/quark-onnx-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quark-onnx-router", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add amd/Quark --skill quark-onnx-router -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install amd/Quark quark-onnx-router --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amd/Quark.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills-impl/l1-atomic/onnx/quark-onnx-router .opencode/skills/quark-onnx-router && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "quark-onnx-router" agent skill from https://github.com/amd/Quark/tree/release%2F0.13/.claude/skills-impl/l1-atomic/onnx/quark-onnx-router into .opencode/skills/quark-onnx-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quark-onnx-router", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
quark-onnx-routerRoute Quark ONNX user goals to the correct atomic skill. An agent skill from amd/Quark.
Quark Onnx Router is an agent skill from amd/Quark. Route Quark ONNX user goals to the correct atomic skill. Use when a user describes an ONNX quantization task in plain language — such as "install onnxruntime", "analyze my .onnx model", "choose a preset for my YOLO model", "plan ONNX PTQ", "quantize this .onnx with XINT8/BFP16/MXFP4", "validate my quantized .onnx", "debug a failed ONNX quantization", or any request that involves Quark's ONNX-to-ONNX flow. This is the ONNX-side entry point — trigger it whenever the user's intent involves Quark ONNX and the correct…
Its SKILL.md is about 2.7k 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 LLM inference and serving, Computer vision and Plain language and style rules. It works with ONNX. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 313cb0b. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Quark Onnx Router loads about 2.7k tokens when it runs. Until then it costs about 145 tokens; SKILL.md has 1,189 words of instructions outside code blocks.
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.
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.
The full file from amd/Quark at commit 313cb0b, republished under its MIT licence (© amd). 1,189 words, ~2,658 tokens.
.claude/skills/quark-onnx-router/SKILL.md (or your agent's skills folder).Translate a user's natural-language ONNX quantization goal into the smallest correct skill boundary. The router exists because Quark's ONNX flow spans install, intake, planning, execution, debug, and validation — picking the wrong skill wastes time and produces wrong artifacts. The router is the sole producer of session_context.json for the ONNX backend; every other artifact (env, workspace, install results, model analysis, quant plan) is produced by its own owning skill, and the router only carries forward references to those files.
env_context.json (optional, when routing depends on hardware / execution-provider facts)workspace_context.json (optional, when routing depends on validated .onnx / .onnx_data paths)Carries the user goal, selected workflow (or atomic skill if no workflow applies), constraints with backend = "onnx", *_ref pointers to other artifacts, and unresolved questions.
Schema: session_context.schema.json
{
"user_goal": "Quantize ./models/yolov8n.onnx with XINT8 and validate against the FP32 baseline",
"workflow": "quark-onnx-ptq-workflow",
"constraints": {
"backend": "onnx",
"offline": false,
"execution_mode": "interactive_execute"
},
"env_context_ref": null,
"workspace_context_ref": null,
"onnx_install_result_ref": null,
"quark_install_result_ref": null,
"model_analysis_ref": null,
"quant_plan_ref": null,
"open_questions": [
"Deployment target (CPU / CUDA / ROCm / NPU CNN / NPU Transformer) not yet confirmed — affects preset gating in quark-onnx-quant-plan"
]
}Set each *_ref field to the path of the corresponding artifact once its producer skill has run. The router never embeds hardware, workspace, install, model, or plan facts inline — those belong in their owning artifacts. Always set constraints.backend = "onnx" so downstream skills and any future cross-backend orchestrator can disambiguate from the Torch flow.
Vision / CNN .onnx PTQ requests MUST route to quark-onnx-ptq-workflow.
Signals: model name contains yolo, resnet, mobilenet, efficientnet, etc.; inputs are image tensors [N, C, H, W]; preset is XINT8 / A8W8 / A16W8 / BF16 / BFP16; user mentions mAP / Prec@1 / NPU CNN / Ryzen AI.
Examples:
quark-onnx-ptq-workflowquark-onnx-ptq-workflowquark-onnx-ptq-workflowNEVER invoke quark.onnx.ModelQuantizer.quantize_model(...) directly from within the router. Execution belongs inside the workflow, after a confirmed quant_plan.json and a generated script the user has reviewed (the workflow's 4-step flow: intake → plan → manifest+script → confirmed execution).
| User Intent | Target Skill | Why |
|---|---|---|
| Quantize a .onnx vision/CNN model (YOLO / ResNet / MobileNet / …) | quark-onnx-ptq-workflow | Vision-specific: image data reader, CNN presets (XINT8 / A8W8 / BFP16), EnableNPUCnn, mAP / Prec@1 eval |
Full end-to-end ONNX PTQ: from .onnx to quantized .onnx | quark-onnx-ptq-workflow | Multi-step workflow orchestration |
| Install ONNX Runtime, fix CPU/GPU variant, missing CUDA/ROCm EP | quark-onnx-install | ONNX Runtime install is separate from Quark package install |
| Install Quark, set up Quark dependencies | quark-install | Backend-neutral Quark package install (assumes ORT already set up) |
Inspect a .onnx model, check opset / IR / op-type histogram, NPU compatibility | quark-onnx-model-intake | Model facts are prerequisites for planning |
| Choose preset (XINT8 / A8W8 / BFP16 / MX* / MatMulNBits), calibration method, algorithm | quark-onnx-quant-plan | Planning is separate from execution |
| Debug a failed ONNX quantization, ORT EP error, custom-op load failure, calibration crash | quark-onnx-debug | Error recovery has its own diagnostic flow |
Validate quantized .onnx, verify QDQ insertion, check non-quantized initializers | quark-onnx-result-validator | Post-quantization byte-level + structural validation |
| Check environment, detect GPU, verify setup | quark-env-preflight | L0 fact collection (shared backend-neutral) |
Validate .onnx / .onnx_data paths, output directory | quark-workspace-validate | L0 path validation (shared backend-neutral) |
Confirm the backend. If the user mentions .onnx, quantize_static, ModelQuantizer, an ONNX Runtime execution provider, opset, or QDQ, treat the request as ONNX. If they mention HuggingFace, safetensors, transformers, torch._dynamo, or quantize_quark.py, hand off to quark-torch-router instead — never silently mix backends.
Extract the core intent. Strip filler and figure out what the user actually needs. "I want to quantize yolov8n.onnx with XINT8 for CPU" → vision PTQ → quark-onnx-ptq-workflow.
Check for L0 prerequisites. Before routing to an L1 skill, check if downstream skills need facts that are missing:
quark-env-preflight first..onnx (and any sibling .onnx_data) path or output directory needs validation → run quark-workspace-validate first.Pick the smallest fit. If the user only wants to inspect a .onnx graph, route to quark-onnx-model-intake — do not start the full workflow. If they only want to install ORT, route to quark-onnx-install. But if they say "quantize my .onnx", use quark-onnx-ptq-workflow.
Handle ambiguity honestly. If the goal is unclear, record the likely routes in open_questions and ask. Example: "I want to use Quark with my ONNX model" — does that mean inspect, plan, quantize end-to-end, or validate an already-quantized file?
quark-onnx-quant-plan depends on this..onnx files in the router. The router only reads paths and string intent; loading the model is quark-onnx-model-intake's job (especially relevant for >2 GB models with external data).session_context.json already exists from a previous step, read it and carry forward — do not start from scratch..onnx into quark-torch-*; never feed safetensors into quark-onnx-*. If the user's input doesn't match this router's backend, hand off to quark-torch-router.session_context.json (with constraints.backend = "onnx") and pass control to the chosen skill.quark-onnx-quant-plan without a model_analysis.json).session_context.json with the gaps documented rather than forcing a premature routing decision.quark-torch-router and stop.User: "Quantize ./models/yolov8n.onnx with XINT8 for Ryzen AI deployment, output to ./output/yolov8n-xint8.onnx" Router: →
quark-onnx-ptq-workflow(vision task family: YOLO + XINT8 + NPU CNN) Explain: "I'll quantize your YOLOv8 ONNX model with the vision PTQ workflow: 4 steps (intake → plan → generated script + manifest → confirmed execution)."
User: "I need to install onnxruntime-rocm 7.1" Router: →
quark-onnx-install(clear ORT install intent, EP stated)
User: "
quantize_staticis failing with 'CUDAExecutionProvider not available'" Router: →quark-onnx-debug(ORT EP error, established diagnostic flow)
User: "Here's the quantized output — did the QDQ insertion actually happen?" Router: →
quark-onnx-result-validator
User: "I want to use Quark with my ONNX model" Router: Ask — "Do you want to: (a) inspect the graph's opset and op-types, (b) plan and run a full PTQ, (c) install ONNX Runtime / Quark first, or (d) validate an already-quantized output?"
User: "Quantize Qwen/Qwen3-8B with FP8" (HuggingFace repo id, no
.onnx) Router: Hand off →quark-torch-routerand stop. Do not attempt to route this through the ONNX flow.
© amd, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills-impl/l1-atomic/onnx/quark-onnx-router of amd/Quark.
Open the folder on GitHubat commit 313cb0b
Quark Onnx Router 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Quark Onnx Router this skillamd/Quark | 181 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Matlab Use Visual Inspectionmatlab/matlab-agentic-toolkit | 1.1k | — | ~3.1k | Automated safety check: Pass | Custom licence | |
| Contextpilot SavingsEfficientContext/ContextPilot | 140 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Tao Finetune ClipNVIDIA/skills | 3.5k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Tao Port Huggingface ModelNVIDIA/skills | 3.5k | — | ~4.5k | Automated safety check: Notes | Apache-2.0 | |
| Segment Anything Model GuideOrchestra-Research/AI-Research-SKILLs | 13k | 8 repos | ~3.3k | Automated safety check: Pass | MIT |
matlab/matlab-agentic-toolkit
Build machine vision inspection systems with MATLAB Visual Inspection Toolbox.
EfficientContext/ContextPilot
A skill your agent uses when a user asks how many tokens (or how much context/cost) ContextPilot has saved, or wants a ContextPilot savings status/summary inside Hermes Agent — e.g.
NVIDIA/skills
CLIP vision-language model for image-text retrieval, zero-shot classification, embedding extraction, ONNX export, and TensorRT deployment.
NVIDIA/skills
Integrate a HuggingFace Computer Vision model into the NVIDIA TAO Toolkit ecosystem (tao-core config, tao-pytorch trainer, tao-deploy TensorRT pipeline).
Orchestra-Research/AI-Research-SKILLs
Guide to using Meta's Segment Anything Model for zero-shot image segmentation with point, box or mask prompts, or automatic mask generation.
gridaco/grida
Query images with a local Ollama vision model without loading the image into the main agent context.
amd/Quark
Author or restructure a Quark Agent Skill so it conforms to this project's template, contracts, and layer rules.
amd/Quark
Run, resume, monitor, diagnose, and report Quark Quant-Perf workflows for PyTorch and HuggingFace transformers models.
amd/Quark
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.
amd/Quark
Collect and normalize environment facts (OS, Python, GPU, CUDA/ROCm, container state) before Quark installation or PTQ planning.
amd/Quark
Install or verify the AMD Quark package and its dependencies.
amd/Quark
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…
Works with
Categories
Route Quark ONNX user goals to the correct atomic skill. An agent skill from amd/Quark. Quark Onnx Router is an agent skill from amd/Quark. Route Quark ONNX user goals to the correct atomic skill.
Quark Onnx Router fits situations like: A user describes an ONNX quantization task in plain language — such as install onnxruntime; analyze my .onnx model; choose a preset for my YOLO model; quantize this .onnx with XINT8/BFP16/MXFP4.
Run `npx skills add amd/Quark --skill quark-onnx-router -a claude-code`. Or copy the skill folder (.claude/skills-impl/l1-atomic/onnx/quark-onnx-router in amd/Quark) into .claude/skills/quark-onnx-router in your project. Claude Code loads it when a task matches its description.
Run `npx skills add amd/Quark --skill quark-onnx-router -a codex`. Or copy the skill folder (.claude/skills-impl/l1-atomic/onnx/quark-onnx-router in amd/Quark) into .agents/skills/quark-onnx-router in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add amd/Quark --skill quark-onnx-router -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-onnx-router, .gemini/skills/quark-onnx-router, .github/skills/quark-onnx-router and .opencode/skills/quark-onnx-router in your project.
SKILL.md names no scripts, command-line tools or credentials: Quark Onnx Router is instructions for the agent only.
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.
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.
Quark Onnx Router is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Quark Onnx Router: Matlab Use Visual Inspection (matlab/matlab-agentic-toolkit, 1.1k stars), Contextpilot Savings (EfficientContext/ContextPilot, 140 stars), Tao Finetune Clip (NVIDIA/skills, 3.5k stars) and Tao Port Huggingface Model (NVIDIA/skills, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.