BC bom-vuln-intel-tool-pro
物料清单漏洞情报专业版,为企业安全团队提供全方位SBOM管理与依赖漏洞治理能力。核心能力:多生态SBOM生成、CycloneDX/SPDX标准输出、OSV+GHSA+NVD三库联查、批量扫描、持续监控与告警、SARIF报告。Use。Use when 需要系统监控、日志分析、运维告警、部署管理时使用。不适用于物理硬件维修。 功能涵盖: vuln, intel。
物料清单漏洞情报专业版,为企业安全团队提供全方位SBOM管理与依赖漏洞治理能力。核心能力:多生态SBOM生成、CycloneDX/SPDX标准输出、OSV+GHSA+NVD三库联查、批量扫描、持续监控与告警、SARIF报告。Use。Use when…
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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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 Exfiltration
exfil-webhook-urlSKILL.md:236Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)webhook: "https://hooks.slack.com/services/未指定"
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: All mapping items must start at the same column at line 9, column 1: description: "物料清单漏洞情报专业版,为企业安全团队提供全方位SBOM管理与依赖漏洞治理能力。核心能力:多生态SBOM生成、CycloneDX/… when 需要系统监控、日志分析、运维告警、部署管理时使用。不适用于物理硬件维修. ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 180 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools"
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. Tools declared in frontmatter
- 100Steps. 29 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3903 tokens
- 100Running it twice. No mutating operations
- 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
- +2Single-language instructions
- +3Description length 180: enough signal without eating the budget
- +4Structure: 39 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (11 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.