SKILLEMALL.ai
GitHub ↗ RU Sign in

BC llm_wallet

Manage crypto wallets and make x402 micropayments with USDC stablecoins on Polygon

modbender/skill-library-mcp Agent Skills author: modbender MIT 5 files body ≈ 1 602 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Manage crypto wallets and make x402 micropayments with USDC stablecoins on Polygon

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

GeneratorAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
88
Quality 40%
67
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Risky intent medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.

For the author

Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 8

✓ No critical or high findings

Medium and low: 8
  • medium Risky intent intent-wallet-secrets references/x402-protocol.md:33
    Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target
    - Signs with wallet private key
  • low Secrets in code secret-high-entropy-token README.md:182
    High-entropy token-like string (may be an id, hash or a credential)
    - **USDC**: 0x41…582
  • low Secrets in code secret-high-entropy-token README.md:189
    High-entropy token-like string (may be an id, hash or a credential)
    - **USDC**: 0x3c…359
  • low Secrets in code secret-high-entropy-token references/examples.md:10
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
    # Output: address: 0x74…4e4
    fixture
  • low Secrets in code secret-high-entropy-token references/wallet-setup.md:30
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "address": "0x74…4e4",
    quoted
  • low Secrets in code secret-high-entropy-token references/wallet-setup.md:183
    High-entropy token-like string (may be an id, hash or a credential)
    - USDC: 0x41…582
  • low Secrets in code secret-high-entropy-token references/wallet-setup.md:190
    High-entropy token-like string (may be an id, hash or a credential)
    - USDC: 0x3c…359
  • low Secrets in code secret-high-entropy-token references/x402-protocol.md:25
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "payTo": "0xCA…C00",
    quoted

Files scanned: 5. 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-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 54/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (llm_wallet) differs from the folder (llm-wallet)
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. No external tools needed
  • 100Steps. 29 steps
  • 100Execution cost. Instruction body is 1602 tokens
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 12 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)
  • +3Description length 82: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 32 headings
  • +3Step-by-step instructions: 29 items
  • +4Has examples (23 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)

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