onboard-arch-precheck

Detect host Ascend silicon and block mismatched onboard test invocations.

34|71|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/hw-native-sys/simpler --skill onboard-arch-precheck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard-arch-precheck
Source: https://github.com/hw-native-sys/simpler/tree/main/.claude/skills/onboard-arch-precheck
Command: npx skills add https://github.com/hw-native-sys/simpler --skill onboard-arch-precheck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects the host's actual Ascend silicon and refuses mismatched --platform onboard hardware test invocations BEFORE any device is locked. MUST invoke this skill before running pytest or task-submit commands that use --platform a2a3 or --platform a5 (onboard only — sim variants pass through). Use when invoking onboard hardware tests, repro'ing flaky-test reports, or wrapping pytest in task-submit. Skip for --platform a2a3sim / --platform a5sim (silicon-agnostic).

Core Features & Use Cases

  • Detects host Ascend silicon and maps to the repo arch using npu-smi and CANN platform_config Short_SoC_version.
  • Provides guardrails to prevent running onboard tests with mismatched hardware by exiting with actionable codes.
  • Skips checks automatically for sim variants to keep silicon-agnostic workflows fast.

Quick Start

Run the onboard-arch-precheck script before any onboard tests to confirm you are on the correct Ascend silicon.

Frequently Asked Questions about onboard-arch-precheck

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent running onboard tests with the wrong Ascend silicon?

To prevent running onboard tests with the wrong Ascend silicon, invoke an arch precheck script before pytest or task-submit to verify the --platform value matches the detected host architecture and block mismatched invocations.

How does Ascend silicon detection work for onboard hardware tests?

Ascend silicon detection works by reading npu-smi output and CANN platform_config Short_SoC_version to map the host hardware to a repo arch, caching the detection result for one hour to speed up subsequent onboard test checks.

Do I need to run silicon arch detection for a2a3sim or a5sim platform tests?

You do not need to run silicon arch detection for a2a3sim or a5sim platform tests because these sim variants are silicon-agnostic and automatically skip the precheck to keep workflows fast.

What happens when the --platform value does not match the detected Ascend arch?

When the --platform value does not match the detected Ascend arch, the precheck exits with a code of 2 to block the mismatched invocation, exiting with 1 if detection fails or 0 on a successful match.

When should I use an Ascend platform precheck before submitting tasks?

You should use an Ascend platform precheck before submitting tasks when invoking onboard hardware tests, reproducing flaky-test reports, or wrapping pytest in task-submit to ensure hardware matches before any device is locked.

Can I use npu-smi to verify CANN platform_config before running pytest?

Yes, you can verify CANN platform_config before running pytest by using a precheck that reads npu-smi output and Short_SoC_version to confirm your host Ascend silicon matches the specified --platform.