BC domain-research
全功能域名研究工具。支持 RDAP (RFC 7480-7484) 结构化查询、WHOIS 传统查询、DNS 多类型记录解析 (A/AAAA/MX/NS/TXT/CNAME/SOA/CAA/SRV/PTR)、SSL/TLS 证书检查、域名可用性判断、多解析器 DNS 传播检测、子域名枚举、批量域名分析和交互式 HTML 可视化报告。触发词：查域名、域名查询、域名信息、WHOIS、RDAP、DNS查询、域名可用性、域名研究、SSL证书、子域名、domain lookup、domain research、check domain、dig DNS、whois lookup、domain availability、域名分析。
全功能域名研究工具。支持 RDAP (RFC 7480-7484) 结构化查询、WHOIS 传统查询、DNS 多类型记录解析 (A/AAAA/MX/NS/TXT/CNAME/SOA/CAA/SRV/PTR)、SSL/TLS 证书检查、域名可用性判断、多解析器 DNS 传播检测、子域名枚举、批量域名分析和交互式…
As a process C 53/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 skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 Dangerous commands
cmd-install-from-urlSKILL.md:32Installs a package from an untrusted URL / archivepip install -i https://pypi.tuna.tsinghua.edu.cn/simple/ dnspython python-whois requests cryptography
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")
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. No external tools needed
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 905 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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 312: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (13 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.