Skill Bundles
Theaomi-labs/skills repo ships two skill bundles:
aomi-transact
Teaches agents how to use the Aomi CLI for on-chain operations — chat, simulate, sign. The agent learns to:- Run natural-language chat sessions against any Aomi App
- Simulate transactions on forked network state before signing
- Sign and broadcast transactions through the wallet pipeline
- Manage sessions, switch models, and configure API keys
- Handle errors and recovery flows
aomi-build
Teaches agents how to scaffold and build new Aomi Apps from API specs. The agent learns to:- Generate Aomi SDK project structure (
lib.rs,client.rs,tool.rs) - Design tools that wrap REST/GraphQL endpoints
- Configure preambles, models, and MCP servers
- Validate builds and run tests
Installation
Prerequisites
@aomi-labs/clientv0.1.30 or newer — the CLI runtime that executes all on-chain operationsviem— wallet integration for transaction signingaomi-sdk(Rust) — only needed if building custom apps withaomi-build
Protocol Catalog
Theaomi-transact skill references 25+ protocol integrations that the Aomi runtime loads dynamically. Each app has its own tool set and credential requirements:
| App | Description | App-Specific Tools | Credentials |
|---|---|---|---|
default | General-purpose on-chain agent with web search | brave_search | None |
binance | Binance CEX — prices, order book, klines | binance_get_price, binance_get_depth, binance_get_klines | Exchange credentials |
bybit | Bybit CEX — orders, positions, leverage | (No Bybit-specific tools yet) | Exchange credentials |
cow | CoW Protocol — MEV-protected swaps via batch auctions | get_cow_swap_quote, place_cow_order, get_cow_order_status | None |
defillama | DefiLlama — TVL, yields, volumes, stablecoins | get_token_price, get_yield_opportunities, get_defi_protocols, get_chain_tvl, get_dex_volumes | None |
dune | Dune Analytics — execute and fetch SQL queries | execute_query, get_execution_status, get_execution_results | Provider token |
dydx | dYdX perpetuals — markets, orderbook, candles, trades | dydx_get_markets, dydx_get_orderbook, dydx_get_candles, dydx_get_trades, dydx_get_account | None |
gmx | GMX perpetuals — markets, positions, orders, prices | get_gmx_prices, get_gmx_markets, get_gmx_positions, get_gmx_orders | None |
hyperliquid | Hyperliquid perps — mid prices, orderbook | get_meta, get_all_mids | None |
kaito | Kaito — crypto social search, trending, mindshare | kaito_search, kaito_get_trending, kaito_get_mindshare | Provider token |
kalshi | Kalshi prediction markets via Simmer SDK | simmer_register, simmer_status, simmer_briefing | SDK token |
khalani | Khalani cross-chain intents — quote, build, submit | get_khalani_quote, build_khalani_order, submit_khalani_order, get_khalani_order_status | None |
lifi | LI.FI aggregator — cross-chain swaps and bridges | get_lifi_swap_quote, place_lifi_order, get_lifi_bridge_quote, get_lifi_transfer_status | Optional provider token |
manifold | Manifold prediction markets — search, bet, create | list_markets, get_market, search_markets, place_bet, create_market | Provider token |
molinar | Molinar on-chain world — move, explore, chat | molinar_get_state, molinar_move, molinar_jump, molinar_chat, molinar_collect_coins | None |
morpho | Morpho lending — markets, vaults, positions | get_markets, get_vaults, get_user_positions | None |
neynar | Farcaster social — users, search | get_user_by_username, search_users | Provider token |
okx | OKX CEX — tickers, order book, candles | okx_get_tickers, okx_get_order_book, okx_get_candles | Exchange credentials |
oneinch | 1inch DEX aggregator — quotes, swaps, allowances | get_oneinch_quote, get_oneinch_swap, get_oneinch_approve_transaction | Provider token |
para | Para — MPC wallet management across EVM, Solana, Cosmos | (Para wallet tools) | Provider token |
polymarket | Polymarket prediction markets — search, trade, CLOB | search_polymarket, get_polymarket_details, get_polymarket_trades, build_polymarket_order_preview | None |
polymarket-rewards | Polymarket LP — liquidity provisioning into reward markets | (LP scoring and position tools) | Provider token |
x | X/Twitter — users, posts, search, trends | get_x_user, get_x_user_posts, search_x, get_x_trends | Provider token |
yearn | Yearn Finance — vault discovery, details | get_all_vaults, get_vault_detail, get_blacklisted_vaults | None |
zerox | 0x DEX aggregator — swaps, quotes, liquidity | get_zerox_swap_quote, place_zerox_order, get_zerox_swap_chains | Provider token |
--app <name> to select an app for a chat turn, or set AOMI_APP=<name> for a multi-command shell.
Security
Skills are security-audited against the OWASP AST03 framework. Every PR runs four automated scanners in CI:| Scanner | Purpose |
|---|---|
| pors/skill-audit | Skill-specific behavioral analysis |
| Cisco AI Defense | Offline behavioral analysis |
| NMitchem/SkillScan | Static skill analysis |
| Snyk agent-scan | Dependency and configuration scanning |
FAQ
What AI tools support Aomi Skills?
Claude Code, Cursor, VS Code Copilot, Gemini CLI, and any tool that implements the Agent Skills specification. Install once and your agent knows the full Aomi command surface.How are skills different from MCP servers?
Skills are markdown instruction files — the agent reads them at runtime to learn procedures and tool patterns. MCP servers are live endpoints that expose tools via the Model Context Protocol. Skills tell the agent how to use Aomi; MCP servers execute live actions like querying a database. They’re complementary — skills can reference MCP-connected tools.Do skills execute code on my machine?
No. Skills are read-only markdown files. The agent reads them and executes the shell commands described within (e.g.,aomi chat, aomi tx sign). The actual execution happens through the Aomi CLI, which runs in your terminal with your permissions.
What are the prerequisites for using a skill?
You need@aomi-labs/client v0.1.30+ and viem for wallet signing. For building custom apps, you also need the Rust aomi-sdk. No other dependencies — the skill definitions are self-contained markdown.
How do I switch between protocols?
Use--app <name> in any aomi chat command, or set AOMI_APP=<name> in your shell for a multi-command session. Run aomi app list to see all available apps from the backend.
What happens when an app needs credentials?
The CLI reports at runtime what credentials are missing. Configure them on your end or runaomi secret add with the value you supply. The skill never invents or pastes credentials on your behalf.
Can I build my own app and add it to the catalog?
Yes. Use theaomi-build skill and the aomi-sdk Rust SDK to scaffold a new app from an API spec. The SDK provides the CoreAppBuilder pattern — define your tools, preamble, and model, then deploy it as a loadable app in the Aomi runtime.
Are skills kept up to date?
Theaomi-labs/skills repo is actively maintained. Each PR runs four security scanners, and the skill definitions are updated alongside CLI releases. Run npx skills update to pull the latest versions.
Which chains does Aomi support?
Aomi supports all EVM chains accessible through the configured RPC endpoints, plus Solana and Cosmos via the Para wallet integration. Individual apps may have chain-specific requirements — the app catalog and CLI output indicate supported networks.Do I need to install both skill bundles?
No. Install both withnpx skills add aomi-labs/skills and your agent picks the right one based on context. aomi-transact activates on transaction-related prompts; aomi-build activates on app-building prompts.
SDK for Custom Skills
For protocol teams that want to build their own Aomi App (with custom tools, preamble, and deployment), use theaomi-sdk Rust SDK. The SDK provides the CoreAppBuilder pattern for constructing apps that the Aomi runtime can load and the skills layer can invoke.
See Building Apps for the full SDK reference.
Repositories
| Repo | Description |
|---|---|
| aomi-labs/skills | Official skill definitions — aomi-transact, aomi-build, and the full protocol catalog |
| aomi-labs/aomi-sdk | Rust SDK for building custom Aomi Apps and plugins |
| aomi-labs/aomi | Core widget library, backend runtime, and CLI client |
Next Steps
- Building Apps — create custom Aomi Apps with the Rust SDK
- Custom Tools — extend Aomi with your own tools
- CLI Reference — full CLI command reference