.claude/skills/windows-shellRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Windows 命令行工作规范:先选对 shell(默认 Git Bash),再避开编码与 MSYS2 参数改写两类陷阱。覆盖 GBK/UTF-8、BOM、MSYS2 路径转换、PowerShell/pwsh、WSL 判定、Python/Node.js、Git 配置与代码生成规则。适用于 Windows 10/11 + MSYS2/Git Bash 环境下的所有命令行操作。细节按需读 references/。
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/windows-shellRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/windows-shellRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/windows-shellSKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @chenmo0414/windows-shellclawhub inspect @chenmo0414/windows-shell --version 5.3.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:dfbbd72dda29235ea5f492d46dbb2b353ed463f3240fadcc7544b0b37fd4b8a4CHANGELOG.mdreferences/encoding.mdreferences/gitbash-pitfalls.mdreferences/msys2.mdreferences/shell-routing.mdreferences/wsl.mdskill-card.mdSKILL.md补两条,否掉一条。候选来自 agent 实测自报的「规范没写、只能靠自有知识现推」, 再用 TokenHub 多模型探针筛出其中模型真不会的(每格 5 次采样,共 240 次调用)。 **新增 1:`PIPESTATUS` 会被下一条命令重置,包括赋值语句本身。** cmd | tail -1; a=${PIPESTATUS[0]}; b=${PIPESTATUS[1]} # ✗ b 恒为 0 cmd | tail -1; st=("${PIPESTATUS[@]}") # ✓ 紧邻、一次取完 实测 `(exit 7) | tail -1`:紧邻读得 7,中间隔一条命令再读得 0,先赋值再读第二个也得 0。 原规范只写了「用 ${PIPESTATUS[0]}」,没说它会失效——三个 agent 都在这上面栽过。 TokenHub 裸问命中率 40%,加规则后 deepseek 两个模型由 4/5、2/5 拉满到 5/5。 **新增 2(辟谣条目):中文写在 `-Command '...'` 参数里是安全的,不需要 BOM。** powershell -NoProfile -Command '$s="中文测试"; Write-Output $s.Length' # → 4,正确 要 BOM 的只有**脚本文件**(见 5.2.0),命令行参数走的是另一条路径。这条是反向陷阱: 实测中有两个 agent 因为担心参数被 ANSI 吃掉,绕道去写带 BOM 的 .ps1,白花两条命令。 TokenHub 裸问只有 40% 答对——六成情况下模型会误以为会坏。 **否掉:编码判定方法(`od` 看字节区分 GBK/UTF-8)。** 四个 agent 点名「规范没写这个」,但 TokenHub 三模型裸问 **15/15 全对**,两轮复测一致。 它们不是不知道,是不确定该不该做这一步。写进去纯属浪费篇幅,故不收。 这条同时给出一个方法学结论:**agent 自报的 spec_gaps 不能直接采信**。四条候选里, 一条被证伪(中文传 -Command 根本不会坏,是 ag…
Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.
These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.
sha256:97f30bfa37bb928a53cd5174576eb5c1b78fb218d87f1215555836b0a156fd7bsha256:9a1896d76096cddba928278fbd543090620eb237ce5bb890b17213f87e035ee0