arm-examples/llm-android-cross-build
skills/llm-android-cross-build/SKILL.md
Cross-compile for Android (x-android-aarch64 preset), optionally build tests/benchmarks, and outline adb push/run steps. Use when building for Android targets or diagnosing Android toolchain issues.
$ install --global
skillsauthnpx skillsauth add arm-examples/llm-runner llm-android-cross-buildInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 9:42 PM1.9s1 file scanned
SKILL.md
- name:
- llm-android-cross-build
- description:
- Cross-compile for Android (x-android-aarch64 preset), optionally build tests/benchmarks, and outline adb push/run steps. Use when building for Android targets or diagnosing Android toolchain issues.
Android cross-build
Use this to build for Android targets using the x-android-aarch64 preset.
Windows note: if python3 isn’t available, use python (or py -3) for any scripts below.
Offline/build caveat
During configure, CMake may use FetchContent to download dependencies from the network. If your network is blocked, configure can fail before tests run. To enable network access when the process runs in a sandbox, see skills/README.md. Otherwise, run the build on your local machine (with network access) and share the resulting build path with the tool (for example: build dir: /path/to/build), or point CMake at pre-downloaded dependencies in your environment.
Workflow
1) Configure
cmake --preset=x-android-aarch64 -B build
If configure fails because the NDK is missing, set it explicitly:
export NDK_PATH=/path/to/ndk
cmake --preset=x-android-aarch64 -B build
Note: configure triggers downloads via the standard downloader; set HF_TOKEN (or ~/.netrc) for gated models.
Optional flags:
cmake --preset=x-android-aarch64 -B build -DLLM_FRAMEWORK=llama.cpp -DBUILD_JNI_LIB=ON
cmake --preset=x-android-aarch64 -B build -DBUILD_BENCHMARK=ON
2) Build
cmake --build ./build --parallel
3) (Optional) Push and run on device
Use adb to copy binaries and models/configs to the device, then run them from a shell. Keep paths consistent with your config modelRoot.
4) Troubleshooting
- Ensure NDK is installed and discoverable (Android Studio or
NDK_HOME). - If JNI fails, verify
JAVA_HOMEand JDK version. - See
TROUBLESHOOTING.mdfor platform-specific notes.
Related Skills
arm-examples/llm-update-downloads
tools
VerifiedTrustedCommunity
Update scripts/py/requirements.json entries (URLs + sha256sum) for models/tools, validate hash changes, and keep downloads deterministic without committing artifacts. Use when adding or refreshing model/tool downloads.
4SKILL.mdUpdated Apr 4, 2026
arm-examples/llm-session-start
tools
VerifiedTrustedCommunity
Run fast “session start / doctor” checks for this repository (toolchain + wiring sanity, framework version report, optional upstream update check), optionally generate a debug bundle, and when needed bump pinned backend framework versions with build+ctest verification. Use at session start or when upgrading llama.cpp/onnxruntime-genai/mediapipe/mnn pins.
4SKILL.mdUpdated Apr 4, 2026
arm-examples/llm-jni-smoke
tools
VerifiedTrustedCommunity
Run a fast JNI-focused build/test smoke check (JNI on, minimal test run), and isolate JNI toolchain issues. Use when changing JNI/Java code or validating JNI setup.
4SKILL.mdUpdated Apr 4, 2026
arm-examples/llm-debug-test-failures
development
VerifiedTrustedCommunity
Debug failing LLM integration tests caused by model output drift, incorrect context/runtime parameters (contextSize, batchSize, threads), prompt/template mismatches, or backend/framework regressions. Use when tests fail and you need to see the model response, reproduce a single failing CTest, or trace issues into src/cpp/frameworks (llama.cpp, onnxruntime-genai, mediapipe, mnn).
4SKILL.mdUpdated Apr 4, 2026