SKILLEMALL.ai

AC xerolite

Integrate OpenClaw with Xerolite - IBKR. Use when: querying Xerolite API, placing orders, searching contracts.

modbender/skill-library-mcp Agent Skills author: modbender MIT 7 files · 2 scripts body ≈ 711 tokens Open the sourcegithub.com analyzed 2 d ago

Integrate OpenClaw with Xerolite - IBKR.

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

IntegrationAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
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: 7. 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

    • 0Result and completion. Does not say what the result is
    • 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
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 4 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 711 tokens
    • 100Running it twice. No mutating operations

    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 110: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • -2localhost URLs: will not work for another user
    • -32 of 3 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 4 items
    • +4Has examples (5 code blocks)
    • +4Reference files are cited in the instructions (1 of 2)

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