arm-examples/llm-jni-smoke
skills/llm-jni-smoke/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add arm-examples/llm-runner llm-jni-smokeInstall 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.8s1 file scanned
SKILL.md
- name:
- llm-jni-smoke
- description:
- 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.
JNI smoke check
Use this for fast JNI validation after Java/JNI changes.
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 with JNI enabled
cmake --preset=native -B build -DBUILD_JNI_LIB=ON
2) Build
cmake --build ./build --parallel
3) Run only the JNI test
ctest --test-dir ./build -R llm-jni-ctest -V --output-on-failure
Tip: list available tests with ctest --test-dir ./build -N if the regex doesn't match.
4) Troubleshooting
- Set
JAVA_HOMEifjni.his not found. - If JNI is not relevant, disable with
-DBUILD_JNI_LIB=OFF.
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/mnn/executorch pins.
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, mnn, executorch).
4SKILL.mdUpdated Apr 4, 2026
arm-examples/llm-config-schema-change
testing
VerifiedTrustedCommunity
Safely add or change model config schema keys (JSON) and update parsing, tests, and docs. Use when editing model_configuration_files schema or LlmConfig parsing without doing broader model onboarding.
4SKILL.mdUpdated Apr 4, 2026