SKILLEMALL.ai

BD skill-security-guard

Skill 安全扫描器 - 检测第三方技能的恶意代码、信息泄露等安全风险,保护你的 AI 助手安全!

ClawHub Agent Skills author: sukimgit v1.0.2 MIT-0 17 files body ≈ 575 tokens Open the sourceclawhub.ai analyzed 4 d ago

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

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
98
Quality 40%
68
Run on models
none yet
Process rating
D
41/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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Secrets in code secret-password-literal checkers/checkers/sensitive_checker.py:276
    Hard-coded password / key literal (may be an example) (placeholder value)
    api_key = "sk-1…def"
    placeholder
  • low Secrets in code secret-password-literal checkers/sensitive_checker.py:205
    Hard-coded password / key literal (may be an example) (placeholder value)
    api_key = "sk-1…def"
    placeholder

Files scanned: 16. 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 41/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
  • 40Consistency. Frontmatter name (skill-security-guard) differs from the folder (skill-security-guard-publish)
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 36 steps
  • 100Execution cost. Instruction body is 575 tokens
  • 100Running it twice. No mutating operations
  • low 11 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 50: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -228 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 36 items
  • +4Has examples (6 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This is mainly a local skill-code scanner, but it also ships under-disclosed live network probing and firewall-inspection code.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026