qualcomm
- 84 skills
- 0 followers
- 7 hours ago last updated
- ▌ Wos Woa Dashboard 2 · qualcommWindows on Arm Ecosystem Dashboard lookup — resolves each project dependency to a native-ARM64 / building / unsupported / unknown status per Arm AppReady, with citation links. Load during wos-analyzer Phase 2 (dependency audit) and when writing the Phase 8 Arm AppReady Status section. Also emits the ARM64-native vs emulated-x64 vs blocking three-way classification Arm's guidance recommends.
- ▌ Wos Neon Reference 2 · qualcommSSE/AVX → ARM NEON translation reference for Windows ARM64. Load when actively converting x86 SIMD intrinsics to NEON, choosing between baseline ARMv8.0 and optional ARMv8.2+ extensions, or checking the Windows ARM64 baseline ISA (AES/SHA1/SHA2/PMULL/CRC32) — no runtime feature check needed for baseline. Do NOT load for general questions about ARM64; load only when a specific intrinsic must be translated.
- ▌ Wos Build Error Recipes 2 · qualcommARM64 build/link error diagnosis and fix recipes for Windows (C-series compiler errors, LNK linker errors, D80xx conflicts, .sln/.vcxproj platform mis-configuration, dumpbin AA64 validation). Load when triaging an ARM64 build log line-by-line — do NOT load for general porting questions.
- ▌ Wos Toolchain Discovery 2 · qualcommCanonical PowerShell block that detects the Windows ARM64 build toolchain (host arch, Visual Studio path, ARM64-target cl.exe, MSBuild, dumpbin, vcvars script) and caches the result to .copilot/state/wos-toolchain.json for reuse across agents/phases. Load when any wos-* agent needs to build/validate ARM64 artifacts. Cached results survive across tool calls within a session; re-run only if the cache is missing or stale.
- ▌ Wos Forbidden Skip Reasons 2 · qualcommCanonical list of forbidden vs valid skip reasons for ARM64 SIMD porting, plus the PowerShell regex audit block used by wos-porter Phase 8 gate G7c and wos-optimizer Hard Constraints. Load when auditing an optimizer report, when the optimizer decides whether to skip a Tier-S file, or when writing the Limitations section of ARM64-PORT.md.
- ▌ Conventional Commit Rebaser 2 · qualcommRebase the current branch into clean conventional commits with proper author attribution. Use when the user wants to clean up a branch's commit history into well-organized conventional commits.
- ▌ Apply Qui Component Rules 2 · qualcomm bundleUse when writing or modifying QUI Angular template usage involving q-icon-button, q-inline-icon-button, q-header-bar-action-icon-button, q-avatar-image, labels for q-text-input/q-number-input/q-password-input/q-select/q-combobox/q-switch/q-checkbox/q-radio, interactive q-card, q-alert-banner actions, q-card actions, q-header-bar-action-bar, q-menu-trigger, or q-select-root checkbox indicators.
- ▌ Audit Qui Component Rules 2 · qualcomm bundleUse when reviewing or final-checking QUI Angular template usage involving q-icon-button, q-inline-icon-button, q-header-bar-action-icon-button, q-avatar-image, labels for q-text-input/q-number-input/q-password-input/q-select/q-combobox/q-switch/q-checkbox/q-radio, interactive q-card, q-alert-banner actions, q-card actions, q-header-bar-action-bar, q-menu-trigger, or q-select-root checkbox indicators.
- ▌ Add Model · qualcommAdd a new LLM model to the geniex runtime (creates spec header, example executable, CMakeLists)
- ▌ Write Xtensor · qualcommWrite C++ tensor logic using xtensor (NumPy-like API) for prototyping before QNN conversion
- ▌ Dev Qairt Runtime · qualcommReference for developing against the QAIRT/QNN runtime — graph execution, KV cache, tensor I/O, multi-shard wiring
- ▌ Convert Xtensor To Qnn · qualcommConvert xtensor prototype code to production QNN direct-buffer operations (zero-copy)
- ▌ Qimsdk Deploy · qualcomm bundleDeploy, build, run, and retrieve QIM SDK GStreamer C apps, gst-launch pipelines, QIM SDK C++ apps, and Python qimsdk apps on Qualcomm Linux devices. Five modes: Mode A (gst-launch — push and run directly, no build), Mode B (Ubuntu on-device build — QIMSDK source tree on device), Mode C (host build — gstreamer-app-builder C sample app, build on a Linux workstation (x86_64 or aarch64, arch auto-detected) using the host SDK, deploy to QLI device), Mode P (Python qimsdk app — push main.py and run, no build), Mode D (host build — cpp-app-builder C++ SDK app, standalone build against the Yocto SDK on a Linux workstation (x86_64 or aarch64, arch auto-detected), deploy to QLI device). Returns structured result for eval scoring.
- ▌ Qimsdk Cpp App Builder · qualcomm bundleQIM SDK C++ app development using only APIs and patterns defined by this skill bundle. Use when building or updating C++ applications with qti::Pipeline, qti::Element, qti::AppSrc/AppSink, qti::CamSrc, qti::MLVConverter, qti::MLPostprocess, qti::MLVideo*Bin, stream filters, YAML pipeline config mode, and QIM SDK logging.
- ▌ Qimsdk Python App Builder · qualcomm bundleQIM SDK Python application development using the qimsdk package. Use when building, editing, fixing, reviewing, or packaging Python apps that import qimsdk, construct Pipeline objects, use Element/AppSrc/AppSink/CamSrc/MLVConverter/MLPostprocess/MLVideo*Bin wrappers, generate multimedia or AI pipelines, wire custom Python preprocess or postprocess callbacks, or load qimsdk pipelines from YAML.
- ▌ Qimsdk Gstreamer App Builder · qualcomm bundleQIM SDK GStreamer development for gst-launch commands and GStreamer C sample apps on Qualcomm platforms. Use when building multimedia pipelines, AI pipelines, LiteRT/QNN/SNPE inference flows, daisy-chained models, batching, multi-stream composition, runtime source management, zero-copy cross-process pipelines, or robust bus/error handling.
- ▌
- ▌
- ▌ Add Quantization · qualcommAdd a quantized precision to a float recipe. Tries w8a8, falls back to w8a16, or gives up. Checks both tflite and qnn_dlc and disables the pairs that fail. Hard-requires a dataset + evaluator (authors them under supervision if missing). Best run after `validate-on-device`, but does not require it.
- ▌ Onboard Internal · qualcommOnboard a new model to Qualcomm AI Hub Models as an in-tree recipe (lives under src/qai_hub_models/models/<id>/, appears in the public catalog, has a scorecard entry). This is a thin delta on top of the base `onboard` skill — it inherits all authoring guidance from there and only adds the extra rules that apply to Qualcomm-catalog-bound recipes. Use when a Qualcomm engineer is adding a model to the shipping product, not when an external contributor is authoring a standalone folder.
- ▌
- ▌
- ▌ Validate On Device · qualcommCompile, profile, and check numerics for a float recipe on a Snapdragon device via AI Hub, across both tflite and qnn_dlc, running the matrix in parallel. Records every failed (precision, runtime) pair in the manifest's disabled_paths and reports it rather than debugging; troubleshoots with `.claude/docs/on-device-debugging.md` only when asked. Use after `onboard` produces a `validate`-green float recipe, and before `add-quantization`.
- ▌
- ▌ Wos Woa Dashboard · qualcommWindows on Arm Ecosystem Dashboard lookup — resolves each project dependency to a native-ARM64 / building / unsupported / unknown status per Arm AppReady, with citation links. Load during wos-analyzer Phase 2 (dependency audit) and when writing the Phase 8 Arm AppReady Status section. Also emits the ARM64-native vs emulated-x64 vs blocking three-way classification Arm's guidance recommends.
- ▌ Wos Neon Reference · qualcommSSE/AVX → ARM NEON translation reference for Windows ARM64. Load when actively converting x86 SIMD intrinsics to NEON, choosing between baseline ARMv8.0 and optional ARMv8.2+ extensions, or checking the Windows ARM64 baseline ISA (AES/SHA1/SHA2/PMULL/CRC32) — no runtime feature check needed for baseline. Do NOT load for general questions about ARM64; load only when a specific intrinsic must be translated.
- ▌ Wos Build Error Recipes · qualcommARM64 build/link error diagnosis and fix recipes for Windows (C-series compiler errors, LNK linker errors, D80xx conflicts, .sln/.vcxproj platform mis-configuration, dumpbin AA64 validation). Load when triaging an ARM64 build log line-by-line — do NOT load for general porting questions.
- ▌ Wos Toolchain Discovery · qualcommCanonical PowerShell block that detects the Windows ARM64 build toolchain (host arch, Visual Studio path, ARM64-target cl.exe, MSBuild, dumpbin, vcvars script) and caches the result to .copilot/state/wos-toolchain.json for reuse across agents/phases. Load when any wos-* agent needs to build/validate ARM64 artifacts. Cached results survive across tool calls within a session; re-run only if the cache is missing or stale.
- ▌ Wos Forbidden Skip Reasons · qualcommCanonical list of forbidden vs valid skip reasons for ARM64 SIMD porting, plus the PowerShell regex audit block used by wos-porter Phase 8 gate G7c and wos-optimizer Hard Constraints. Load when auditing an optimizer report, when the optimizer decides whether to skip a Tier-S file, or when writing the Limitations section of ARM64-PORT.md.
- ▌ Easywos Spec · qualcomm bundleBridges EasyWoS scan output with OpenSpec task generation for x64-to-ARM64 porting. MUST be invoked when OpenSpec generates tasks.md for changes involving porting_items. Parses EasyWoS YAML, runs hybrid spec matching (script initial screening + LLM semantic refinement), produces a matched YAML file with port_spec_ids and confidence scores, then guides tasks.md generation with dispatcher skill invocations. On invocation it FIRST runs a dependency preflight check and stops to ask the user if any dependent skill or data file is missing. Triggered via openspec/config.yaml rules.tasks.
- ▌ Etl Generator · qualcomm bundleRun a target program under a CPU-sampling profiler and produce an ETL trace file for later performance analysis. Keywords - collect ETL, profile a program, generate etl, capture CPU trace, record ETL.
- ▌ Perf Optimizer · qualcomm bundlePerformance bottleneck root-cause analysis tool. Parses SpeedScope JSON flame graphs, traces back the call chain to the true root-cause module (not just the most expensive leaf), then combines that with user-provided source paths to pinpoint hotspots, and lets the model produce targeted optimization suggestions based on context. Two input modes are supported: 1. **SpeedScope JSON** (proceeds straight to Phase 1) 2. **ETL file** (first follow the `perf-sampling-parser` skill instructions in the current agent context to analyze per-process CPU usage; the user picks the target process and exports a SpeedScope JSON, then proceeds to Phase 1) **The target process is NOT specified up front by the user**: when the input is an ETL, do NOT ask the user "which process do you want to analyze" before following the perf-sampling-parser workflow. The target process must be chosen by the user based on real data — the process tree and Top-N CPU breakdown produced by perf-sampling-parser. Triggers: - The user asks to analyze
- ▌ Sse Avx To Neon · qualcomm bundlePort x86 SSE/AVX intrinsics to ARM NEON, including CRC32 PCLMULQDQ → PMULL. Use when translating x86/x64 intrinsic code to NEON equivalents, adding ARM paths alongside existing x86 code, writing ARM NEON compute kernels from SSE/AVX specifications, or porting PCLMULQDQ-based CRC32 to PMULL. Triggers on: port SSE to NEON, add ARM NEON path, translate AVX to NEON, port CRC32 to ARM, intrinsic names like _mm_add_epi32 / _mm256_sub_ps / _mm_load_si128 / _mm_clmulepi64_si128, __m128i, __m256i, vmull_p64, ARM_PMULL, or any task involving mapping x86 vector intrinsics to ARM NEON.
- ▌ Asm X64 To Arm64 · qualcomm bundleConvert x64 assembly to AArch64 arm64 — both inline asm (asm volatile / __asm__) and standalone MASM .asm files (PROC/ENDP, equ, macro/endm) translated to GAS .S form. Use when porting x64-specific asm to arm64, adding arm64 support alongside an existing x64 path, translating an entire MASM hot-loop file, or auditing code for missing arm64 coverage.
- ▌ Dispatcher Skill · qualcomm bundleExpert skilltree layer-1 dispatcher. Receives porting task commands from tasks.md, parses arguments, loads porting_item data and spec descriptions, then routes to the appropriate leaf skill for actual migration execution. Invoked as: /dispatcher-skill <porting_item_id> --specs <ids> --source <path> or /dispatcher-skill <porting_item_id> --mode llm-freeform --source <path>. Does NOT contain migration logic itself — only routing and data assembly.
- ▌ Leaf Skill Creator · qualcomm bundleCreates new leaf skills for the expert skilltree, or adds missing spec.yaml files to existing leaf skills. Enforces the standard directory structure (SKILL.md + references/specs/*.md + *.yaml) and guides LLM to auto-generate structured spec.yaml files from natural-language spec.md content. Two modes: create (new leaf skill) and add-yaml (supplement existing).
- ▌ Arm64 Porting Report · qualcomm bundleGenerate an x64-to-ARM64 porting report in YAML format. Triggers when the user asks to generate/create/write an ARM64 porting report or migration analysis. Trigger phrases include: generate arm64 porting report, create porting report, write porting report, arm64 porting analysis, generate migration report, porting analysis for this code.
- ▌ Perf Sampling Parser · qualcomm bundleAnalyze per-process CPU usage from ETL log files and export SpeedScope flame graphs. Keywords - ETL, flame graph, CPU usage, speedscope.
- ▌ Arm64 Baseline Porting · qualcommFallback skill for porting x64 code to ARM64 when no specific spec matches. Provides mandatory architectural constraints that ALL ARM64 migrations must respect regardless of code pattern — covering both hand-written assembly and C/intrinsics output. Use when the dispatcher receives a porting_item with port_spec_ids: [] and mode=llm-freeform, OR when the LLM is producing freeform ARM64 output (C, intrinsics, or asm) without a more specific leaf skill. Ensures freeform porting still adheres to ARM64 correctness invariants: Windows ARM64 ABI, weak memory ordering, NEON 128-bit width limits, ARM64EC ABI shims, and intrinsic header / target-macro hygiene.
- ▌ Arm64 Port Orchestrator · qualcomm bundleTop-level loop-engineering orchestrator for x64-to-ARM64 porting of any open source project. Drives the whole pipeline end to end — scan, OpenSpec propose, easywos-spec task generation, OpenSpec apply (per-kernel port + verify/retry), wiring the ported kernels into the project's real build, building the WHOLE project for ARM64, running the project's OWN test/bench suites, an auto-fix loop over integrated build/test failures, and OpenSpec archive on green. Use when the user wants to "port <project> to ARM64 end to end", "automate the whole openspec-to-build-and-test loop", "loop engineering for arm64 porting", or hand a project directory and ask for a hands-off ARM64 port. It is the layer ABOVE easywos-spec: it invokes easywos-spec, dispatcher-skill, enable-windows-arm64 and the leaf skills rather than reimplementing them.
- ▌ Intrinsics X64 To Arm64 · qualcomm bundleExpert guidance for porting x86/x64 SSE/AVX vectorized C++ to ARM64 NEON, grounded in the Microsoft STL's two real backends (vector_algorithms.cpp). Use this skill when: translating __m128i/__m256i intrinsics to NEON (uint8x16_t/uint16x8_t/etc.), replacing _mm_*/_mm256_* with vld1q/vst1q/vceqq/vmaxvq/vminq, converting AVX2 tail-mask patterns (_Avx2_tail_mask_32) to ARM64 descending-granularity loops, replacing __isa_enabled with IsProcessorFeaturePresent, removing _Zeroupper_on_exit, handling 64-bit int min/max exclusion on ARM64, fixing _M_ARM64-only guards that miss _M_ARM64EC, auditing #ifdef guards for cross-arch correctness, or any x86-to-ARM64 SIMD migration in Windows C++ codebases. Also trigger for NEON equivalents of SSE/AVX ops, or why an x64 pattern cannot port to ARM64.
- ▌ Arm64 Inlineasm To Intrinsics · qualcomm bundleConvert ARM64 NEON inline assembly written in Clang/GCC-style `asm volatile(...)` blocks into maintainable C/C++ intrinsics, and must build a Verification project that compares the original asm against the translated intrinsics for semantic equivalence. Use when: (1) the user provides a source file path and line range and wants a specific ARM64 asm block rewritten as intrinsics; (2) the main source file needs an MSVC-compatible `#if defined(_MSC_VER) && (defined(_M_ARM64) || defined(_M_ARM64EC))` intrinsics branch while preserving the original asm in `#else`; (3) the task requires a mandatory GoogleTest-based verification workflow using the bundled template stored under `assets/Verification/`. Keywords: asm to intrinsics, ARM64 asm to intrinsics, NEON intrinsics, clang asm, msvc arm64, verification, gtest equivalence.
- ▌ Jit Arm64ec Virtualalloc Fix Skill · qualcomm bundleAnalyze ARM64EC JIT executable memory allocation bugs where JIT-generated ARM64 or ARM64EC code is allocated with VirtualAlloc/VirtualAllocEx and then misclassified or treated as X64 code. Use this skill whenever the user mentions ARM64EC, JIT code pages, VirtualAlloc vs VirtualAlloc2, MEM_EXTENDED_PARAMETER_EC_CODE, executable page allocation, or wants a bug report, patch explanation, review checklist, or fix guidance for this exact Windows issue.
- ▌ De Slop · qualcommClean AI-typical prose patterns from documentation files. Fixes em dash overuse, filler phrases, redundant openings, and bolded-label-with-em-dash lists. Use after writing or editing documentation.
- ▌ Sync Demos · qualcommSync a documentation site's demos with its corresponding debug apps. Detects new, removed, or renamed demos and updates debug app component pages, barrel exports, routes, and home pages accordingly.
- ▌ Fsd Enforcer · qualcommValidate project structure against Feature-Sliced Design rules. Checks layer import restrictions, slice isolation, and segment conventions. Use on a directory or set of changed files to catch FSD violations.
- ▌ Write Docs · qualcomm bundleWrite or revise QUI Docs documentation. Use whenever Codex is creating, editing, restructuring, or expanding MDX route files, navigation entries, documentation links, examples, screenshots, or docs assets in packages/docs/qui-docs or any QUI Docs-based documentation site; also use when a user asks to author documentation, add a docs page, rewrite docs copy, or prepare documentation for a PR.
- ▌ Review Docs · qualcomm bundleReview QUI Docs documentation for authoring compliance. Use whenever Codex is reviewing, proofreading, auditing, final-checking, or preparing to submit MDX route files, navigation entries, documentation links, examples, screenshots, or docs assets in packages/docs/qui-docs or any QUI Docs-based documentation site; also use as the final quality pass after writing or revising QUI Docs documentation.
- ▌ Conventional Commit Rebaser · qualcomm bundleRebase the current branch into clean conventional commits with proper author attribution. Use when the user wants to clean up a branch's commit history into well-organized conventional commits.
- ▌ Behavior Focused React Testing · qualcomm bundleUse when writing, reviewing, or refactoring React component tests that must validate public behavior instead of implementation details, especially tests in packages/frameworks/react.
- ▌ React Testing · qualcomm bundleUse when writing, reviewing, or refactoring React tests for application behavior, hooks, routes, state, or integration flows, especially when tests may assert implementation details instead of public outcomes.
- ▌ Angular Testing · qualcomm bundleUse when writing, reviewing, or refactoring Angular tests for application behavior, services, routes, state, forms, pipes, or integration flows, especially when tests may assert implementation details instead of public outcomes.
- ▌ Vitest Browser Testing · qualcomm bundleUse when writing, reviewing, or refactoring tests that run in Vitest Browser Mode, especially tests using page, userEvent, expect.element, browser locators, polling assertions, or real DOM interactions.
- ▌ React Component Testing · qualcomm bundleUse when writing, reviewing, or refactoring React component tests, especially tests for props, callbacks, controlled state, children, accessibility, form behavior, or multiple public component API variants.
- ▌ Angular Component Testing · qualcomm bundleUse when writing, reviewing, or refactoring Angular component or directive tests, especially tests for inputs, outputs, host behavior, template probes, forms, accessibility, or signal-backed behavior.
- ▌ Apply Qui Component Rules · qualcomm bundleUse when writing or modifying QUI React usage involving IconButton, InlineIconButton, HeaderBarActionIconButton, Avatar.Image, labels for TextInput/NumberInput/PasswordInput/Select/Combobox/Switch/Checkbox/Radio, interactive Card.Root, AlertBanner actions, Card.Root actions, HeaderBar.ActionBar, Menu.Trigger, or Select.Root checkbox indicators.
- ▌ Audit Qui Component Rules · qualcomm bundleUse when reviewing or final-checking QUI React usage involving IconButton, InlineIconButton, HeaderBarActionIconButton, Avatar.Image, labels for TextInput/NumberInput/PasswordInput/Select/Combobox/Switch/Checkbox/Radio, interactive Card.Root, AlertBanner actions, Card.Root actions, HeaderBar.ActionBar, Menu.Trigger, or Select.Root checkbox indicators.
- ▌ Aipc Toolkit · qualcomm bundleAIPC, AI Porting Conversion. Tools and workflows for QAIRT/AIPC project setup, model conversion, inspection, operator patching, quantization, context-binary generation, and inference on Qualcomm platforms. Use this skill when creating or initializing an AIPC project, exporting AI models to ONNX, converting ONNX models to QNN or SNPE/DLC, converting models to FP16/FP32, patching unsupported operators, generating context binaries, or implementing inference for QNN/SNPE DLC.
- ▌ Weather · qualcomm bundleQuery weather forecasts for any city. Uses wttr.in service, no API key required.
- ▌ Email 163 Com · qualcomm bundle163 email tool for sending, reading, searching, and replying to emails via 163.com (NetEase Mail).
- ▌ Read Arxiv Paper · qualcomm bundleFetch and summarize academic papers from arxiv.org. Use for arxiv.org paper URLs (e.g. arxiv.org/abs/...). Triggers include 'read/summarize this arxiv paper', 'read paper', 'summarize paper'. Note — arxiv URLs must use this skill, NOT summarizenews.
- ▌ Browser Automation · qualcommUse 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 screenshotting a rendered page — and especially when a page will not cooperate — a selector matches nothing, content is missing because it renders with JavaScript, an interaction has no effect, or a browser must be attached to instead of launched.
- ▌ Qai Appbuilder Docs · qualcomm bundleQAI AppBuilder technical documentation retrieval. Find guides on installation, Python/C++ APIs, and model deployment examples. QAI AppBuilder is a rapid AI application development framework designed to simplify the deployment of QNN models on NPU (HTP) across Qualcomm(高通) Windows on Snapdragon, Android, and Linux platforms. This tool is highly suitable for deploying classic models (all types of models except large language models can be deployed via QAI AppBuilder), such as real_esrgan_x4plus, inception_v3, beit, easy_ocr, and whisper_base_en. This tool is only applicable for loading QNN (*.bin) format models and performing inference, and is not suitable for converting model formats.
- ▌ Computer Automation · qualcommUse when working with the `computer` tool — driving the Windows desktop, clicking or dragging anything on screen, opening or focusing an app, or locating a UI element — and especially when a computer action did not do what was expected — a click or drag missed a target that looked right, a drag turned into a selection box, typing went to the wrong place, a shortcut had no effect, or the target cannot be pinpointed from the screenshot.
- ▌ Genie API Service Docs · qualcomm bundleGenieAPIService technical documentation retrieval. Find guides on platform deployment, model configuration, and API usage. GenieAPIService is an OpenAI-compatible API service that enables running large language models(include LLM & VLM model) locally on Qualcomm(高通) Windows on Snapdragon, Android, and Linux platforms. It leverages the device local NPU(HTP) or CPU for efficient inference.
- ▌ Ppt Gen · qualcomm bundleGenerate 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 layout capabilities for cover, table of contents, section/transition, viewpoint statement, image-text mixed layout, multi-card, columns, data, workflow, timeline, comparison, case study, quote, summary, and ending pages.
- ▌ Model Hub · qualcomm bundleModel Hub — download pre-exported models from Qualcomm AI Hub, run inference on-device, and export them to App Builder as ready-to-import Packs. Use this skill when the user wants to use an AI Hub prebuilt package (`.bin` / `.dlc` / ONNX) without doing custom conversion. NOT for self-converted models — use model-builder skill instead.
- ▌ App Builder · qualcomm bundleApp 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.). Use this skill when the user wants to build, generate, modify, or debug a standalone WebUI app around any installed Model Pack.
- ▌ Code Assist · qualcommA professional programming assistant supporting code writing, debugging, review, refactoring, and performance optimization, as well as open-source repository analysis.
- ▌ Model Builder · qualcomm bundleQAI 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.
- ▌
- ▌
- ▌
- ▌
- ▌ Real Esrgan X4plus · qualcomm bundleSKILL · Real-ESRGAN x4plus (Super-Resolution — App Builder Pack)
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Enable Windows Arm64 · qualcomm bundleGuide for enabling Windows ARM64 support in software projects. This skill will be used when users want to "enable ARM64", "add ARM64 support", "support Windows on ARM", or "make project ARM64 compatible". It detects build systems (cmake, visual_studio, autotools, bazel, make, ninja, qmake, scons) with priority ordering, checks if ARM64 is already supported, and modifies build files to add ARM64 configurations.
- ▌ Coverage · qualcommGenerate an HTML coverage report for all Go tests via bazel + genhtml, then open it in the browser.
- ▌ Reshape Pr Commits · qualcommReorganize the commits on the current PR branch into a clean, logically-grouped history with short one-line messages. Use when the user asks to tidy, squash, reshape, or clean up commits on the current branch or PR. ALSO proactively suggest this skill (ask, do not run unprompted) when the user signals a PR is finished or ready to review — e.g. "done with this PR", "ready for review", "let's open the PR", or just before calling `gh pr ready` / marking a draft ready — especially if `git log <base>..HEAD --oneline` shows many small WIP / fixup / "oops" commits.