Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/crypto/aomi/skills/transact

aomi-transact

Verified

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 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.

FileKindSize
SECURITY.mdmarkdown14.9 KB
SKILL.mdskill md10.1 KB
agents/openai.yamlconfig372 B
references/account-abstraction.mdmarkdown4.9 KB
references/apps.mdmarkdown15.9 KB
references/commands.mdmarkdown11.2 KB
references/drain-vectors.mdmarkdown4.7 KB
references/examples.mdmarkdown25.8 KB
references/gotchas.mdmarkdown6.7 KB
references/session.mdmarkdown6.4 KB
references/troubleshooting.mdmarkdown6.0 KB
references/workflows.mdmarkdown7.1 KB
templates/aomi-workflow.shexecutablescript8.1 KB

references/troubleshooting.md

View on GitHub
# Troubleshooting

Read this when a command fails unexpectedly or behaves differently than the workflow predicts.

## Chat / Session

- If `aomi chat` returns `(no response)`, wait briefly and run `aomi session status`.
- If `aomi session status` shows the session is gone, the local pointer may be stale — retry with `--new-session`.

## Signing

- If `aomi tx sign` fails with `AA execution now runs in the backend lane (rolling out); use --eoa for local execution.`, an AA path was selected. Drop `--aa` / `--aa-provider` / `--aa-mode` — and if no flags were passed, check for `AOMI_AA_PROVIDER` or `AOMI_AA_MODE` in the environment and have the user unset them.
- If a transaction fails on-chain, check the RPC URL, balance, and chain.
- If the signer address differs from the stored session public key, the CLI updates the session to the signer address and continues — this is expected, not an error.
- `--public-key` must match the address derived from `--private-key`; a mismatch is a hard error, not a warning.

## RPC

- `401`, `429`, and generic parameter errors during `aomi tx sign` are usually RPC problems, not transaction-construction problems. Pass a reliable chain-matching public RPC via `--rpc-url`.
- If one or two public RPCs fail for the same chain, stop rotating through random endpoints and ask the user to supply a proper RPC URL for that chain themselves. Do not paste provider-keyed URLs into chat.
- The pending transaction already contains its target chain. If the default RPC is wrong, override with `--rpc-url` for the matching chain.

## Simulation

- If `aomi tx simulate` fails with a revert, read the revert reason. Common causes: expired quote or timestamp (re-chat to get a fresh quote), insufficient token balance, missing prior approval. Do not sign transactions that failed simulation without understanding why.
- If `aomi tx simulate` returns `stateful: false`, the backend could not fork the chain — simulation ran each tx independently via `eth_call`, so state-dependent flows (approve → swap) may show false negatives. Retry, or check that the backend's Anvil instance is running before signing.

## Cross-chain

- When the chat/session chain (`--chain`) differs from the chain the agent eventually queues a tx for, that's normal — the user may have asked for a cross-chain operation. Sign with `--rpc-url` matching the *queued tx*'s chain, not the session chain.

## Invocation

- If `aomi: command not found`, the user does not have the global install. Substitute `npx @aomi-labs/client@latest` for `aomi` in every command and retry.
- If `aomi --version` reports a version older than `0.4.2`, advise `npm install -g @aomi-labs/client@latest` (or use `npx @aomi-labs/client@latest …` for one-shot calls) before continuing. This matters more than it looks: **a global `aomi` is never upgraded by reinstalling the skill**, so a machine can sit on an old binary indefinitely while the skill docs move ahead. On 0.1.x, `aomi account` had only `login` and `whoami`, account auth lived at `aomi wallet login`, and `aomi tx sign` still attempted AA locally.
- If a command errors with `Unknown command`, check it against [commands.md → Not in v0.4.2](commands.md#not-in-v042) before assuming the CLI is broken.

## Quirks observed in current CLI/source

These are not bugs the skill should try to fix — they are CLI behaviors to recognize and route around.

- **`[session] Backend user_state mismatch (non-fatal)` log spam** appears between the prompt and the agent response. These lines are large JSON dumps that look alarming. Ignore them — they are not errors. Look past them for the actual agent response and the `⚡ Wallet request queued: tx-N` line.
- **The active session pointer can disappear between shell invocations.** If `aomi tx list` returns `No active session. Run \`aomi chat\` first.` after a successful chat, run `aomi session list` to find the session id (look for `topic` matching what you just asked the agent), then `aomi session resume <N> > /dev/null && aomi tx list` in the **same** shell call.
- **`aomi deploy` is advertised but not wired up.** It appears in `aomi --help` under COMMANDS, but it is not registered as a subcommand in v0.4.2, so `aomi deploy` exits with `❌ Unknown command deploy` and `aomi deploy --help` prints the generic root help. Fix pending in aomi-labs/aomi#467; until a release ships it, do not use it.
- **Stale failed-simulation txs accumulate.** When the agent retries (e.g. Across with expired deadlines), the failed prior attempts stay visible in `aomi tx list`. Match against the `batch_status` metadata: only sign txs whose status reads `Batch [...] passed`. Skip ones tagged `failed at step N: 0x...`.
- **Agent self-heals expired deadlines.** For deadline-bearing routes (Across, Khalani fillers), if simulation reports an expiry, the agent will rebuild the request automatically with fresh deadlines. Do not re-prompt — just check `aomi tx list` for the latest passing batch.
- **`BYOK key set for anthropic: sk-ant-...` echoes the first ~7 characters of the provider key.** This is by design (provider identification, not authentication). Do not try to scrub it from output — it is not a credential leak.
- **Public backend app/model introspection can return 404.** Treat `aomi app list` and `aomi model list` as convenience commands. A 404 there does not prove chat, tx, simulation, or signing is broken.
- **Solana instruction-only pending requests are not fully CLI-signable yet.** The current TypeScript signer reconstructs pending Solana signables when the backend/local pending record includes `unsigned_tx` / `unsignedTx`. Canonical `svm_ixs` without an unsigned tx may be filtered out.

## Native gas

If `aomi tx sign` returns `insufficient funds for transfer` from viem, the signing EOA has no native gas on the destination chain. Since local signing is EOA-only in v0.4.2, there is no sponsorship path to fall back on — the EOA needs a small amount of native gas on that chain (~0.0005 ETH equivalent is enough). Do not retry with different flags; see [account-abstraction.md](account-abstraction.md#gas-the-rule-the-skill-must-follow).
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall