SKILLEMALL.ai

BD claw-ctct-security-patrol

OpenClaw 安全巡检工具,一键执行系统安全扫描并生成通俗易懂的报告。 使用场景:用户说"安全巡检"、"安全检查"、"安全审计"、"巡检"、"security audit"、"检查安全"、"系统安全"等。 触发条件:任何与 OpenClaw 安全检测、审计、巡检相关的请求。

ClawHub Agent Skills author: Williamwang-wh v1.0.0 MIT-0 5 files body ≈ 1 164 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
95
Quality 40%
79
Run on models
none yet
Process rating
D
43/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 5

✓ No critical or high findings

Medium and low: 5
  • low Dangerous commands cmd-cron-mention references/cron-setup.md:123
    Mentions editing / listing crontab (documentation of a security skill)
    crontab -e  # 删除相关行
    security skill

A further 4 matches are quotations in this security skill's documentation and are not counted as findings.

Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 43/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
  • 30Running it twice. 1 mutating operations with no state check
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 100Steps. 23 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1164 tokens
  • low The response is described with custom markup (3 tags): a typed call is more reliable

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 139: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 23 items
  • +4Has examples (5 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.

External checks

ClawHub: suspicious
This appears to be a real OpenClaw security audit skill, but its full and scheduled modes can repeatedly send host-identifying audit metadata to a CTCT remote service with incomplete disclosure.
LLM: suspicious (high) · VirusTotal: · 29 May 2026