SKILLEMALL.ai

BB wallet balance

Multi-chain wallet balances (EVM + BTC). Supported non-BTC addresses use the company MCP tool wallet-balance-query; EVM queries can fall back to public data when MCP fails. BTC uses public APIs only. Supports remembering addresses; when the user asks for a balance without a new address, query saved addresses. Replies must use the same language as the user message.

ClawHub Agent Skills author: bevanding v1.4.0 MIT-0 6 files body ≈ 2 356 tokens Open the sourceclawhub.ai analyzed 36 h ago

Multi-chain wallet balances (EVM + BTC).

As a process B 74/100 · Nearly there — weak spots: inputs and preconditions, consistency, running it twice

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
89
Quality 40%
80
Run on models
none yet
Process rating
B
74/100
Nearly there
Progress reporting w 2
0
Inputs and preconditions w 11
30
Running it twice w 4
30
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: 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 · 11

    ✓ No critical or high findings

    Medium and low: 11
    • low Secrets in code secret-high-entropy-token package-lock.json:41
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…jgR+Mkmf+D189…ihQ==",
      detector
    • low Secrets in code secret-high-entropy-token package-lock.json:103
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…9c8+Zse2…TOt+g==",
      detector
    • low Secrets in code secret-high-entropy-token package-lock.json:140
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…FFX/+gVeY…NlM++NqRc…bqg==",
      detector
    • low Secrets in code secret-high-entropy-token package-lock.json:262
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…hCu+wO3O…kUg==",
      detector
    • low Secrets in code secret-high-entropy-token package-lock.json:328
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…FrF+LTRo…W3g==",
      detector
    • low Exfiltration read-dotenv README.md:37
      Reads a .env file
      cp .env.example .env
    • low Secrets in code secret-high-entropy-token README.md:73
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "Check the balance of 0x81…1Dd"
      quoted
    • low Exfiltration read-dotenv README.md:117
      Reads a .env file
      cp .env.example .env
    • low Secrets in code secret-high-entropy-token README.md:153
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "Check the balance of 0x81…1Dd"
      quoted
    • low Secrets in code secret-high-entropy-token server.js:53
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      Ethereum: [{ symbol: "USDT", address: "0xdA…ec7" }],
      quoted
    • low Secrets in code secret-high-entropy-token server.js:54
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      BSC: [{ symbol: "USDT", address: "0x55…955" }],
      quoted

    Files scanned: 6. 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)

    Process rating: all ten parameters 74/100

    • 0Progress reporting. Says nothing while it works
    • 30Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 8 mutating operations with no state check
    • 40Consistency. Frontmatter name (wallet balance) differs from the folder (wallet-balance)
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 49 steps
    • 100Failures and branches. 4 branches, has a failure section
    • 100Execution cost. Instruction body is 2356 tokens

    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)
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +3Description length 366: enough signal without eating the budget
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 49 items
    • +3Output format is stated explicitly
    • +4Has examples (4 code blocks)

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

    External checks

    ClawHub: suspicious
    The skill does what it claims, but its local gateway can persist, list, modify, and query saved wallet addresses without built-in authentication or per-user isolation.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026