Test All Device
Run the full hardware (onboard) CI pipeline (examples + tests/st) with automatic platform and device detection. Use when the user asks to run all device/hardware tests or the full onboard CI locally.
Install
npx skills add hw-native-sys/simpler --skill test-all-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-all-device ~/.claude/skills/test-all-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 full hardware CI pipeline with automatic device detection
Detection / isolation procedures referenced below live in
[`../../lib/onboard-detection.md`](../../lib/onboard-detection.md).
1. If `command -v npu-smi` is not found, tell the user to use `/test-all-sim`
instead and stop.
2. **Precheck + detect platform** (§A) — gate on real silicon, then read the
detected arch into `PLATFORM`.
3. **Extract CI timeout** (§D, `st-onboard-<platform>` job):
`--pto-session-timeout`.
4. **Select a device range** (§C, range ≤4) — or, when wrapping in
`task-submit`, let it pick via `--device auto --device-num <range size>`.
5. **Read the marker selector out of the same job** you took the timeout from.
`st-onboard-a2a3` is three pytest passes, not one: the sweep deselects
`-m "not sdma and not sdma_fault"`, a later step runs
`-m "sdma and not sdma_fault"`, and a one-device step runs `-m sdma_fault`.
`st-onboard-a5` uses
`--exclude-level 4` and does not exclude `sdma`. Take the expression from
`ci.yml` rather than assuming, so this skill cannot drift from the job it
reproduces.
6. **Run through `task-submit`** (§E). On a5, the underlying command excludes
only level-4 tests, so SDMA remains in the sweep:
```bash
pytest examples tests/st --exclude-level 4 --platform a5 \
--device <range-or-$TASK_DEVICE> --pto-session-timeout <timeout> -v
```
On a platform whose job separates SDMA tests, the underlying sweep command
is:Details
- Skill name
test-all-device- Repository
- hw-native-sys/simpler
- Path
.claude/skills/test-all-device/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Test All Device skill do?
Run the full hardware (onboard) CI pipeline (examples + tests/st) with automatic platform and device detection. Use when the user asks to run all device/hardware tests or the full onboard CI locally.
How do I install the Test All Device skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add hw-native-sys/simpler --skill test-all-device. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test All 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 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.
Plan Audit
49lllyys/vreader
Audit an implementation against a plan (dev-docs/plans/*). Use when a user asks to check for gaps, logic errors, or missing tests relative to a plan or Work Items.
Test Example Device
49hw-native-sys/simpler
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.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.