SKILLEMALL.ai

AA aomi-transact

Build natural-language crypto agents, web3 assistants, and trading bots that read and write EVM chain state. Aomi turns prompts ("swap 1 ETH for USDC", "open a 3x GMX long", "bet $100 on Polymarket") into wallet-signed transactions on Ethereum, Base, Arbitrum, Optimism, Polygon, Linea — non-custodial, fork-simulated. Use when the user wants a crypto/DeFi agent, AI trading/wallet assistant, or on-chain execution against Uniswap, Aave, Lido, GMX, Hyperliquid, Polymarket, Binance, OKX, or 40+ other protocols. Trigger with prompts about swaps, lending, bridging, staking, perps, prediction markets, or any DeFi/CEX action needing a wallet signature. Account-abstraction first with EIP-7702/4337 and EOA fallback. MUST NOT fabricate or echo credentials; values reach the CLI only when the user explicitly supplied them.

ClawHub Agent Skills author: CeciliaZ030 v0.10.1 MIT-0 14 files · 1 script body ≈ 1 793 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process A 85/100 · Runs to the end — weak spots: running it twice

GeneratorAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
95
Quality 40%
91
Run on models
none yet
Process rating
A
85/100
Runs to the end
Running it twice w 4
30
Result and completion w 14
60
When it triggers w 12
70
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 · 5

    ✓ No critical or high findings

    Medium and low: 5
    • low Secrets in code secret-high-entropy-token references/examples.md:37
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
      That's enough. The agent picks `Swap…r02 0x68…c45`, fee tier 500, recipient = your wallet, and queues the approve in the same batch.
      fixturequoted
    • low Secrets in code secret-high-entropy-token references/examples.md:51
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
      to:    0xA0…B48
      fixture
    • low Secrets in code secret-high-entropy-token references/examples.md:55
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
      to:    0x68…c45
      fixture
    • low Secrets in code secret-high-entropy-token references/examples.md:80
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
      #   tx-1  to 0xA0…B48 (USDC)
      fixture
    • low Secrets in code secret-high-entropy-token references/examples.md:82
      High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
      #   tx-2  to 0x68…c45 (Uniswap Swap…r02)
      fixture

    Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "permissions"
    • note frontmatter-key unknown frontmatter key "risk_tier"
    • note frontmatter-key unknown frontmatter key "requires"

    Process rating: all ten parameters 85/100

    • 30Running it twice. 2 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 37 steps
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1793 tokens
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • 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

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Description length 820: 120–800 characters recommended
    • +2Single-language instructions
    • +5Description quotes 3 example trigger phrases
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 37 items
    • +3Output format is stated explicitly
    • +4Has examples (2 code blocks)
    • +4Reference files are cited in the instructions (9 of 9)
    • +1License stated

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

    External checks

    ClawHub: suspicious
    This crypto transaction skill is mostly disclosed and purpose-aligned, but its high-impact signing ability is paired with under-scoped network and command authority that needs review.
    LLM: suspicious (high) · VirusTotal: · 10 Jul 2026