SKILLEMALL.ai
GitHub ↗ RU Sign in

BC Receipt & Expense Auditor

Extract, categorize, and audit receipts and bills to generate expense reports and spot discrepancies.

ClawHub Hermes author: haidong v1.0.0 MIT-0 12 files · 1 script body ≈ 3 584 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

Extract, categorize, and audit receipts and bills to generate expense reports and spot discrepancies.

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

AnalyzerFinancetype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
79/100
safety, quality, tests
Safety 60%
100
Quality 40%
48
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
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.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 12. 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-long-hermes description is 101 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • 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 "name_zh"
  • note frontmatter-key unknown frontmatter key "search_keywords"
  • note frontmatter-key unknown frontmatter key "first_success_path"

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 40Consistency. Frontmatter name (Receipt & Expense Auditor) differs from the folder (receipt-auditor)
  • 50Failures and branches. 0 branches, has a failure section
  • 85Steps. 45 steps, 1 vague phrases
  • 100Tools and files. No external tools needed
  • 100Execution cost. Instruction body is 3584 tokens
  • 100Progress reporting. Reports progress

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 101: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • -32 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 28 headings
  • +3Step-by-step instructions: 45 items
  • +4Has examples (19 code blocks)

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

External checks

ClawHub: suspicious
The skill does what it claims, but its CLI silently saves users' receipt and bill contents locally despite claiming no data storage.
LLM: suspicious (high) · VirusTotal: · 17 Jun 2026