BF kernel-vuln-discover
Linux 内核漏洞主动发现技能。当用户需要以下操作时使用此技能：(1) 对 Linux 内核特定子系统（io_uring、Netfilter、SMB、OverlayFS 等）进行漏洞挖掘；(2) 使用 fuzzer（syzkaller/trinity）对内核进行模糊测试；(3) 对内核代码进行静态审计和代码审查；(4) 基于 CVE 样本归纳发现模式并扫描同类漏洞；(5) 生成漏洞发现报告（PoC/根因分析）。不用于已知 CVE 查询（那是 kernel-cve-tracker 的职责）。
Linux 内核漏洞主动发现技能。当用户需要以下操作时使用此技能：(1) 对 Linux 内核特定子系统（iouring、Netfilter、SMB、OverlayFS 等）进行漏洞挖掘；(2) 使用 fuzzer（syzkaller/trinity）对内核进行模糊测试；(3)…
As a process F 35/100 · Will not run — References files that are not bundled: references/upstream-commits.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: 5. 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/upstream-commits.md
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: references/upstream-commits.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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1607 tokens
- 100Progress reporting. Reports progress
- low 10 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
- +1No license
- +2Single-language instructions
- +3Description length 248: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (19 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.