Aomi Transact turns plain-English crypto and DeFi prompts into fork-simulated, wallet-signed on-chain transactions from the terminal.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install aomi-transact
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install aomi-transact using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is Aomi Transact?
Aomi Transact is an Openclaw Skills skill for building natural-language crypto agents, web3 assistants, and trading bots with the aomi TypeScript CLI. It translates prompts into actionable on-chain intents, stages them as wallet requests, and requires explicit user signing before broadcast.
It is optimized for non-custodial execution across Ethereum, Base, Arbitrum, Optimism, Polygon, Linea, Sepolia, Monad, Monad Testnet, and local Anvil. With account abstraction first support via EIP-7702 and EIP-4337, plus EOA fallback, it is well suited for safe DeFi automation, CEX-connected workflows, and repetitive trading operations.
Aomi Transact Use Cases
- The user wants a terminal-based crypto assistant that can answer balances, quotes, prices, routes, and transaction status.
- The user needs to swap, lend, bridge, stake, trade perps, or place prediction market bets with a wallet signature.
- The user wants a bot or agent that stages transactions, simulates them on a fork, and only signs approved steps.
- The user wants to interact with protocols such as Uniswap, Aave, Lido, GMX, Hyperliquid, Polymarket, Binance, or OKX.
- The user needs to inspect or switch chains, apps, models, threads, wallet modes, or account-abstraction settings.
- The user wants authenticated CLI account and wallet management via login, account, wallet ls, and secret commands.
How Aomi Transact Works
- Install or detect the
@aomi-labs/clientCLI and confirmaomi --versionworks. - Start a new session with
aomi chatoraomi --promptand provide the task, chain, app, wallet, or AA preferences. - The CLI interprets the prompt, resolves app/model/chain context, and either returns read-only data or creates one or more queued transaction intents.
- Review the queue with
aomi tx list, then simulate multi-step batches withaomi tx simulateto inspect success/failure, revert reasons, gas usage, and stateful ordering. - Sign only the transactions that pass simulation with
aomi tx sign; the CLI applies account abstraction first, then falls back to EOA semantics when appropriate. - Verify results with
aomi thread status,aomi thread log, oraomi thread events, and continue, resume, or close the thread as needed.
Aomi Transact Setup
This Openclaw Skills workflow assumes Node.js 18+ and access to the aomi CLI.
- Install the client globally or run it on demand.
npm install -g @aomi-labs/client@latest
aomi --version
# or
npx @aomi-labs/client@latest --version
- Set up a signing identity only when you are ready to transact. Use a dev key for local testing, or supply your own EVM or Solana key material explicitly.
aomi wallet dev-key
aomi wallet ls
# or, when you already have your own secret material:
export PRIVATE_KEY=0xYourPrivateKey
export SOLANA_PRIVATE_KEY=YourSolanaKeypairOrBase58
- Configure optional account-bound or backend settings as needed.
export AOMI_ACCOUNT_BEARER=your-account-token
# Use the production backend by default.
aomi config current
# Target staging only when you explicitly need it:
npx @aomi-labs/client@latest --backend-url https://api-staging.aomi.dev --version
- Run a first non-custodial transaction flow and review the queue before signing.
aomi chat "swap 1 ETH for USDC" --new-session --public-key 0xYourAddress --chain 1
aomi tx list
aomi tx simulate tx-1
aomi tx sign tx-1
- For protocol-specific flows, set the app or chain context before prompting.
aomi chat "stake 0.5 ETH on Lido" --app lido --chain 1 --new-session
Aomi Transact Data Schema & Taxonomy
Aomi Transact stores operational state inside ~/.aomi/ and does not require project-local schema files. The CLI persists user settings, thread state, wallet configuration, queue metadata, and secret records in that home-directory scope.
| Data layer | What is stored or generated | Key metadata | Primary commands |
|---|---|---|---|
| Configuration | Backend URL, chain, model, app, wallet mode, and execution preferences | current backend, selected chain, selected model, active app | aomi config current, `aomi chain list |
| Threads and sessions | Long-running chat context, logs, events, and resume state | thread ID, session state, event history, status | aomi chat, `aomi thread list |
| Transaction queue | Pending wallet requests and batch execution state | tx-N, batch_status, stateful, gas usage, revert reason, simulation outcome |
`aomi tx list |
| Account and wallet state | Logged-in account, linked wallets, signing mode, and identity selectors | account ID, public key, EOA/AA mode | `aomi login |
| Secrets and automation | Named secrets and scheduled jobs | secret name, cron job ID, schedule state | `aomi secret list |
Metadata taxonomy used in output and queue inspection:
tx-N: sequential transaction identifier assigned by the queue.batch_status: transaction batch state such as passed, pending, or failed.stateful: indicates whether execution order matters for the batch.chain: the active EVM network or test chain context.appandmodel: the selected protocol app and reasoning context.thread: the conversation context that links prompts, queue items, and logs.
Aomi Transact Advanced Features
- Non-custodial execution with explicit user signing and no blind broadcast.
- Fork-simulated multi-step transaction batches before signing, reducing execution risk.
- Account-abstraction first support with EIP-7702 and EIP-4337, plus EOA fallback.
- Drain-vector protection that blocks risky calldata targets during simulation when recipient-like fields do not match the expected sender.
- Support for 40+ protocols and apps, including Uniswap, Aave, Lido, GMX, Hyperliquid, Polymarket, Binance, and OKX.
- Thread-based workflows with queue inspection, status checks, logs, events, resume, and close operations.
- Backend switching and authenticated account-bound requests for production or staging workflows.
- Secret management and cron automation for repeatable agent execution inside
~/.aomi/. - Compatible with Claude Code, Cursor, Codex CLI, Gemini, and any runtime that supports the Anthropic skill spec.
SKILL.md
Loading
Related Openclaw Skills
CI Pipeline Debugger
CI Pipeline Debugger gives Openclaw Skills users a fast way to parse CI/CD logs, isolate failing steps, and turn pipeline errors into actionable fixes.
Merged Social and Poster Generator Skill
An automation skill that merges the visual design systems of guizang-social-card and magazine-poster into a unified programmatic design asset generator.
BankAI
BankAI is an AI-powered drafting assistant that converts brief natural language instructions into 59 types of standardized, hallucination-free banking document drafts.
微信管家 / WeChat Butler
WeChat Butler automates WeChat message sending and AI-powered auto-replies from a single, self-contained Openclaw Skills package.
Aomi Build
Aomi Build turns OpenAPI specs, SDK docs, and API references into production-ready Rust Aomi crates with typed, agent-callable tools for Openclaw Skills workflows.
ProofKit
ProofKit catches fake-success in AI agents by requiring live evidence before any task is marked done.
Featured*
