SKILLEMALL.ai

BB AB-Agents-Meter-Reader

📊 Read meter readings from photos. Electricity (day/night tariffs) and water meters. Saves history and generates messages for landlord.

ClawHub Agent Skills author: alexburrstudio v1.0.4 MIT-0 4 files · 1 script body ≈ 865 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process B 66/100 · Nearly there — weak spots: result and completion, when it triggers, progress reporting

GeneratorAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
98
Quality 40%
66
Run on models
none yet
Process rating
B
66/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
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-high-entropy-token SKILL.md:131
    High-entropy token-like string (may be an id, hash or a credential)
    🥝 TON: UQDH…yfr
  • low Secrets in code secret-high-entropy-token SKILL.md:132
    High-entropy token-like string (may be an id, hash or a credential)
    🥝 USDT TRC20: TE1m…HZc

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "acceptLicenseTerms"

Process rating: all ten parameters 66/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 23 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 865 tokens
  • 100Running it twice. No mutating operations
  • low 10 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)
  • +3Output format is not stated: the model decides each time
  • -218 emoji in the instructions: noise for the model
  • +3Description length 136: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 23 items
  • +4Has examples (5 code blocks)
  • +1License stated
  • +2Bilingual instructions (RU + EN)

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

External checks

ClawHub: suspicious
This meter-reading skill mostly does what it says, but it needs review because it sends household photos through an external tool and silently looks for credentials in a root OpenClaw file.
LLM: suspicious (high) · VirusTotal: · 29 May 2026