SKILLEMALL.ai

BC urlgo

连 CDP,开网页,截图,执行 JS 的浏览器控制 CLI

ClawHub Agent Skills author: fslong v6.5.3 MIT-0 2 files body ≈ 536 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
95
Quality 40%
57
Run on models
none yet
Process rating
C
51/100
Has gaps
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

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Write Bash

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

Against the Agent Skills spec

  • warning description-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 51/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
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 13 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 536 tokens
  • 100Running it twice. No mutating operations
  • low The response is described with custom markup (8 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)
  • +3Description length 29: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +1No license
  • +2Single-language instructions
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 13 items
  • +4Has examples (1 code blocks)

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

External checks

ClawHub: suspicious
This skill does what it says, but it gives an agent broad browser-control powers without enough safety boundaries for sensitive or authenticated sites.
LLM: suspicious (high) · VirusTotal: · 18 Aug 2026