Source profileQuality 93/100

aomi-labs/skills/aomi-transact/SKILL.md

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

Source repository stars
7
Declared platforms
3
Static risk flags
1
Last source update
2026-08-23
Source checked
2026-08-25

Decision brief

What it does: where it fits

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.

Best for

  • The user wants to chat with the Aomi agent from the terminal.
  • The user wants balances, prices, routes, quotes, or transaction status.
  • The user wants to build, simulate, confirm, sign, or broadcast wallet requests.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexDeclaredSource recordInstall path and trigger
Claude CodeDeclaredSource recordInstall path and trigger
CursorDeclaredSource recordInstall path and trigger
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/aomi-labs/skills --skill "aomi-transact"
Safe inspection promptEditorial

Inspect the Agent Skill "aomi-transact" from https://github.com/aomi-labs/skills/blob/783b6debae3182aa4906fbbc301cb2a27510d0c9/aomi-transact/SKILL.md at commit 783b6debae3182aa4906fbbc301cb2a27510d0c9. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Instructions

    1. Detect the CLI and check its version: aomi --version 2/dev/null || npx @aomi-labs/client@latest --version. If it prints below 0.6.0, stop and tell the user to run npm install -g @aomi-labs/client@latest, or prefix every command with npx @aomi-labs/client@latest instead. An al…

    Detect the CLI and check its version: aomi --version 2/dev/null || npx @aomi-labs/client@latest --version. If it prints below 0.6.0, stop and tell the user to run npm install -g @aomi-labs/client@latest, or prefix every…Start a new session: aomi chat "" --new-sessionInspect queue: aomi tx list
  2. 02

    Prerequisites

    Node.js 18+ with npm or npx

    Node.js 18+ with npm or npx@aomi-labs/client v0.6.0 or newer: npm install -g @aomi-labs/client@latestFor EVM signing: a 0x-prefixed private key via aomi wallet set, --private-key, or PRIVATEKEY
  3. 03

    Examples

    Four end-to-end walkthroughs (approve+swap, lending, bridging, staking) in examples.md. Per-app first-turn examples (Khalani, 0x, Polymarket, Binance, Neynar) in apps.md.

    Four end-to-end walkthroughs (approve+swap, lending, bridging, staking) in examples.md. Per-app first-turn examples (Khalani, 0x, Polymarket, Binance, Neynar) in apps.md.
  4. 04

    Output

    aomi chat: agent response or ⚡ Wallet request queued: tx-N

    aomi chat: agent response or ⚡ Wallet request queued: tx-Naomi tx list: table of pending/signed tx ids with batchstatusaomi tx simulate: per-step success/failure, revert reason, gas usage
  5. 05

    Error Handling

    Full troubleshooting in troubleshooting.md.

    Full troubleshooting in troubleshooting.md.

Permission review

Static risk signals and limitations

Writes files

medium · line 91

The documentation asks the agent to create, modify, or delete local files.

aomi account login|whoami|logout|links|link|unlink|rename|update|delete|sessions|switch

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score93/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars7SourceRepository attention, not individual Skill quality
Compatibility3 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
aomi-labs/skills
Skill path
aomi-transact/SKILL.md
Commit
783b6debae3182aa4906fbbc301cb2a27510d0c9
License
MIT
Collected
2026-08-25
Default branch
main
View the original SKILL.md

Aomi Transact

Overview

Aomi Transact drives the aomi TypeScript CLI to build natural-language crypto agents and web3 assistants. It composes calldata, fork-simulates transactions as a batch, and stages wallet requests for explicit user signing — non-custodial throughout. Current chain metadata includes Ethereum, Polygon, Arbitrum, Base, Base Sepolia, Optimism, Sepolia, Linea, Linea Sepolia, Monad, Monad Testnet, Robinhood Chain, MegaETH, and local Anvil. The npm CLI is the production/end-user surface; the Rust aomi-cli in product-mono is an in-process dev/test CLI with a different command surface — never mix the two. For deep references, see commands.md, workflows.md, gotchas.md, account-abstraction.md, apps.md, examples.md, session.md, drain-vectors.md, troubleshooting.md.

Prerequisites

  • Node.js 18+ with npm or npx
  • @aomi-labs/client v0.6.0 or newer: npm install -g @aomi-labs/client@latest
  • For EVM signing: a 0x-prefixed private key via aomi wallet set, --private-key, or PRIVATE_KEY
  • For Solana sign-only flows: a base58 or JSON keypair via aomi wallet set --solana (which also persists the cluster; --cluster overrides), --solana-private-key, or SOLANA_PRIVATE_KEY
  • Optional: AOMI_ACCOUNT_BEARER / --account-bearer for authenticated account-bound requests
  • Native gas on the destination chain for the signing EOA — local signing is EOA-only, so there is no sponsorship fallback

Instructions

  1. Detect the CLI and check its version: aomi --version 2>/dev/null || npx @aomi-labs/client@latest --version. If it prints below 0.6.0, stop and tell the user to run npm install -g @aomi-labs/client@latest, or prefix every command with npx @aomi-labs/client@latest instead. An already-installed global aomi is never upgraded by installing this skill, and the pre-0.4 surface differs.
  2. Start a new session: aomi chat "<task>" --new-session
  3. Inspect queue: aomi tx list
  4. For multi-step flows, simulate first: aomi tx simulate tx-1 tx-2
  5. Sign: aomi tx sign tx-1
  6. Verify: aomi session status or aomi session log

