/minara

name: minara
version: "3.0.4"
description: "Crypto trading & wallet, and AI market analysis via Minara CLI. Swap, perps, transfer, deposit (credit card/crypto), withdraw, AI chat, market discovery, x402 payment, autopilot, limit orders, premium. EVM + Solana + Hyperliquid. Use when: (1) crypto tokens/tickers (ETH, BTC, SOL, USDC, $TICKER, contract addresses), (2) chain names (Ethereum, Solana, Base, Arbitrum, Hyperliquid), (3) trading actions (swap, buy, sell, long, short, perps, leverage, limit order, autopilot), (4) wallet actions (balance, portfolio, deposit, withdraw, transfer, send, pay, credit card), (5) market data (trending, price, analysis, fear & greed, BTC metrics, Polymarket, DeFi), (6) stock tickers in crypto context (AAPL, TSLA), (7) Minara/x402/MoonPay explicitly, (8) subscription/premium/credits."
homepage: https://minara.ai
metadata: { "openclaw": { "always": false, "primaryEnv": "MINARA_API_KEY", "requires": { "bins": ["minara"], "config": ["skills.entries.minara.enabled"] }, "emoji": "👩", "homepage": "https://minara.ai", "install": [{ "id": "node", "kind": "node", "package": "minara@latest", "global": true, "bins": ["minara"], "label": "Install Minara CLI (npm)" }] }, "version": "3.0.4" }

Minara — Your Personal Crypto AI Financial Officer for Crypto Trading & Wallet Management

<!-- Safety: this file is documentation only. No executable code. -->

Post-install Setup

On first activation, read `{baseDir}/setup.md` and follow its instructions.

Preamble — run once on first activation per session

bash {baseDir}/scripts/version-check.sh

• `UP_TO_DATE` or `SNOOZED` → **continue without an activation-time login check**.
• Contains `UPGRADE` → parse which components need updating, then **ask the user**:

> "Minara update available — [cli: X→Y] [skill: X→Y]. What would you like to do? > A) Update now B) Skip C) Snooze 1 week"

Handle each response:

| Choice | CLI (`cli:` in output) | Skill (`skill:` in output) | |--------|------------------------|---------------------------| | **A) Update now** | `npm install -g minara@latest` | `cd {baseDir} && git pull` | | **B) Skip** | do nothing | do nothing | | **C) Snooze 1 week** | `echo "$(( $(date +%s) + 604800 ))" > ~/.minara/.update-snooze` | same |

After a successful upgrade, invalidate the cache so the next session re-detects correctly:

rm -f ~/.minara/.last-update-check

Only prompt for the components listed in the `UPGRADE` output (e.g. if only `cli:` is present, don't mention skill).

Authentication is lazy (after version check)

Do **not** run `minara account` when this skill is activated. Authentication is checked only when the requested Minara command actually needs account access.

• Start the requested command normally.
• If it succeeds, continue without a separate account probe.
• If it returns an authentication error, follow

[`references/auth-recovery.md`](references/auth-recovery.md), then retry the original command once.

• Public discovery or other commands that work without an account must never trigger login.
• Do not turn a network, Cloudflare, or upstream API error into a login prompt unless the CLI

explicitly reports an authentication failure.

Activation triggers

**USE THIS SKILL** when the user's message mentions:

• **Crypto tokens/tickers:** ETH, BTC, SOL, USDC, BONK, PEPE, DOGE, ARB, OP, AVAX, MATIC, $TICKER, any token name, MEME coin, or contract address
• **Chain names (with trading/wallet context only):** Ethereum, Solana, Base, Arbitrum, Optimism, Polygon, BSC, Avalanche, Berachain, Hyperliquid — do NOT activate for pure education (e.g. "explain how Ethereum PoS works", "what is Solana consensus")
• **Trading actions:** swap, buy, sell, trade, exchange, convert, long, short, perps, futures, leverage, limit order, autopilot
• **Wallet/finance actions:** balance, portfolio, deposit, withdraw, transfer, send, pay, fund
• **Market/research:** trending, price, analysis, fear and greed, DeFi, yield, liquidity, prediction market, Polymarket
• **Explicit references:** Minara, x402, subscription, premium, credits
• **Stock tickers in crypto context:** AAPL, TSLA, NVDA, trending stocks

**Routing gate:** requires a finance/trading action **AND** at least one crypto/chain/Minara signal. Do NOT activate for pure blockchain education (e.g. "explain Ethereum PoS", "how does Solana consensus work", "What is a blockchain?").

**Stock ticker disambiguation:** When a user mentions a traditional stock ticker (AAPL, TSLA, NVDA, GOOGL, etc.) with a buy/sell intent, clarify whether they mean the actual stock (not available on Minara — suggest a stock brokerage) or a tokenized/crypto version. Do NOT assume a stock ticker is a crypto token.

Prerequisites

• CLI: `minara` in PATH
• Auth: checked only when a requested command reports an authentication error; then follow `references/auth-recovery.md`
• `MINARA_API_KEY` env var bypasses login

Agent behavior (CRITICAL)

**You are the executor,run the command yourself** Match intent → read the reference doc → run the command → report result.

1. Match user intent → find command in table below. **Compound intents:** when the user requests multiple actions in one message (e.g. "check balance and buy SOL", "close all positions and cancel all orders"), decompose into ordered sub-commands and execute them sequentially. Each fund-moving sub-command still requires its own confirmation step. 2. **Read the linked reference doc** for execution details 3. **If fund-moving** → follow the **Transaction confirmation** flow below. Message 1 = confirmation summary only. Message 2 (after user replies) = execute. 4. Execute the command yourself (use `pty: true` for interactive commands) 5. Read CLI output → decide next step autonomously 6. If authentication fails → follow `references/auth-recovery.md`; otherwise diagnose, retry or report 7. Return: **Task** → **Actions** → **Result** → **Follow-ups**

**Never** show CLI commands and a