CD security-health-check
Check email breaches and password strength. Generate security score reports.
As a process D 38/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
GeneratorData and analyticsInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Risky intent
intent-offensive-securityENTERPRISE_PLAN.md:85Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### 2.5 勒索软件 Preparedness 检查（Ransomware Readiness Assessment）
-
low Risky intent
intent-offensive-securityENTERPRISE_PLAN.md:88Offensive-security / dual-use content (legitimate for authorised testing; review intended use)评估企业在遭受勒索软件攻击时的恢复能力。5 大检查维度：备份覆盖率（是否至少 3-2-1 备份：3份副本、2种介质、1份离线）、备份完整性（定期演练验证）、网络分段（关键资产是否与互联网隔离）、终端防护（EDR 安装率 + 病毒库更新率）、 Incident Response 计划（是否有成文的 IR 流程 + 联系人清单）。输出：Ransomware Readiness Score（RRS 0-
Files scanned: 7. 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: Implicit map keys need to be followed by map values at line 9, column 1: Check if your email was compromised in data breaches and evaluate password stre… ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 38/100
- 0Steps. Prose only: no discrete steps
- 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
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 37 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)
- +3Description length 76: 120–800 characters recommended
- +4Structure: 0 headings, hard to scan
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -15SKILL.md body under 300 characters: nearly empty
- -33 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
Quality base 70; lint remarks subtract, signals add up to 100. Result: 30.
External checks
ClawHub: suspicious
This security-check skill is not malware, but it needs Review because it handles passwords and email addresses while misstating privacy details and including under-scoped enterprise social-engineering plans.
LLM: suspicious (high) · VirusTotal: · 7 Jun 2026