SKILLEMALL.ai

AB xero-accounting

Manage invoices, contacts, bills, payments, and accounting records in Xero via the Xero API. Use this skill when users want to create invoices, manage contacts, track payments, or automate Xero accounting workflows.

ClawHub Agent Skills author: Jay v1.0.6 MIT-0 2 files body ≈ 3 681 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process B 65/100 · Nearly there — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureFinancetype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
B
65/100
Nearly there
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

    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: 2. 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 65/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
    • 100Tools and files. No external tools needed
    • 100Steps. 44 steps
    • 100Failures and branches. 5 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3681 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 13 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
    • -5TODO / placeholder text left in the skill
    • +1No license
    • +2Single-language instructions
    • +3Description length 215: enough signal without eating the budget
    • +4Structure: 38 headings
    • +3Step-by-step instructions: 44 items
    • +4Has examples (14 code blocks)

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

    External checks

    ClawHub: clean
    The available evidence shows a clean, coherent skill version with no artifact-backed signs of hidden or unsafe behavior.
    LLM: benign (medium) · VirusTotal: · 9 Jun 2026