SKILLEMALL.ai

AC bank-statement-reconciler

Bank Statement Reconciler · 银行流水对账 — Upload bank statements (CSV/Excel/PDF) + orders/invoices → AI auto-matching → Reconciliation results (matched/difference/unclaimed/unmatched). Supports Chinese banks (BOC/ICBC/CCB), Alipay/WeChat Pay, PayPal/Stripe, Amazon/Shopify/Temu. Trigger: 银行流水, 对账, 流水匹配, 银行对账, bank reconciliation, statement matching, 订单对账, 发票对账.

ClawHub Agent Skills author: YKGlobal01 v1.0.0 MIT-0 11 files body ≈ 1 476 tokens Open the sourceclawhub.ai analyzed 4 d ago

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

ReferenceStripeShopifyFinancetype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
54/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
This is a copy of a skill from another catalog; the rating counts the canonical one: bank-statement-reconciler (ClawHub)

How to improve

    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: 11. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 54/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
    • 30Running it twice. 1 mutating operations with no state check
    • 40Consistency. Frontmatter name (bank-statement-reconciler) differs from the folder (bank-reconciler-pro)
    • 60Result and completion. Output format stated, no completion criterion
    • 100Tools and files. No external tools needed
    • 100Steps. 16 steps
    • 100Execution cost. Instruction body is 1476 tokens
    • 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)
    • -5TODO / placeholder text left in the skill
    • -41 reference files, but SKILL.md never points to them: the model will not open them
    • -37 of 7 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 357: enough signal without eating the budget
    • +4Structure: 20 headings
    • +3Step-by-step instructions: 16 items
    • +3Output format is stated explicitly
    • +4Has examples (5 code blocks)

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

    External checks

    ClawHub: suspicious
    This appears to be a real bank reconciliation skill, but it should be reviewed because it handles sensitive financial records and under-explains external sharing through Feishu.
    LLM: suspicious (high) · 28 May 2026