probe-platforms
提供逐步带出策略，避免在平台适配上浪费大量时间。
在新操作系统上带出测试探针并排查跨平台失败的连锁故障。
在全新操作系统（Windows 或 Linux）上把测试探针或 harness 搭起来，或排查在某个平台上跑不通的问题。第一次在新平台运行或同一套在不同系统表现不一致时会用到。该流程汇总了常见连锁故障和绕坑经验（如 Windows 的 spawn/path/disk 问题、Linux 的 Landlock 与目录布局、远程 shell 的 quoting），能帮你少走很多弯路。
▸ 展开 SKILL.md 英文原文
Bring a test harness or probe up on a NEW operating system (Windows or Linux), or debug one that fails there. Invoke before the first run on a platform, and whenever a harness works on one OS but not another. Carries the bring-up ladder that avoids spending hours learning single booleans, the Windows spawn/path/disk faults that each present as something else entirely, the Linux Landlock and node-layout traps, and the remote-shell mechanics (PowerShell-over-SSH quoting, pkill matching your own command) that waste a loop each time they are rediscovered.
帮我安装这个 skill：https://raw.githubusercontent.com/nubjs/nub/main/.claude/skills/probe-platforms/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/nubjs/nub/main/.claude/skills/probe-platforms/SKILL.md"# Bringing a probe up on a new platform A harness that works on one OS fails on another for reasons that are almost never the thing the error names. Expect a CHAIN of faults, each hidden by the one in front of it. ## ⛔ Debug with the SMALLEST payload — the single most expensive mistake here Measured, bringing the build-jail probe up on Windows: **six sequential faults, found using `puppeteer` as the probe, at ~25 minutes per attempt.** Every one was answerable by a question as small as *"does the binary spawn?"* — seconds with `is-odd`. About two hours bought six booleans. **Climb this ladder in order. Do not skip to the end.** | # | Step | Proves | |---|---|---| | 1 | `<binary> --versi