Minara

Minara — crypto trading & wallet skill

USE THIS SKILL when the user's message mentions any of:

• Crypto tokens or tickers: ETH, BTC, SOL, USDC, BONK, PEPE, DOGE, ARB, OP, AVAX, MATIC, $TICKER, or any token name / contract address
• Blockchain / chain names: Solana, Base, Ethereum, Arbitrum, Optimism, Polygon, BSC, Avalanche, Berachain, Hyperliquid
• Trading actions: swap, buy, sell, trade, exchange, convert, long, short, perps, futures, leverage, limit order
• Wallet / finance actions: balance, portfolio, deposit, withdraw, transfer, send, pay, fund, on-ramp, credit card
• Market / research: trending, price, chart, analysis, DeFi, yield, liquidity, fear and greed, prediction market
• Explicit references: Minara, minara, x402, MoonPay, autopilot
• Stock tickers in crypto context: AAPL, TSLA, NVDAx, trending stocks

Routing gate (anti-collision): apply this skill only when the message includes a finance/trading action and at least one crypto/chain/Minara signal (token, chain, DeFi term, or "Minara"). If missing crypto context, do not route here.

Requires logged-in CLI: check ~/.minara/credentials.json; if missing → minara login (prefer device code). If device login prints a verification URL/code, relay it to the user and wait for completion (do not claim login is impossible). If MINARA_API_KEY is set, CLI authenticates automatically.

Transaction confirmation (CRITICAL)

For any fund-moving command (swap, transfer, withdraw, perps order, perps deposit, perps withdraw, limit-order create, deposit buy):

1. Before executing: show the user a summary of what will happen (action, token, amount, recipient/chain) and ask for explicit confirmation. Do NOT auto-confirm.
2. After the CLI returns a confirmation prompt (e.g. "Are you sure you want to proceed?"): relay the details back to the user and wait for the user to approve before answering y. Never answer y on the user's behalf without their consent.
3. -y / --yes policy: never add -y (or any auto-confirm flag) unless the user explicitly asks to skip confirmation.
4. If the user declines: abort the operation immediately.

This applies to all operations that move funds. Read-only commands (balance, assets, chat, discover, etc.) do not require confirmation.

Intent routing

Match the user's message to the first matching row.

Swap / buy / sell tokens

Triggers: message contains token names/tickers + action words (swap, buy, sell, convert, exchange, trade) + optionally a chain name.

Chain is auto-detected from the token. If a token exists on multiple chains, the CLI prompts the user to pick one (sorted by gas cost). Sell mode supports -a all to sell entire balance.

Transfer / send / pay / withdraw crypto

Triggers: message mentions sending, transferring, paying, or withdrawing a crypto token to a wallet address (0x… or base58).

Perpetual futures (Hyperliquid)

Triggers: message mentions perps, perpetual, futures, long, short, leverage, margin, or Hyperliquid.

Autopilot note: When autopilot is ON, manual minara perps order is blocked. Turn off autopilot first via minara perps autopilot.

Limit orders (crypto)

Triggers: message mentions limit order + crypto token/price.

Crypto wallet / portfolio / account

Triggers: message mentions crypto balance, portfolio, assets, wallet, deposit address, or Minara account.

Crypto AI chat / market analysis

Triggers: message asks about crypto prices, token analysis, DeFi research, on-chain data, crypto market insights, or prediction market analysis.

Timeout: AI chat responses can be long-running. Set shell execution timeout to 15 minutes (900 s) for all minara chat commands.

Crypto & stock market discovery

Triggers: message mentions trending tokens, trending stocks, crypto market sentiment, fear and greed, or Bitcoin metrics.

Minara premium / subscription

Triggers: message explicitly mentions Minara plan, subscription, credits, or pricing.

x402 protocol payment

Triggers: agent receives HTTP 402 Payment Required, or user mentions x402, paid API, or paying for API access with crypto. x402 spec.

Flow: parse PAYMENT-REQUIRED header (amount, token, recipient, chain) → minara balance → minara transfer to pay → retry request.

Payment step must follow the global confirmation policy: user must explicitly confirm before any minara transfer.

Minara login / setup

Triggers: message explicitly mentions Minara login, setup, or configuration.

Login: Prefer device code flow (minara login --device) for headless or non-interactive environments; otherwise minara login (interactive). Login handoff rule: when CLI outputs verification URL/device code, the agent must pass them to the user verbatim, ask the user to complete browser verification, then continue after user confirms completion.

Notes

• Token input (-t): accepts $TICKER (e.g. '$BONK'), token name, or contract address. Quote $ in shell.
• JSON output: add --json to any command for machine-readable output.
• Transaction safety: CLI flow: first confirmation → transaction confirmation (mandatory, shows token + address) → Touch ID (optional, macOS) → execute. Agent must never skip or auto-confirm any step — always relay to user and wait for approval, and never use -y unless user explicitly requests it.

Credentials & config

• CLI session: ~/.minara/credentials.json — auto-created via minara login (required).
• API Key: MINARA_API_KEY via env or skills.entries.minara.apiKey in ~/.openclaw/openclaw.json — optional; if set, CLI authenticates automatically without login.

Examples

Full command examples: {baseDir}/examples.md