BC bat-ps1-dev
Windows/Linux batch + PowerShell script dev experience vault — encoding pitfalls, cmd syntax traps, PS 5.1/7 compat, cross-platform gotchas, security tool best practices. 批处理/PowerShell 脚本开发经验库，编码陷阱、cmd 语法坑、PS兼容、跨平台坑、安全工具最佳实践。Keywords: bat, cmd, PowerShell, ps1, pwsh, BOM, CRLF, 闪退, 乱码, Windows scripting
Windows/Linux batch + PowerShell script dev experience vault — encoding pitfalls, cmd syntax traps, PS 5.1/7 compat, cross-platform gotchas, security tool…
As a process C 50/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:687High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)- **v1.35.0 (2026-08-21)**:**架构变更:自保护从 PowerShell 层下沉到 Go exe**(对应 SilverFox Detector **v2.15.0**):① **变更实质**: 原 §5/§7 记录的 `Self…ps1`(看门狗+进程 DACL) 与 `Silv…ity`(文件完整性) 全
detector
A further 2 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 30504 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "created" - note
frontmatter-keyunknown frontmatter key "updated"
Process rating: all ten parameters 50/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 10Execution cost. Instruction body is 30504 tokens: crowds the task out of the window
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 50 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 100Steps. 428 steps
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 41 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (10 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -221 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 305: enough signal without eating the budget
- +4Structure: 43 headings
- +3Step-by-step instructions: 428 items
- +4Has examples (17 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.