SKILLEMALL.ai
RU Sign in

BD encryption

|-

ClawHub Hermes author: 天轰穿 v1.0.0 MIT-0 2 files body ≈ 1 087 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

|-

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

ReferenceSecurityInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
57
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Map keys must be unique at line 25, column 1: category: "Automation" homepage: "" ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "summary"
  • note frontmatter-key unknown frontmatter key "summary_zh"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "pricing_tier"

Process rating: all ten parameters 46/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
  • 40Consistency. Frontmatter name (encryption) differs from the folder (encryption-paid)
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 13 steps
  • 100Execution cost. Instruction body is 1087 tokens
  • 100Running it twice. No mutating operations
  • low 14 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 2: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 13 items
  • +4Has examples (2 code blocks)
  • +1License stated

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

External checks

ClawHub: clean
This is a plainly described encryption helper that can change files and handle keys, but I found no hidden install code, persistence, or unrelated data access.
LLM: benign (medium) · VirusTotal: · 25 Aug 2026