BF hekouwang-env-doctor-skill
会勇禾口王 · 开发环境体检器(第三把 doctor)。扫描 Mac/Linux 上被开发工具占掉的磁盘空间,把每个目录判定成「数据 / 缓存 / 残留」三类,重点识别**你已经换掉但从没卸干净的旧工具**(如还留着 nvm 却早就在用 fnm),逐条给出判定依据、官方清理命令与代价。配交互式清理选择器(空格勾选、数据类锁死勾不上、确认后才执行、支持 --dry-run),删什么由你逐项勾。触发:用户说「磁盘满了 / 硬盘不够了 / 清理缓存 / 电脑越用越满 / 开发环境体检 / 查查什么占空间 / env-doctor / 环境体检 / disk doctor / 我的 Mac 空间去哪了 / node_modules 太大 / 缓存清理 / 残留清理 / 换过 nvm 想清干净」。任何「查/清 本机磁盘被开发工具占用」的请求都应触发。
会勇禾口王 · 开发环境体检器(第三把 doctor)。扫描 Mac/Linux 上被开发工具占掉的磁盘空间,把每个目录判定成「数据 / 缓存 / 残留」三类,重点识别你已经换掉但从没卸干净的旧工具(如还留着 nvm 却早就在用…
As a process F 35/100 · Will not run — References files that are not bundled: scripts/clean.sh, scripts/scan.sh
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 asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read
Files scanned: 0. 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
missing-refreference to a missing file: scripts/clean.sh - warning
missing-refreference to a missing file: scripts/scan.sh - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: scripts/clean.sh, scripts/scan.sh
- 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
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 605 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 375: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (3 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.