Test Example Device
Run the hardware (onboard) device test for a single example/scene-test directory ($ARGUMENTS). Use when the user asks to run or onboard one example on real hardware.
Install
npx skills add hw-native-sys/simpler --skill test-example-devicegit clone --depth 1 https://github.com/hw-native-sys/simpler.git /tmp/simpler
mkdir -p ~/.claude/skills
cp -r /tmp/simpler/.claude/skills/test-example-device ~/.claude/skills/test-example-devicePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Run the hardware device test for the example at $ARGUMENTS Detection / isolation procedures referenced below live in [`../../lib/onboard-detection.md`](../../lib/onboard-detection.md). 1. Locate the test file under `$ARGUMENTS/`: pick the single `test_*.py` that lives directly in that directory (not in a subdirectory). If none exists, tell the user the directory is not a scene test and stop. 2. If `command -v npu-smi` is not found, tell the user to use `/test-example-sim` instead and stop. 3. **Precheck + detect platform** (§A) — derive the arch from `$ARGUMENTS`, gate on real silicon, then read the detected arch into `PLATFORM`. 4. **Select a single idle device** (§C) — or let `task-submit` pick via `--device auto --device-num 1`. 5. **Run through `task-submit`** (§E, `--device-num 1`). The underlying command: ```bash python $ARGUMENTS/test_<name>.py -p <platform> -d $TASK_DEVICE ``` 6. Report pass/fail status with any error output.
Details
- Skill name
test-example-device- Repository
- hw-native-sys/simpler
- Path
.claude/skills/test-example-device/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Test Example Device skill do?
Run the hardware (onboard) device test for a single example/scene-test directory ($ARGUMENTS). Use when the user asks to run or onboard one example on real hardware.
How do I install the Test Example Device skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add hw-native-sys/simpler --skill test-example-device. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test Example Device popular?
It lives in hw-native-sys/simpler, which has 49 GitHub stars and 102 forks.
Related skills
Benchmark
49hw-native-sys/simpler
Benchmark runtime performance on hardware. If the current branch has commits ahead of upstream/main or uncommitted changes, compares against the fork point (merge-base). Otherwise benchmarks current state only. Use when the user asks to benchmark, measure performance, or compare latency.
Checkout PR
49hw-native-sys/simpler
Add a remote for a given PR's head repository and checkout a local pr-xxx-work branch. Use when the user wants to work on someone else's PR locally.
Clean Branches
49hw-native-sys/simpler
Remove stale local and remote git branches that have been merged into main. Detects regular merges and squash merges. Cleans up fork remote branches and prunes tracking refs. Use when the user asks to clean up branches, remove merged branches, or tidy up git.
Test Example Sim
49hw-native-sys/simpler
Run the simulation test for a single example/scene-test directory ($ARGUMENTS). Use when the user asks to run one example in simulation.
Test All Sim
49hw-native-sys/simpler
Run the full simulation CI pipeline (examples + tests/st) on a2a3sim/a5sim. Use when the user asks to run all sim tests or the full simulation CI locally.
Test Runtime Device
49hw-native-sys/simpler
Run hardware (onboard) device tests for one runtime ($ARGUMENTS — host_build_graph or tensormap_and_ringbuffer). Use when the user asks to onboard or test a single runtime on real hardware.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.