SKILLEMALL.ai

AC system-health-check

System health validator — checks skill files, paths, permissions, binaries, backup freshness, and encryption. Produces pass/fail reports.

ClawHub Agent Skills author: Stems v0.1.0 3 files body ≈ 3 340 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

AnalyzerData and analyticsSecurityInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
74
Run on models
none yet
Process rating
C
62/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
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
  • 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: 3. 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")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 62/100

  • 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
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. No external tools needed
  • 100Steps. 5 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3340 tokens
  • 100Running it twice. No mutating operations
  • medium 5 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 137: enough signal without eating the budget
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 5 items
  • +3Output format is stated explicitly
  • +4Has examples (18 code blocks)

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

External checks

ClawHub: clean
This appears to be a diagnostic health-check skill whose filesystem reads and report/log writes fit its stated purpose, with a documentation caveat about the meaning of read-only.
LLM: benign (medium) · VirusTotal: benign · 28 May 2026