Skip to content
Back to skills

Qualcomm

ASecurity

"Build, export, test, and debug ExecuTorch Qualcomm QNN backend

  • 247 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 8, 2026
toolspythongobashtestingdebuggingbackend

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 8, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill qualcomm --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Qualcomm?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Qualcomm
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-qualcomm/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-qualcomm)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: qualcomm
description: "Build, export, test, and debug ExecuTorch Qualcomm QNN backend
  workflows, including QNN SDK setup, compile specs, model enablement,
  Buck/CMake parity, and intermediate-output accuracy triage."
disable-model-invocation: true
metadata:
  disco-role: operating
license: NOASSERTION
---

# qualcomm

Use this sub-skill when the user mentions Qualcomm, QNN, AI Engine Direct, HTP, Hexagon, QNN SDK, Qualcomm Android SoCs, QNN delegate tests, QNN accuracy divergence, or QNN Buck/CMake parity.

## First Route

- Build or SDK setup: read [Qualcomm workflows](references/qualcomm-workflows.md#build-and-environment).
- Export/lowering/quantization: read [Qualcomm workflows](references/qualcomm-workflows.md#export-lowering-and-quantization).
- Device/x86 tests: read [Qualcomm workflows](references/qualcomm-workflows.md#testing).
- Buck-vs-CMake CI failures: read [Buck/CMake parity](references/buck-cmake-parity.md).
- Per-layer accuracy divergence or intermediate outputs: read [Troubleshooting](references/troubleshooting.md#intermediate-output-debugging).

## Hard Prerequisites

QNN workflows require SDK/toolchain state that a generic CPU environment cannot prove. Confirm `QNN_SDK_ROOT`, Android NDK path, target SoC model, device serial/host if running on device, and build directory before issuing run commands.

## Bundled Planner

Generate a safe command plan without touching SDKs or devices:

```bash
python scripts/plan_qnn_command.py --soc SM8750 --build-dir build-android --artifact-dir /tmp/qnn-artifacts --device SERIAL
python scripts/plan_qnn_command.py --soc SM8750 --x86 --compile-only
```

The planner prints command templates and required environment variables; it does not build, install, push to a device, or download SDKs.

## Cross-Links

- Use `../llm-workflows/SKILL.md` for Llama/LLM model-asset planning before QNN backend execution.
- Use `../profiling-debugging/SKILL.md` for generic ETDump/Inspector work; return here for QNN-specific intermediate-output/debugger workflows.
- Use `../setup-build/SKILL.md` for generic CMake/Python environment failures.

Files in this skill

  • SKILL.md2.1 KB
  • references/buck-cmake-parity.md1020 B
  • references/qualcomm-workflows.md1.9 KB
  • references/troubleshooting.md1.8 KB
  • scripts/plan_qnn_command.py1.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.