Agent skill

Model Builder

by qualcomm in qualcomm/qai-appbuilder

QAI ModelBuilder. An agent skill from qualcomm/qai-appbuilder.

BSD-3-ClauseAuto-check passedAI & LLM Engineering

Install Model Builder

skills CLI
$ npx skills add qualcomm/qai-appbuilder --skill model-builder -a claude-code

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

GitHub CLI
$ gh skill install qualcomm/qai-appbuilder model-builder --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/qualcomm/qai-appbuilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tools/qaiappbuilder/factory/chat_features/model-builder .claude/skills/model-builder && 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
model-builder
GitHub stars
246
Token cost
~4.1k tokens
SKILL.md length
1,760 words
Files
50 (incl. scripts, references, assets)
Skills in repo
13
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

QAI ModelBuilder. An agent skill from qualcomm/qai-appbuilder.

  • Works in 8 steps: Export to ONNX — python_x64_venv,… → Inspect ONNX I/O —… → Operator patching — ONLY if actual… → …
  • Working with custom ONNX/PyTorch models — export to ONNX
  • SKILL.md covers 🚨 Boundary Decision — pass…, 🧭 Routing Table — load only…, Core Workflow (8-step spine) and 🛑 Blocking Conditions (always…, plus 2 more sections
  • Calls pip

What it does

Model Builder is an agent skill from qualcomm/qai-appbuilder. QAI ModelBuilder. Tools and workflows for model conversion, inspection, operator patching, quantization, and inference validation of self-converted models on Qualcomm platform. Use this skill when working with custom ONNX/PyTorch models — export to ONNX, convert to QNN/SNPE DLC, FP16/FP32/INT8 quantization, operator patching, context binary generation, and inference validation of self-built models. NOT for AI Hub prebuilt packages — use model-hub skill instead.

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 51 other files, including scripts, reference files and assets (for example `README.md`, `assets/plan.md` and `references/adb_execution.md`).

It sits in AI & LLM Engineering, covering Model hubs and datasets, LLM inference and serving and Deep learning. It works with ONNX and PyTorch. The repository describes itself as: QAI AppBuilder is designed to help developers easily execute models on WoS and Linux platforms. It encapsulates the Qualcomm® AI Runtime SDK APIs into a set of simplified… The licence is BSD-3-Clause.

When your agent uses it

  • Working with custom ONNX/PyTorch models — export to ONNX
  • Convert to QNN/SNPE DLC
  • FP16/FP32/INT8 quantization
  • Operator patching

Example prompts

  • “/model-builder”

Requirements

  • Python 3

Workflow steps

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

  1. Export to ONNX — python_x64_venv, model.eval(), FP32 only (never FP16), opset_version=18; disable training-only branches…
  2. Inspect ONNX I/O — qai_inspect_onnxio.py. ⚠️ Do NOT gate on --dry_run (false positives) — go straight to Step 4. -> core_workflow.md §…
  3. Operator patching — ONLY if actual conversion hits a hard op error. Patch in-memory, re-validate (checker -> real conversion -> cosine ≥…
  4. Convert float model — run_pipeline.py (Flow A, default, all hosts). run_pipeline_legacy.py / qai_convert_fp.py / qai_convert_int.py are…
  5. Quantization (optional) — run_pipeline.py --precision --calib_list . ⚠️ Real multi-class calibration data; ask user if none. ->…
  6. Context binary — run_pipeline.py emits .bin automatically. The .bin is a QNN context binary for the HTP backend; on ARM64 hosts it targets…
  7. Inference + validation — route by HOST_OS per ${APP_ROOT}/factory/chat_features/_shared/qnn-inference-routing.md (the routing doc): ARM64…
  8. Validation report (MANDATORY) — ONNX (CPU-only) vs QNN cosine (≥0.99 FP16/FP32, ≥0.95 INT); below threshold -> B6 (stop, don't auto-fix)…

What it can do on your machine

Read from SKILL.md and the folder at commit c62ccca. 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

    Ships 1 file in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • pip

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

  • Network

    No URLs in SKILL.md. Its commands use pip, which can reach the network depending on how they are called.

    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

Model Builder loads about 4.1k tokens when it runs, and up to ~56k if it reads all its reference files. Until then it costs about 120 tokens; SKILL.md has 1,760 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
~4.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~56k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from qualcomm/qai-appbuilder at commit c62ccca, republished under its BSD-3-Clause licence (© qualcomm). 1,760 words, ~4,143 tokens.

Download SKILL.mdSave it as .claude/skills/model-builder/SKILL.md (or your agent's skills folder). This skill also uses 49 other files; get the full folder from GitHub.
name
model-builder
description
QAI ModelBuilder. Tools and workflows for model conversion, inspection, operator patching, quantization, and inference validation of self-converted models on Qualcomm platform. Use this skill when working with custom ONNX/PyTorch models — export to ONNX, convert to QNN/SNPE DLC, FP16/FP32/INT8 quantization, operator patching, context binary generation, and inference validation of self-built models. NOT for AI Hub prebuilt packages — use model-hub skill instead.

Model Builder

How to use this SKILL (it is a thin dispatch layer):

  1. Pass the Boundary Decision gate below first — it decides whether this skill even applies.
  2. Use the Routing Table to load the ONE reference / sub-SKILL that matches your step or problem — do NOT read everything up front.
  3. Follow the Core Workflow spine; open references/core_workflow.md for per-step commands.
  4. The Blocking Conditions and Disciplines below are the only rules you must hold in mind the whole time.
  5. Trust the docs: never run commands to re-verify facts already in this file or ${APP_ROOT}\data\config\qairt_env.json (torch/Python versions, tool paths). Don't read script source unless a reference doc is missing the detail (then update that doc).
  6. x64 host + user wants to run inference locally on this machine? Read ${APP_ROOT}/factory/chat_features/_shared/x64-host-notes.md FIRST (before Step 7). If HOST_OS is ARM64, or if inference will go via ADB, skip that file entirely.

🚨 Boundary Decision — pass BEFORE activating (MANDATORY GATE)

Answer three questions; if any veto holds, stop and switch skills.

#QuestionYES ->NO ->
Q1Does the model already have a prebuilt package on AI Hub (Zipformer, MobileNet, YOLO, …)?❌ Stop -> model-hub skillQ2
Q2Is the file to download/use an AI Hub prebuilt artifact (QNN context binary .bin / .dlc)?❌ Stop -> model-hub skillQ3
Q3Does the user have a custom ONNX/PyTorch model to convert, or to re-quantize/recompile into a custom .bin?✅ Activate this skill❓ Intent unclear — confirm first

Switch to model-hub on any of: "download from AI Hub" / "model on AI Hub" / "prebuilt package" / "on-device pre-exported package"; a model name + "download" where it already exists on AI Hub; "QNN_CONTEXT_BINARY" / "QNN_DLC". An AI Hub prebuilt package (.bin/.dlc) is loaded directly by model-hub via qai_appbuilder/QNNContext; this skill only converts/compiles custom ONNX/PyTorch. ("run inference" alone does NOT pick this skill — only when the target is a self-converted model.)

Dispatching a sub-agent to another skill (e.g. model-hub) — MANDATORY: a sub-agent inherits NOTHING from this skill (blank context). Once a vacuum-written prompt sent one recursively scanning C:\/C:\WoS_AI for .bin -> 30-min hang. So: (1) **first read the target SKILL.md in full**, write the prompt from it; (2) the prompt's first instruction MUST be "read the target SKILL.md in full before acting"; (3) the prompt MUST NOT carry any path/script/toolchain from this skill (run_pipeline.py, qnn-onnx-converter, …) — useless for prebuilt packages and lures a wrong disk scan; (4) reuse the target's Sub-Agent Dispatch Template if it has one.

⚠️ First action after activating (before Step 1): ask the DLC portability question (cross-platform vs SoC-optimised DLC) unless the user's request already signals it. Full wording + CLI mapping + skip-signals -> references/operations_reference.md § DLC Portability Question.


🧭 Routing Table — load only the ONE that matches (MANDATORY)

This SKILL is the main pipeline + index. For any specific step, error, or topic, load the single matching doc below — do NOT read them all. Troubleshooting sub-SKILLs are the canonical authority for errors (more complete than any inline summary). base ships in the external edition; advanced is internal-only (silently skip if the file is absent).

By problem / error (troubleshooting sub-SKILLs — canonical):

Symptom / error codeLoadtier
unsupported operator / 0xc26 / Einsum / Mod / Floor / ScatterND / dry-run false positive${APP_ROOT}/factory/chat_features/model-builder/troubleshooting/operator-patching/SKILL.mdbase
Graph Compose failure / graph_names / Wrong number of Parameters 5 / loadRemoteSymbols 4000 / arch mismatch${APP_ROOT}/factory/chat_features/model-builder/troubleshooting/conversion-troubleshooting/SKILL.mdbase
QNNContext crash / stale artifact / multi-model same-process / Linux HTP transport mismatch / NCHW-NHWC wrong${APP_ROOT}/factory/chat_features/model-builder/troubleshooting/inference-troubleshooting/SKILL.mdbase
VCTargetsPath / CMake / import cv2·Pillow / qai_appbuilder import fails${APP_ROOT}/factory/chat_features/model-builder/troubleshooting/env-troubleshooting/SKILL.mdbase
0-byte generator / WinError 193 / need to modify an SDK file${APP_ROOT}/factory/chat_features/model-builder/troubleshooting/sdk-integrity-recovery/SKILL.mdbase
basicsr / functional_tensor / aux-branch ReshapeOp (ONNX export)${APP_ROOT}/factory/chat_features/model-builder/troubleshooting/export-troubleshooting/SKILL.mdbase

By topic (references):

TopicLoad
Core Workflow step details (commands + caveats)references/core_workflow.md
Operations detail (flow selection, DLC-portability Q, guardrails, working-dir, project config, script index, pack export)references/operations_reference.md
Environment setup (Windows)references/win_qairt_setup.md
Export + ONNX validationreferences/model_export_validation.md
Operator patching (full code library)references/operator_patching.md
QNN conversionreferences/qnn_conversion.md
SNPE conversionreferences/snpe_conversion.md
Quantization (+ tool-param map)references/model_quantization.md
Context binaryreferences/context_binary.md
Inference (NCHW/NHWC, API, templates)references/inference.md
QNN inference routing (per-platform defaults + override keywords)${APP_ROOT}/factory/chat_features/_shared/qnn-inference-routing.md
x64 host — local inference guide (opt-in; compatibility matrix, backend choice via question tool, B11, closing statement)${APP_ROOT}/factory/chat_features/_shared/x64-host-notes.md
Quantization sensitivity (pre-conversion risk pre-flight)references/quantization-sensitivity.md
Verification disciplinereferences/verification-discipline.md
Pack export & inference_manifest.jsonreferences/pack_export.md
ADB device deploymentreferences/adb_execution.md
Remote (SSH) executionreferences/remote_execution.md
Troubleshooting quick-index + Windows tipsreferences/troubleshooting.md

Core Workflow (8-step spine)

Per-step commands, caveats, and MANDATORY sub-requirements -> references/core_workflow.md — open it when you start executing. First (once, before Step 1): run Host OS Detection, write HOST_OS to plan.md (windows-arm64 / windows-x64 / linux-aarch64 / linux-x64; drives Step 3 backend + Step 7 path) -> core_workflow.md § Host OS Detection.

  1. Export to ONNX — python_x64_venv, model.eval(), FP32 only (never FP16), opset_version=18; disable training-only branches (aux_logits/dropout). -> core_workflow.md § Step 1 / model_export_validation.md.
  2. Inspect ONNX I/O — qai_inspect_onnxio.py. ⚠️ Do NOT gate on --dry_run (false positives) — go straight to Step 4. -> core_workflow.md § Step 2.
  3. Operator patching — ONLY if actual conversion hits a hard op error. Patch in-memory, re-validate (checker -> real conversion -> cosine ≥ 0.95). Canonical -> operator-patching sub-SKILL.
  4. Convert float model — run_pipeline.py (Flow A, default, all hosts). run_pipeline_legacy.py / qai_convert_fp.py / qai_convert_int.py are Flow C (DLL, windows-arm64 only; error out elsewhere). --precision fp16|fp32. Do NOT manually pass --htp_version — run_pipeline.py auto-detects on Linux via qnn-platform-validator; Windows defaults to v73. Only specify manually when auto-detection fails AND you know the target SoC (see core_workflow.md § Step 4 for the full SoC→HTP table). -> core_workflow.md § Step 4 / qnn_conversion.md.
  5. Quantization (optional) — run_pipeline.py --precision <p> --calib_list <list>. ⚠️ Real multi-class calibration data; ask user if none. -> core_workflow.md § Step 5 / model_quantization.md.
  6. Context binary — run_pipeline.py emits .bin automatically. The .bin is a QNN context binary for the HTP backend; on ARM64 hosts it targets real HTP. For loading a .bin on an x64 host, see x64-host-notes.md. Portable across HTP backend builds (routing doc §4); use .dlc for cross-backend / late backend choice. -> core_workflow.md § Step 6 / context_binary.md.
  7. Inference + validation — route by HOST_OS per ${APP_ROOT}/factory/chat_features/_shared/qnn-inference-routing.md (the routing doc): ARM64 hosts default to local HTP via Path A (qai_runner.py + qai_appbuilder, python_runtime_venv); x64 hosts default to ADB via Path B (adb_runner.py), with opt-in local execution when the user asks — see ${APP_ROOT}/factory/chat_features/_shared/x64-host-notes.md. User override keywords can flip the default (routing doc §3). NEVER call qnn-net-run directly. MANDATORY: save infer_{MODEL}.py + inference_manifest.json; any x64-local-execution run must emit the closing statement (see x64-host-notes.md §4) in the user's language. Per-step details -> core_workflow.md § Step 7 / inference.md.
  8. Validation report (MANDATORY) — ONNX (CPU-only) vs QNN cosine (≥0.99 FP16/FP32, ≥0.95 INT); below threshold -> B6 (stop, don't auto-fix). Write REPORT.md with the exact "Cosine Similarity Summary" plain-text format. Print ${WORKSPACE}\<model_name> in every turn's final summary. Update plan.md. -> core_workflow.md § Step 8.

Artifact checklist per Flow (A/B/C) -> references/expected_output_artifacts.md. Batch runs -> scripts/model_config.json.


Show full SKILL.md (701 more words)Show less

🛑 Blocking Conditions (always STOP & ask — both modes)

#Condition -> Action
B1Required config var empty/placeholder -> stop, list missing, ask user.
B2pip install needed -> stop, state package + reason, ask permission.
B3Patch iterations exhausted, NO progress (same ops, no patterns left) -> stop, list attempts + logs, escalate.
B4Operator patch would change model semantics -> stop, describe change, ask approval.
B5Target device unavailable for context-bin gen / on-device test (incl. remote unreachable) -> stop, ask how to proceed.
B6Accuracy < threshold after quant (cosine < 0.95) -> do NOT auto-fix. ① zero-cost diagnosis (is calibration one image / its augmentations? not diverse). ② STOP, report cosine + diagnosis, present options (each 1-line principle), ask which: (1) improve calib diversity; (2) --cle (+--per_channel); (3) --precision w8a16; (4) keep FP16 / try bf16; (5) accept if Top-K correct. Full flow -> model_quantization.md / quant-accuracy sub-SKILL.
B7No known replacement pattern for an unsupported operator -> stop, document, escalate.
B8Context binary gen fails on windows-arm64 / linux-aarch64 (real HTP hosts) -> stop (run_pipeline.py exits non-zero; NOT silently degraded). Return to operator patching; do NOT retry alternate generators (x86_64 build can't load an ARM64 DLL). 0-byte/corrupt generator = damaged SDK file -> qai_dev_gen_contextbin.py self-heals from the kept SDK zip; if none -> sdk-integrity-recovery sub-SKILL. Diagnose READ-ONLY. On x64 hosts see ${APP_ROOT}/factory/chat_features/_shared/x64-host-notes.md for loading the .bin locally and applicable blocking rules (B11).
B9Fixing would require modifying any file under $QAIRT_SDK_ROOT/$QNN_SDK_ROOT -> STOP IMMEDIATELY. Never edit/copy-over/rename/delete an SDK file (the C:\Qualcomm tree is tool-layer write-protected). Copy the file into the workspace and edit the copy, pointing tooling at it via documented overrides (--config_file, QNN_* env, workspace-local backend_extensions.json). Reading the SDK dir is fine. Genuinely missing/corrupt -> recover from kept zip (sdk-integrity-recovery); ask explicitly "edit <sdk_path>/<file>? [y/N]" and act only on a scoped yes naming the file.
B10A tool/script/package not described here must run and the venv is unclear -> stop, ask. Default to python_x64_venv for conversion tools (python310.dll); use python_runtime_venv (aka legacy python_arm64_venv, resolves to .venv_arm64_313 on WoS / .venv_x64_313 on x64) only for qai_appbuilder/QNNContext inference. Still unsure -> ask.
B11Any x64 local execution run (see ${APP_ROOT}/factory/chat_features/_shared/x64-host-notes.md) — user asks to report the numbers as real HTP performance → stop. Full definition, options to present, and closing statement → x64-host-notes.md §5 & §4.

Disciplines (hold these the whole run)

  • Execution mode (MODE in config, default batch): batch = run all phases autonomously, apply safe defaults, log decisions, only stop on a Blocking Condition — do NOT ask "proceed to next phase?" / "which precision?" (use config) / "run onnxsim?" (always). interactive = confirm at each phase. Never silently fall back to ONNX/CPU when QNN/HTP fails — diagnose & fix, or stop & report; substituting CPU for a failed HTP run is never an acceptable fix.
  • Inference results MUST come from actual execution. Never output Top-K/confidence/latency/cosine without first running the script via exec; every number traces to an exec log line. No guessing/estimating from model knowledge; no writing the report before running.
  • Operator patching is exhaustive — patch ALL unsupported ops until no pattern remains; never fall back to CPU; no fixed iteration cap; escalate only on B7/B4/B3. Rules + code -> references/operator_patching.md.
  • Working directory: all model artifacts under ${WORKSPACE}\<model_name>\ — NEVER under a QAIModelBuilder path, home/Downloads, or a CWD outside ${WORKSPACE}. Self-check every write. Bootstrap with qai_workspace_init.py. Tables + init diagnosis -> references/operations_reference.md § Working Directory.
  • Wrappers only: conversion via run_pipeline.py (run_pipeline_legacy.py = Flow C, windows-arm64 only); inference via qai_runner.py/qai_appbuilder (never qnn-net-run). Wrappers handle --preserve_io, layout, PYTHONPATH, arch dirs, and host_arch routing.
  • Trust known facts; never re-verify via shell (torch=2.x, Python x64=3.10/ARM64=3.13, tool paths — all in qairt_env.json). Timeouts: timeout=0 for all conversion commands. Benign HTP errors, os._exit crash, encoding, escalation, SDK read-only rules -> references/operations_reference.md § Guardrails.

⚠️ Python Environments (not interchangeable — gates B10)

Paths from ${APP_ROOT}\data\config\qairt_env.json (Setup.bat generates it). Never hardcode.

EnvKeyPythonRole
Conversionpython_x64_venvx86_64 3.10ONNX export, qairt-converter, qairt-quantizer, qnn-onnx-converter, qnn-model-lib-generator (all hosts).
Runtimepython_runtime_venv (fallback: python_arm64_venv)3.13 — aarch64 on WoS (.venv_arm64_313), x86_64 on x64 Windows (.venv_x64_313)qai_appbuilder, QNNContext, inference.
Ubuntupython3_venvx86_64 3.12All Ubuntu ops (no ARM64 venv on Ubuntu).

Default for tools not listed here: python_x64_venv (most QAIRT tools link python310.dll); switch to python_runtime_venv only when the tool imports qai_appbuilder/QNNContext or runs inference on a .bin/.dlc; unsure -> B10. On x64 hosts, if the user asks to run inference locally, use python_runtime_venv (resolves to .venv_x64_313) and see ${APP_ROOT}/factory/chat_features/_shared/x64-host-notes.md for backend selection. Setup / pip / --index-url / opencv / PYTHONPATH -> references/win_qairt_setup.md; env broken -> env-troubleshooting sub-SKILL.

© qualcomm, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 49 other files (scripts, references, assets) in tools/qaiappbuilder/factory/chat_features/model-builder of qualcomm/qai-appbuilder.

  • SKILL.md
  • LICENSE
  • README.md
  • assets/plan.md
  • references/adb_execution.md
  • references/context_binary.md
  • references/core_workflow.md
  • references/expected_output_artifacts.md
  • references/inference.md
  • references/model_export_validation.md
  • references/model_quantization.md
  • references/operations_reference.md
  • references/operator_patching.md
  • references/pack_export.md
  • references/qnn_conversion.md
  • references/quantization-sensitivity.md
  • references/remote_execution.md
  • references/snpe_conversion.md
  • references/troubleshooting.md
  • … and 31 more

Open the folder on GitHubat commit c62ccca

Compare with similar skills

Model Builder 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.

Model Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Model Builder this skillqualcomm/qai-appbuilder246—~4.1kAutomated safety check: PassBSD-3-Clause
Quark Torch Ptqamd/Quark181—~2.3kAutomated safety check: PassMIT
Tao Port Huggingface ModelNVIDIA/skills3.5k—~4.5kAutomated safety check: NotesApache-2.0
Quark Create Shapeshifter Passamd/Quark181—~2.9kAutomated safety check: PassMIT
Quark Onnx Shapeshifter Runamd/Quark181—~1.9kAutomated safety check: PassMIT
Quark Torch LLM Ptq Evalamd/Quark181—~2.6kAutomated safety check: PassMIT

Similar skills

  • Runs an end-to-end AMD Quark post-training quantization workflow for PyTorch / Hugging Face LLMs: inspect a Hub or local model, choose a quantization plan, create reproducible artifacts, request…

    181 GitHub stars~2.3k tokensUpdated 9 days ago
    AI & LLM EngineeringAuto-check passed
  • Official

    Integrate a HuggingFace Computer Vision model into the NVIDIA TAO Toolkit ecosystem (tao-core config, tao-pytorch trainer, tao-deploy TensorRT pipeline).

    3.5k GitHub stars~4.5k tokensUpdated today
    AI & LLM EngineeringAuto-check: notes
  • 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 9 days ago
    AI & LLM EngineeringAuto-check passed
  • Apply existing ShapeShifter graph passes to an .onnx model via the quark-cli shapeshifter CLI or a ShapeShifter YAML.

    181 GitHub stars~1.9k tokensUpdated 9 days ago
    AI & LLM EngineeringAuto-check passed
  • L3 recipe that runs a Torch LLM PTQ end-to-end for AMD Quark — for PyTorch / HuggingFace transformers models (safetensors input): quantize → validate → evaluate.

    181 GitHub stars~2.6k tokensUpdated 9 days ago
    AI & LLM EngineeringAuto-check passed
  • Quark Install

    amd/Quark

    Installs or verifies AMD Quark and ensures the selected Python environment has an accelerator-matched PyTorch.

    181 GitHub stars~3.5k tokensUpdated 9 days ago
    AI & LLM EngineeringAuto-check: notes

More from qualcomm/qai-appbuilder

All 13 skills in this repo
  • Model Hub

    qualcomm/qai-appbuilder

    Model Hub — download pre-exported models from Qualcomm AI Hub, run inference on-device, and export them to App Builder as ready-to-import Packs.

    246 GitHub stars~3.3k tokensUpdated today
    Auto-check passed
  • Aipc Toolkit

    qualcomm/qai-appbuilder

    AIPC, AI Porting Conversion. An agent skill from qualcomm/qai-appbuilder.

    246 GitHub stars~5.7k tokensUpdated today
    Auto-check: notes
  • App Builder

    qualcomm/qai-appbuilder

    App Builder — generate complete, runnable fullstack WebUI applications (FastAPI backend + pure HTML/CSS/JS frontend) around on-device AI Model Packs (OCR, TTS, ASR, Super-Resolution, etc.).

    246 GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Ppt Gen

    qualcomm/qai-appbuilder

    Generate fully editable, high-quality PPTX with python-pptx based on the user's topic, materials, or business goals; defaults to a general-purpose "dark gilded elegant" visual system, with adaptive…

    246 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Read Arxiv Paper

    qualcomm/qai-appbuilder

    Fetch and summarize academic papers from arxiv.org. An agent skill from qualcomm/qai-appbuilder.

    246 GitHub stars~308 tokensUpdated today
    Auto-check passed
  • Browser Automation

    qualcomm/qai-appbuilder

    A skill your agent uses when working with the browser tool — navigating or inspecting a page, clicking through a flow, filling and submitting a form, acting inside a logged-in session, or…

    246 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

Works with

Questions about Model Builder

What does Model Builder do?

QAI ModelBuilder. An agent skill from qualcomm/qai-appbuilder. Model Builder is an agent skill from qualcomm/qai-appbuilder. QAI ModelBuilder.

When should I use Model Builder?

Model Builder fits situations like: working with custom ONNX/PyTorch models — export to ONNX; convert to QNN/SNPE DLC; FP16/FP32/INT8 quantization; operator patching.

How do I install Model Builder in Claude Code?

Run `npx skills add qualcomm/qai-appbuilder --skill model-builder -a claude-code`. Or copy the skill folder (tools/qaiappbuilder/factory/chat_features/model-builder in qualcomm/qai-appbuilder) into .claude/skills/model-builder in your project. Claude Code loads it when a task matches its description.

How do I install Model Builder in Codex?

Run `npx skills add qualcomm/qai-appbuilder --skill model-builder -a codex`. Or copy the skill folder (tools/qaiappbuilder/factory/chat_features/model-builder in qualcomm/qai-appbuilder) into .agents/skills/model-builder in your project. Codex loads it when a task matches its description.

Can I use Model Builder 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 qualcomm/qai-appbuilder --skill model-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/model-builder, .gemini/skills/model-builder, .github/skills/model-builder and .opencode/skills/model-builder in your project.

What does Model Builder need to run?

Going by SKILL.md and its folder, Model Builder needs the command-line tools its instructions call (pip). Our summary lists: Python 3.

Does Model Builder access the network?

SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Model Builder 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Model Builder use?

Model Builder is published under the BSD-3-Clause licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Model Builder use?

About 4.1k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 52k tokens, read only when the agent opens those files.

What are the alternatives to Model Builder?

Skills that share tags, products or a category with Model Builder: Quark Torch Ptq (amd/Quark, 181 stars), Tao Port Huggingface Model (NVIDIA/skills, 3.5k stars), Quark Create Shapeshifter Pass (amd/Quark, 181 stars) and Quark Onnx Shapeshifter Run (amd/Quark, 181 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Model Builder?

qualcomm (a GitHub organization) maintains it in qualcomm/qai-appbuilder, which has 246 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

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