For the full procedure (read-only requests, building wallet requests, signing policy, batch simulation, secret ingestion), see workflows.md.

Examples

aomi chat "what is the price of ETH?" --new-session
aomi chat "swap 1 ETH for USDC" --new-session --public-key 0xYourAddress --chain 1
aomi tx list && aomi tx simulate tx-1 tx-2 && aomi tx sign tx-1 tx-2
aomi chat "stake 0.5 ETH on Lido" --app lido --chain 1 --new-session

Four end-to-end walkthroughs (approve+swap, lending, bridging, staking) in examples.md. Per-app first-turn examples (Khalani, 0x, Polymarket, Binance, Neynar) in apps.md.

Output

  • aomi chat: agent response or ⚡ Wallet request queued: tx-N
  • aomi tx list: table of pending/signed tx ids with batch_status
  • aomi tx simulate: per-step success/failure, revert reason, gas usage
  • aomi tx sign: transaction hash and on-chain confirmation

Error Handling

ErrorCauseSolution
insufficient funds for transferSigning EOA has no native gasFund the EOA on the destination chain — local signing has no sponsorship path
AA execution now runs in the backend laneAn AA path was selected on tx signDrop --aa/--aa-provider/--aa-mode; if no flags were passed, unset AOMI_AA_PROVIDER/AOMI_AA_MODE
stateful: false in simulationWrong batch orderReorder tx ids to match execution dependency
RPC 401/429Rate-limited or missing keySet --rpc-url to authenticated endpoint
No tx queued after chatAgent returned quote firstRun aomi tx list; send a confirmation reply
Orphaned tx-N in listPrevious simulation failedOnly sign txs with batch_status: passed
Failed to get apps/models: HTTP 404Public backend does not expose that introspection routeTreat app list/model list as backend-dependent; do not block chat/sign flows on it

Full troubleshooting in troubleshooting.md.

Safety Justification

This skill is risk_tier: L2 because it can sign and broadcast on-chain transactions. The permissions manifest enforces least privilege:

  • Shell allowlist scopes execution to aomi and npx @aomi-labs/client@latest only — no arbitrary subprocesses.
  • Network allowlist restricts outbound traffic to chat.aomi.dev (the CLI's default backend; api.aomi.dev is the legacy host). User-supplied --rpc-url endpoints are resolved by the CLI itself; operators must review them before allowing signing.
  • File scope is read+write to ~/.aomi/ only; identity files (SOUL.md, MEMORY.md, AGENTS.md) are deny-listed against writes per OWASP AST03 mitigation #3.
  • No blind signing. Multi-step flows go through aomi tx simulate on a forked chain before aomi tx sign. Drain-vector calldata fields (recipient, onBehalfOf, mintRecipient, _to) are blocked at simulation time when they do not equal msg.sender — see drain-vectors.md.
  • Opaque credentials. The skill never fabricates, derives, or echoes credential values; setup commands run only when the user explicitly asks and supplies the value in this turn. Full rules in gotchas.md → Hard Rules.

When to Use

  • The user wants to chat with the Aomi agent from the terminal.
  • The user wants balances, prices, routes, quotes, or transaction status.
  • The user wants to build, simulate, confirm, sign, or broadcast wallet requests.
  • The user wants to inspect or switch apps, models, chains, or sessions.
  • The user wants to inspect or change Account Abstraction preferences (synced to the backend lane).
  • The user wants to authenticate a CLI account with aomi account login, inspect it with aomi account whoami, or inspect linked wallets and login methods with aomi account links.
  • The user wants to build a new app from an API spec or SDK — use the companion skill aomi-build.

Command Surface

aomi                                Interactive REPL
aomi --prompt "<message>"           Send one prompt and exit
aomi chat <message>                 Send a message
aomi tx list|simulate|sign
aomi session list|new|resume|delete|status|log|events|close
aomi model list|set|current
aomi app list|current
aomi chain list|set|current
aomi wallet set|current|whoami
aomi account login|whoami|logout|links|link|unlink|rename|update|delete|sessions|switch
aomi logout
aomi config set-backend|current
aomi secret list|clear|add

There is no aomi thread, aomi cron, aomi login, or aomi wallet ls|dev-key|set-mode on this CLI — those belong to the separate Rust aomi-cli. aomi deploy is advertised in --help but unreachable in v0.4.2 (fix pending in aomi-labs/aomi#467). Full command reference, flags, and env vars in commands.md.

Resources

Frequently asked questions

What to verify before installation and use

What does the aomi-transact source document cover?

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.

How do I install aomi-transact?

The source record exposes this install command: npx skills add https://github.com/aomi-labs/skills --skill "aomi-transact". Inspect the command and pinned source before running it.

Which Agent platforms does the source record declare?

The pinned source record declares support for: codex, claude code, cursor.

Which permission-related actions were detected?

Static rules flagged write-files in the source; the page lists the matching lines and excerpts.

Alternatives

Compare before choosing