SKILLEMALL.ai

DC image-scanner-pro

(no description)

Not recommendedlow grade D
ClawHub Agent Skills author: mrxolin v1.0.0 MIT-0 5 files body ≈ 130 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

ReferenceInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
57/100
safety, quality, tests
Safety 60%
95
Quality 40%
0
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
When it triggers w 12
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
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 Secrets in code secret-high-entropy-token package-lock.json:15
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "integrity": "sha512-MqO+MLfM…tPI+z2IE…2Cm/XHO+7gGR…y9Q==",
    quoted
  • low Secrets in code secret-high-entropy-token package-lock.json:51
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "integrity": "sha5…2BV+FY5ZFezP/ypmwayk68+NzzA…NFD/uUmBJuGoXw==",
    quoted
  • low Secrets in code secret-high-entropy-token package-lock.json:69
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…GLw+xYSd…cqA==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:201
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "integrity": "sha5…hnd+3NNM…g6W+rLUs…OoA==",
    quoted
  • low Secrets in code secret-high-entropy-token package-lock.json:216
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "integrity": "sha5…iLo+bD+r332…xd3+v9+KUnZ…Gsg==",
    quoted

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

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger

Process rating: all ten parameters 52/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 14 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 130 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 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 14 items

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

External checks

ClawHub: suspicious
The skill appears purpose-aligned for image analysis, but it needs review because it may scan local image folders and send images to Gemini without clear user-facing disclosure or consent controls.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026