BC skill-system-monitor
跨平台系统监控工具，支持 Linux 和 Windows，监控硬盘、内存、CPU 使用情况，记录历史数据，支持变化对比和预警。**适合定时任务**。触发场景：(1) 定时系统健康检查（推荐每6小时），(2) 用户询问系统状态、资源使用情况，(3) 资源异常预警，(4) 查看历史监控数据对比。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Dangerous commands
cmd-execpolicy-bypassscripts/monitor.sh:59Runs PowerShell with execution policy bypassedpowershell.exe -ExecutionPolicy Bypass -File "$SCRIPT_DIR/moni…ps1"
-
medium Dangerous commands
cmd-execpolicy-bypassSKILL.md:136Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy Bypass -File scripts\moni…ps1
Files scanned: 7. 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")
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 42 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1551 tokens
- 100Running it twice. No mutating operations
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
- -226 emoji in the instructions: noise for the model
- -31 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 146: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.