BD 净盘师 DiskSage
智能净盘师，专治 C盘爆满 / 磁盘空间不足 / 系统盘变红。自动探测全盘，给出回收站真实账本（区分 $I 收据与 $R 实体，戳破"账面虚高"），安全清理系统 Temp、浏览器缓存、npm/pip/conda 包管理缓存、微信/企微/剪映等 IM 与工具缓存（只动可重建项，绝不碰用户文件），内置反省/进化/超越三基因与账实对账，极低误删风险。免费版全功能可用、零上传、账实相符；省心版支持自动值守与规则库持续演进。适用：磁盘清理、垃圾清理、系统优化、释放磁盘空间、回收站净化、C盘清理工具、清理C盘、电脑空间不够、免费磁盘清理、电脑提速。
智能净盘师，专治 C盘爆满 / 磁盘空间不足 / 系统盘变红。自动探测全盘，给出回收站真实账本（区分 $I 收据与 $R 实体，戳破"账面虚高"），安全清理系统 Temp、浏览器缓存、npm/pip/conda 包管理缓存、微信/企微/剪映等 IM…
As a process D 49/100 · Unfinished process — 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.
- 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 · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "agent_created" - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 49/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
- 40Consistency. Frontmatter name (净盘师 DiskSage) differs from the folder (disk-keeper-wangcun)
- 100Tools and files. No external tools needed
- 100Steps. 26 steps
- 100Execution cost. Instruction body is 962 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
- +2Single-language instructions
- +3Description length 271: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.