jeremylongshore/tons-of-skills-marketplace / plugins/crypto/aomi/skills/transact
aomi-transact
VerifiedBuild 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 aware with EIP-7702/4337 in the backend lane; local CLI signing is EOA. MUST NOT fabricate or echo credentials; values reach the CLI only when the user explicitly supplied them.
| File | Kind | Size |
|---|---|---|
| SECURITY.md | markdown | 14.9 KB |
| SKILL.md | skill md | 10.1 KB |
| agents/openai.yaml | config | 372 B |
| references/account-abstraction.md | markdown | 4.9 KB |
| references/apps.md | markdown | 15.9 KB |
| references/commands.md | markdown | 11.2 KB |
| references/drain-vectors.md | markdown | 4.7 KB |
| references/examples.md | markdown | 25.8 KB |
| references/gotchas.md | markdown | 6.7 KB |
| references/session.md | markdown | 6.4 KB |
| references/troubleshooting.md | markdown | 6.0 KB |
| references/workflows.md | markdown | 7.1 KB |
| templates/aomi-workflow.shexecutable | script | 8.1 KB |
references/gotchas.md
View on GitHub# Gotchas, Hard Rules, and Security Model
## What You Probably Got Wrong
LLM training data on aomi is stale. These are the most common mistakes the skill is shaped to prevent. Each correction is anchored to `@aomi-labs/client` v0.4.2 behavior.
- **"The CLI has `thread`, `cron`, `login`, or `wallet ls` commands"** → It does not, and never did. The npm client groups conversations under `aomi session ...`, account auth under `aomi account ...`, and local keys under `aomi wallet set|current|whoami`. There is no cron surface and no `aomi login`. Those forms belong to the Rust `aomi-cli` in `product-mono`, which is a separate dev/test CLI. Never emit them for the npm CLI.
- **"Aomi is a wallet"** → Aomi is an agent + CLI. It composes calldata and queues a wallet request; the user signs. The CLI does not custody funds, never signs without an explicit `aomi tx sign`, and never broadcasts on its own initiative.
- **"`aomi chat` always queues a transaction"** → Often the first response is a quote, route, or clarifying question. The agent only stages calldata when it has enough context. Always run `aomi tx list` after chat to see what is actually pending — never assume.
- **"Approval and swap are one transaction"** → Most DeFi flows are two-step: `approve` then `supply`/`swap`/`deposit`. Aomi stages them as a batch and `aomi tx simulate tx-1 tx-2` runs them sequentially on a fork so the second step sees the first's state changes. Sign them as a batch, not individually.
- **"Use `--rpc-url` to switch chains"** → `--chain` controls the wallet/session context (which chain the agent thinks you are on); `--rpc-url` controls where `aomi tx sign` estimates and submits. They are independent. For a cross-chain flow, the queued tx has its own `chain` field — pass `--rpc-url` matching *that* chain when signing.
- **"`aomi tx sign` does AA for me"** → Not in v0.4.2. Local signing is EOA-only; AA execution moved to the backend lane. Passing `--aa`, `--aa-provider`, or `--aa-mode` makes `aomi tx sign` fail outright, and so does having `AOMI_AA_PROVIDER` / `AOMI_AA_MODE` exported with no flags at all. The signing EOA must hold native gas on the destination chain — there is no local sponsorship fallback. See [account-abstraction.md](account-abstraction.md).
- **"`--new-session` should always be passed"** → Pass it on the *first* command of a new task. Reusing it mid-task starts a fresh conversation and the agent loses context (e.g. the quote it just gave you). For follow-up confirmations like *"yes, proceed"*, omit `--new-session`.
- **"Failed simulation txs disappear"** → They do not. `aomi tx list` can show older `tx-N` entries from earlier failed attempts alongside the current passing batch. Check the `batch_status` line and only sign txs marked as passing.
- **"7702 and 4337 are interchangeable"** → They are not. 7702 is a native EIP-7702 type-4 transaction with EOA delegation; the EOA pays gas. 4337 is a bundler+paymaster UserOperation; the paymaster can sponsor. Both are backend-lane concerns in v0.4.2 — read `aomi chain list` for per-chain AA state rather than assuming a default.
- **"Local key setup uses `wallet dev-key`"** → It uses `aomi wallet set <evm-hex-key>` (or `--evm`). Solana local keys use `aomi wallet set --solana <base58-key>`, or `--solana-private-key` / `SOLANA_PRIVATE_KEY` for one invocation. Inspect with `aomi wallet current`; inspect the bound account with `aomi wallet whoami` or `aomi account links`.
- **"`aomi app list` and `aomi model list` are required preflights"** → These introspection routes are backend-dependent and may return 404 on the public backend. Do not block chat, tx list, simulation, or signing flows just because app/model listing is unavailable.
- **"Drain vectors are aomi-specific"** → They are protocol-specific calldata fields where a malicious prompt could redirect funds (`recipient` in Uniswap, `onBehalfOf` in Aave, `mintRecipient` in CCTP, `_to` in OP-stack bridges). The agent blocks these at simulation time when they do not equal `msg.sender`. The skill's job is to surface the block, not bypass it. Full table in [drain-vectors.md](drain-vectors.md).
## Hard Rules
- Never invent, guess, or derive a credential value. The skill only ever passes through a value the user has explicitly given for a specific action in this turn.
- Never echo a credential value back after it has been used. Confirm the action ("dev key set", "secret `<HANDLE_NAME>` added") without restating the value.
- Setup commands that take a credential (`aomi wallet set <signing-key>`, `aomi secret add NAME=<value>`, flags like `--private-key`) are only run when the user has explicitly asked for that specific setup in this turn and has supplied the value themselves. Do not run them on the skill's own initiative to "prepare" or "fix" something.
- Before running a credential-setup command the user asked for, briefly confirm what will be persisted and where (local CLI state vs. the aomi backend — see [workflows.md → Secret Ingestion](workflows.md#secret-ingestion) for the transmission note), so the user can abort.
- Only call `aomi tx sign` after `aomi tx list` shows a pending `tx-N` the user asked for.
- When starting a new assistant thread, default the first aomi command to `--new-session` unless the user wants to continue an existing session.
- The signing RPC must match the pending transaction's chain. `--chain` (session context) and `--rpc-url` (signing transport) are independent — keep them aligned.
- Do not pass `--aa`, `--aa-provider`, or `--aa-mode` to `aomi tx sign` — they select AA execution, which the local signing path rejects.
## Security Model
This skill is scoped to the `aomi` CLI. It does not install software, read files outside the aomi state directory, or execute code it generates.
- **Credentials are opaque pass-through.** The skill never fabricates, guesses, or derives a credential value. Values only reach the CLI when the user has handed them over for a specific command in this turn, and they are not echoed or retained.
- **No unsolicited setup.** The skill does not run credential-persisting setup (`aomi wallet set`, `aomi secret add NAME=<value>`) to "prepare" for a task. It runs those commands only when the user explicitly asked, with the value the user supplied.
- **No blind signing.** Multi-step flows (approve → swap, approve → deposit) go through `aomi tx simulate` on a forked chain before `aomi tx sign`. Single-step read operations do not require simulation.
- **User-directed batches only.** `aomi tx sign` can take multiple ids; that is for batches the user has reviewed, not for sweeping a queue.
- **Read-only by default.** Chat, simulation, session inspection, and app/model/chain introspection do not move funds. Signing is a separate, explicit step the user must ask for.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |