CC dns-lookup-tool-pro
(no description)
专业版不仅是DNS查询工具，更是企业DNS资产的监控与审计平台。从单次查询到批量巡检，从手动排查到自动告警，从文本输出到结构化数据，专业版覆盖DNS运维的完整生命周期.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
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
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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
-
high Exfiltration
exfil-webhook-urlSKILL.md:200Webhook / callback URL commonly used for exfiltration (verify the destination)url: https://hooks.slack.com/services/未指定
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: A block sequence may not be used as an implicit map key at line 9, column 1: description: "DNS查询专业版是面向运维团队与SRE的企业级DNS诊断与管理Skill，在免费版基础上扩展了批量查询、结构化输出、DNSSEC验… - 批量域名查询（单次100+域名），并行执行并汇总报告 ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 282 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 51/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 66 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2261 tokens
- 100Running it twice. No mutating operations
- low 21 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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -222 emoji in the instructions: noise for the model
- +2Single-language instructions
- +4Structure: 58 headings
- +3Step-by-step instructions: 66 items
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.