BF dead-code-cleaner
基于 codebase-memory-mcp 知识图谱的多阶段死代码检测与安全清理。当用户要求清理无用代码、查找并删除死代码、消除未被引用的文件、进行项目代码清理、或运行基于知识图谱的死代码分析时使用。支持所有编程语言（JS/TS/Vue/React/Python/Java/Go/Rust/C/C++/PHP/C# 等有精确验证模式，其他语言使用通用层验证）。同时处理单仓库与 monorepo。
基于 codebase-memory-mcp 知识图谱的多阶段死代码检测与安全清理。当用户要求清理无用代码、查找并删除死代码、消除未被引用的文件、进行项目代码清理、或运行基于知识图谱的死代码分析时使用。支持所有编程语言（JS/TS/Vue/React/Python/Java/Go/Rust/C/C++/PHP/C…
As a process F 33/100 · Will not run — References files that are not bundled: references/output-template.md, references/verification-patterns.md, references/verification-patterns.md
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 · 0
✓ No critical or high findings
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: references/output-template.md - warning
missing-refreference to a missing file: references/verification-patterns.md - warning
missing-refreference to a missing file: references/verification-patterns.md
Process rating: all ten parameters 33/100
- 0Tools and files. 3 referenced file(s) missing: references/output-template.md, references/verification-patterns.md, references/verification-patterns.md
- 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
- 30Running it twice. 2 mutating operations with no state check
- 100Steps. 108 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3589 tokens
- low 16 top-level sections: this looks like several domains in one skill
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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 199: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 108 items
- +4Has examples (17 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.