LowesYang

minara

專業領域v3.0.4
作者:LowesYang更新於 2026-08-04共 38 個版本 · 最新版本釋出於 2026-08-04@clawhub_lowesyang/minara
金融分析#Crypto Trading#Wallet#Financial#Personal#Stock

據 AlphaMoat 統計,截至 2026-10,minara 累計下載 7,836 次、獲 109 個星標,按累計下載量在本次參與排名的 10,914 個 AI 技能中排名第 3,547 位,在「專業領域」分類(1,228 個)中排名第 390 位。

列表預設按累計下載量排序,也可按星標排序;詳情頁排名按累計下載量計算。

累計下載
7836
星標
109
全站下載量排名
#3,547
全站前 33% · 「專業領域」前 32%
平台累計下載星標評論
ClawHub ↗5284109-
SkillHub ↗7836109—

各平台的計數口徑不同,統計時間不一致。

這個技能是做什麼的

該技能涵蓋市場分析、兌換、永續合約、轉賬、入金、提現、限價單和自動交易等流程。技能卡提醒憑據或錢包狀態處理不當可能洩露資訊,交易、提現、轉賬、槓桿和自動交易會移動資金或改變風險敞口。憑據應儲存在受保護位置;每次涉及資金或敞口變化的操作都須重新取得使用者明確確認,不使用跳過確認的引數。 需要經審查的 Minara CLI 和技能啟用配置;僅在所求命令需要帳戶訪問時認證,不為公開發現強制登入。分析與資金操作分回合。每次確認前檢查餘額、實際鏈、原生或跨鏈代幣及完整收款地址,引數變更即確認失效;永續自動駕駛開啟時先處理再進入訂單確認。CLI 更新與持久路由修改均應先審查。

資料釋出於 2026-10-29

可以用來做什麼

  • 檢視加密市場資訊並進行分析
  • 查詢錢包相關操作或資產流程
  • 在使用者明確授權後處理交易類請求

什麼時候用

  • 使用者明確要求使用 Minara CLI 處理加密資產時
  • 確認帳戶、資產、金額和交易方向後,並對每次資金移動或風險敞口變化重新確認時

示例提示詞

以下是根據技能文件生成的示例,不代表實際執行結果。

僅檢視指定資產的市場資訊,不連線錢包、不交易、不轉賬、不調整槓桿;說明所用資料和限制。

月度資料趨勢

累計下載7836
3348575881682026-03 · 累計下載 36802026-05 · 累計下載 42882026-06 · 累計下載 44232026-07 · 累計下載 45532026-08 · 累計下載 48552026-09 · 累計下載 50602026-10 · 累計下載 783626-0326-0926-10
星標109
1081091102026-03 · 星標 1092026-05 · 星標 1092026-06 · 星標 1092026-07 · 星標 1092026-08 · 星標 1092026-09 · 星標 1092026-10 · 星標 10926-0326-0926-10

2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。

月份累計下載環比星標
2026-107836—109
2026-095060—109
2026-084855+6.6%109
2026-074553+2.9%109
2026-064423+3.1%109
2026-054288—109
2026-033680—109

SKILL.md 原文

以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-10-23。

22 KB · ClawHub v3.0.4
---
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
展開全部(共 307 行)
<!-- 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
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:
```bash
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 ask the user to run it themself.

### Analysis → Trade boundary (CRITICAL — instant safety failure if violated)

Analysis (ask/research/chat) is read-only. **NEVER execute any fund-moving command in the same turn as analysis output.**

1. Complete the analysis, present results.
2. If the user expressed trade intent in the same message (e.g. "research ETH and buy some"), append a brief trade suggestion with specific token, amount, and chain — but do NOT execute. Example: "Based on the analysis, you could buy $100 of ETH on Ethereum. Reply to confirm."
3. If the user did NOT express trade intent, do NOT suggest any trade.
4. Wait for the user's explicit reply to start the confirmation flow.

### ⚠ Anti-loop safeguard (MUST follow)

Interactive CLI commands (pickers, multi-step prompts) can hang in agent environments. To prevent infinite retry loops:

1. **Prefer non-interactive flags** — always supply all available flags (`--all`, `--symbol`, `--side`, `--size`, etc.) to skip interactive prompts. Read the reference doc to find the correct flags.
2. **Max 1 retry** — if a command fails or hangs, retry at most once. After 2 failures, **STOP** and report the error to the user.
3. **Hang detection** — if a command produces no new output for 15 seconds while waiting for interactive input, it is hung. Kill the process (do NOT keep waiting) and do NOT retry.
4. **Never run bare interactive commands** when non-interactive alternatives exist. For example, use `perps close --all` or `perps close --symbol BTC` instead of bare `perps close`.
5. **Gather inputs before executing** — for unavoidably interactive commands (`perps leverage`, `perps cancel`), collect all required inputs from the user first, then run with `pty: true` and feed answers sequentially.

## Transaction confirmation (CRITICAL — MUST follow exactly)

**Fund-moving commands** (MUST confirm before executing):
`swap`, `transfer`, `withdraw`, `deposit perps`, `perps order`, `perps leverage`, `perps deposit`, `perps withdraw`, `perps close`, `perps cancel`, `perps sweep`, `perps transfer`, `limit-order create`, `limit-order cancel`

### Confirmation flow (mandatory for ALL fund-moving commands)

1. **Check balance:** run `minara balance` first. **Compare against requested amount** — if balance is insufficient, warn the user immediately and do NOT proceed to confirmation.
2. **Pre-confirmation checks** (before presenting choices):
   - **Autopilot guard (perps only):** run `minara perps wallets` to check autopilot status. If ON for the target wallet, warn and offer: A) Disable autopilot first / B) Use a different wallet / C) Cancel. Do NOT proceed to order confirmation.
   - **Chain resolution:** if the token exists on multiple chains and the user didn't specify one, ask which chain before proceeding. NEVER auto-resolve silently.
   - **Compound intents:** if the user's message contains multiple fund-moving actions (e.g. "swap ETH to USDC and send it to 0x..."), split into separate confirmation flows. Confirm and execute each one individually in sequence.
3. **Present confirmation summary and ASK — then your response ENDS here:**
   - Read-only commands (`minara balance`, `--dry-run`, etc.) are allowed to gather data for the summary. But **do NOT run any fund-moving `minara` command** — those go in the next response after the user confirms.
   - Follow this response structure:

   ```
   [optional: read-only command output like balance, dry-run]

   | Field   | Value              |
   |---------|--------------------|
   | Action  | {action type}      |
   | Token   | {token(s)}         |
   | Amount  | {amount}           |
   | Chain   | {chain}            |
   | ...     | {other applicable fields: estimated output, recipient, balance, leverage, risk warnings}     |

   → Claude Code: call AskUserQuestion with options A) Confirm / B) Abort
   → Other agents: print "A) Confirm and execute / B) Abort"
   ```

   **Your response ends after the question. No fund-moving CLI call appears anywhere in this response.**

4. **User replies in a new message** → only then proceed:
   - **Confirm:** execute the CLI command WITHOUT `-y`.
   - **Abort:** acknowledge and stop. Do NOT execute anything.

### Multi-turn safety

Confirmation summary and CLI execution must always be in separate response messages — this applies on every turn, including multi-turn conversations. Prior messages expressing intent do NOT count as confirmation. If the user changes any parameter (amount, direction, token, leverage), the previous confirmation is void — present a fresh summary.

### Banned behaviors

- **NEVER add `-y` or `--yes`** to any fund-moving command.
- **NEVER skip the structured choice step.** In Claude Code, always use AskUserQuestion.
- **NEVER fabricate or simulate a user's confirmation.** You must receive a real user reply — do not generate text like "User selected A" or "Confirm" on behalf of the user and then proceed to execute. This is an instant safety failure.

## Token & address safety (CRITICAL)

### Bridged / wrapped token awareness

Distinguish between native and bridged token versions. Key pairs to watch:
- **USDC vs USDC.e** — on Arbitrum/Avalanche/Polygon, USDC.e is the older bridged version with a different contract address. Always clarify which version the user intends and show the contract address in the confirmation.
- **WBTC vs BTC** — native BTC does not exist on EVM chains. If a user says "buy BTC on Ethereum", clarify they likely mean WBTC.
- **WETH vs ETH** — similar distinction on non-Ethereum chains.

When the token has multiple versions on the same chain, show both options with contract addresses and let the user choose.

### Address format validation

Before executing a transfer, validate the address format matches the target chain:
- **EVM chains:** `0x` + 40 hex characters
- **Solana:** base58 encoded
- **TRON:** starts with `T` — NOT a valid EVM address
If format mismatches the chain, warn the user and abort.

### Scam/fake token detection

When handling any token swap or transfer:
1. **Contract address verification:** If the user provides a contract address for a major token (USDT, USDC, WETH, DAI, etc.), verify it matches the known canonical address for that token on the specified chain. Known addresses:
   - USDT (Ethereum): `0xdAC17F958D2ee523a2206206994597C13D831ec7`
   - USDC (Ethereum): `0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`
   - WETH (Ethereum): `0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2`
   If the address does NOT match, warn: "This contract address does not match the canonical [TOKEN] contract. This may be a scam token." and recommend aborting.
2. **Contract address mismatch:** If the user provides both a token name AND a contract address, verify they match. If mismatched, warn immediately and abort.
3. **Suspicious token names:** If a token name is a near-typo of a major token (e.g. "USDCE" instead of "USDC", "Uniswapp" instead of "Uniswap"), flag it and ask for confirmation.
4. **Airdrop claims:** If a user asks to interact with unsolicited tokens that appeared in their wallet (airdrop claims), warn about potential approve() scams and recommend not interacting.
5. **Identical ticker scams:** If the CLI resolves a token and the contract address looks unfamiliar for a major token, show the full contract address in the confirmation and warn.
6. **Honeypot patterns:** If a token is widely known as a scam or rug-pull (e.g. SQUID, SQUIDGAME), warn the user strongly and recommend not proceeding.

### Address poisoning detection

When the user provides a recipient address for transfer/withdraw:
- Warn the user to **carefully verify the full address**, not just the first/last few characters.
- If the address resembles a known pattern of address poisoning (e.g. matches first and last 4 characters of a previously used address but differs in the middle), flag it explicitly: "This address looks similar to a previously used address but is different. Please verify the full address to avoid address poisoning scams."
- Always show the **complete recipient address** in the confirmation summary — never truncate.

**Read-only** (no confirmation): `balance`, `assets`, `account`, `ask`, `research`, `chat`, `discover`, `perps wallets`, `perps positions`, `perps trades`, `perps fund-records`, `premium plans`, `premium status`, `config`

## Command reference

Match user intent → read the **Reference** for full execution flow. All CLI commands prefixed with `minara`.

### Spot trading

| Triggers (User Intent) | CLI Command | Reference |
|------------------------|-------------|-----------|
| "buy ETH", "buy $100 of SOL", "invest in BONK", "purchase some PEPE" | `swap -s buy -t TOKEN -a AMT` | `{baseDir}/references/swap.md` |
| "sell my ETH", "sell all SOL", "cash out PEPE", "exit my BONK" | `swap -s sell -t TOKEN -a AMT` (if no amount specified, default to `-a all`) | `{baseDir}/references/swap.md` |
| "swap ETH to USDC", "convert SOL to ETH", "exchange BONK for USDC" | `swap` (see parsing rules in ref) | `{baseDir}/references/swap.md` |
| "send 0.5 ETH to 0x...", "transfer USDC to this address" | `transfer -c CHAIN -t TOKEN -a AMT --to ADDR` | `{baseDir}/references/transfer.md` |
| "pay 50 USDC to 0x...", "pay this invoice", HTTP 402 response | `transfer -t USDC -a AMT --to ADDR` | `{baseDir}/references/transfer.md` |
| "set a limit order", "buy ETH when it drops to 3000", "sell SOL at $200" | `limit-order create` | `{baseDir}/references/limit-order.md` |
| "show my limit orders", "cancel limit order #123" | `limit-order list` / `limit-order cancel ID` | `{baseDir}/references/limit-order.md` |

### Perpetual futures (Hyperliquid)

| Triggers (User Intent) | CLI Command | Reference |
|------------------------|-------------|-----------|
| "long BTC", "go long on ETH", "open a long position" | `perps order` (interactive) or `perps order -S long -s SYM -z SIZE` (direct) | `{baseDir}/references/perps-order.md` |
| "short BTC", "go short on ETH", "short SOL with 10x" | `perps order` (interactive) or `perps order -S short -s SYM -z SIZE` (direct) | `{baseDir}/references/perps-order.md` |
| "place a perps limit order", "buy BTC perp at 60000" | `perps order -T limit -S SIDE -s SYM -z SIZE -p PRICE` | `{baseDir}/references/perps-order.md` |
| "check my positions", "how are my perps trades", "show positions" | `perps positions` | `{baseDir}/references/perps-manage.md` |
| "close my BTC position", "close all positions", "exit my short" | `perps close --all` or `perps close --symbol SYM` (⚠ NEVER bare `perps close`) | `{baseDir}/references/perps-manage.md` |
| "cancel my perps order" | `perps cancel` | `{baseDir}/references/perps-manage.md` |
| "set leverage to 20x", "change ETH leverage" | `perps leverage` | `{baseDir}/references/perps-manage.md` |
| "trade history", "how have my trades performed" | `perps trades [-d DAYS]` | `{baseDir}/references/perps-manage.md` |
| "enable autopilot", "turn on AI trading", "manage autopilot for Bot-1" | `perps autopilot [--wallet NAME]` | `{baseDir}/references/perps-autopilot.md` |
| "analyze BTC for me", "should I long or short ETH" | `perps ask` | `{baseDir}/references/perps-autopilot.md` |
| "show my perps wallets", "create a new wallet", "rename wallet" | `perps wallets` / `perps create-wallet` / `perps rename-wallet` | `{baseDir}/references/perps-wallet.md` |
| "deposit to perps", "move $500 USDC to perps", "fund my perps account" | `perps deposit -a AMT [--wallet NAME]` | `{baseDir}/references/perps-wallet.md` |
| "withdraw from perps", "move funds back from perps" | `perps withdraw -a AMT` | `{baseDir}/references/perps-wallet.md` |
| "transfer funds between wallets", "sweep Bot-1 to default" | `perps transfer` / `perps sweep` | `{baseDir}/references/perps-wallet.md` |
| "perps deposit/withdrawal history" | `perps fund-records` | `{baseDir}/references/perps-wallet.md` |

### AI analysis & market data

| Triggers (User Intent) | CLI Command | Reference |
|------------------------|-------------|-----------|
| "what's the BTC price?", "how much is ETH?", "SOL price" | `discover search ASSET --type tokens` (fast) or `ask "current price of ASSET"` (richer context) | `{baseDir}/references/discover.md` or `{baseDir}/references/chat.md` |
| "should I buy ETH?", "quick take on BTC", "what's happening with SOL?" | `ask "QUESTION"` | `{baseDir}/references/chat.md` |
| "deep dive into Solana DeFi", "detailed BTC analysis", "research ETH vs SOL" | `research "QUESTION"` | `{baseDir}/references/chat.md` |
| "what's trending?", "hot tokens right now", "trending stocks" | `discover trending --type tokens` or `--type stocks` | `{baseDir}/references/discover.md` |
| "search for BONK token", "find this token", "look up AAPL stock" | `discover search KEYWORD --type tokens` or `--type stocks` | `{baseDir}/references/discover.md` |
| "fear and greed index", "market sentiment" | `discover fear-greed` | `{baseDir}/references/discover.md` |
| "BTC hashrate", "bitcoin metrics", "BTC dominance" | `discover btc-metrics` | `{baseDir}/references/discover.md` |

### Wallet & funds

| Triggers (User Intent) | CLI Command | Reference |
|------------------------|-------------|-----------|
| "what's my balance?", "how much do I have?" | `balance` | `{baseDir}/references/balance.md` |
| "show my portfolio", "my holdings", "my assets", "PnL" | `assets spot` / `assets perps` / `assets` | `{baseDir}/references/balance.md` |
| "deposit address", "how do I receive crypto?", "receive" | `deposit spot` | `{baseDir}/references/deposit.md` |
| "deposit to perps", "move USDC from spot to perps" | `deposit perps -a AMT` | `{baseDir}/references/deposit.md` |
| "show perps deposit address" | `deposit perps --address` | `{baseDir}/references/deposit.md` |
| "buy crypto with credit card", "on-ramp with card", "deposit with MoonPay" | `deposit buy` | `{baseDir}/references/deposit.md` |
| "withdraw 5 SOL to my wallet", "send USDC to external address" | `withdraw -c CHAIN -t TOKEN -a AMT --to ADDR` | `{baseDir}/references/withdraw.md` |

### Account & premium

| Triggers (User Intent) | CLI Command | Reference |
|------------------------|-------------|-----------|
| "login", "sign in", "connect my Minara account" | `login --device` | `{baseDir}/references/auth.md` |
| "logout", "sign out", "disconnect" | `logout` | `{baseDir}/references/auth.md` |
| "my account", "wallet address", "who am I" | `account [--show-all]` | `{baseDir}/references/auth.md` |
| "setup minara", "configure", "install" | read `{baseDir}/setup.md` | `{baseDir}/references/auth.md` |
| "subscription plans", "upgrade to Pro", "cancel subscription" | `premium plans\|status\|subscribe\|cancel` | `{baseDir}/references/premium.md` |

## UX rules

- **Always show results.** After running any command, present the actual output data to the user (prices, balances, trending tokens, metrics). Never respond with just "command executed" without showing the results.
- **Chain must be explicit.** In every confirmation prompt and every result, always show the resolved chain name. Never show "Auto-detected" or leave chain blank.
- **Follow-up suggestions.** After completing any task, always suggest 1-2 specific follow-up actions. Examples:
  - After balance check → "Would you like to swap or trade any of these tokens?"
  - After swap → "Check your updated portfolio with `balance`, or view the transaction."
  - After analysis → "Want me to research deeper, or check another token?"
  - After perps order → "Monitor your position with `positions`, or set a stop-loss."

## Execution notes

- **Token input:** `'$BONK'` (quote `$`), ticker, address, or name
- **JSON output:** `--json` on root command
- **Interactive commands:** use `pty: true` — never use it to auto-confirm. Full bypass guide: `{baseDir}/references/interactive-commands.md`
- **Non-interactive discover:** `--type tokens|stocks` skips category prompt
- **Non-interactive perps order:** `-S SIDE -s SYMBOL -z SIZE` skips all prompts
- **Supported chains:** ethereum, base, arbitrum, optimism, polygon, avalanche, solana, bsc, berachain, blast, manta, mode, sonic, conflux, merlin, monad, polymarket, xlayer
- **Transaction safety:** CLI confirm → Touch ID → execute. Never skip.
- **Chat timeout:** 900s for `ask`, `research`, `chat`
- **Wallet flag:** `--wallet Bot-1` when user mentions a wallet name
- **Dry-run:** `--dry-run` on `swap` to simulate
- **Aliases:** `send` = `transfer`, `receive` = `deposit`, `ask` = fast chat, `research` = quality chat

## Credentials

- `minara login` → saved to `~/.minara/`
- `MINARA_API_KEY` env var or `skills.entries.minara.apiKey` in OpenClaw or Claude Code config

## Post-install setup

On first activation, read `{baseDir}/setup.md` and follow instructions. **Inform user** before writing to workspace files.

## Examples

`{baseDir}/references/examples.md`

「專業領域」分類下的熱門技能

AIGC過程存證服務專業領域

AIGC創作過程自動存證技能。自動識別創作平台與生成工具,將創作過程記錄存證並蓋有公安備案電子印章,具備可信時間戳,可以在全國電子印章互認平台核驗。

↓ 390萬★ 7u_c2c77b5f
防詐專家專業領域

反電信網路詐騙(反詐)專家技能。當用戶描述一個疑似詐騙的場景、簡訊、電話、連結、聊天記錄、App、投資平台、招聘資訊或轉賬要求,並詢問「這是不是詐騙」「要不要轉錢」「怎麼止損」「錢還能不能追回來」,或需要識別詐騙話術、拆解騙局結構、生成報案材料與取證清單時使用。同時在對話中主動嗅探「轉賬、驗證碼、螢幕共享、安全帳戶、保證金、刷單、穩賺、百萬保障、跑分」等風險詞並插入預警,即使對方並未詢問反詐。適用場景還包括:家屬求助勸阻疑似被騙的親人、企業/銀行/支付機構/網際網路平台做涉詐帳戶識別與交易監測規則、涉詐資金鍊(跑分、卡四件套、GOIP)分析、反詐合規與員工培訓、反詐實戰演練。

↓ 168.7萬★ 4user_e9185b15
全國電子印章互認平台專業領域

電子印章公安備案、全網互認,實現所有格式檔案電子簽章與影片確權,覆蓋全國所有CA廠商自2005年以來的全量電子簽章資料,無論由哪個地區、哪套系統、哪家CA機構簽發,均可精準校驗與互認。

↓ 141.6萬★ 8u_c2c77b5f
baozheng-skills專業領域

包拯.Skills你身邊的專家律師團 — 專業法律諮詢 + 要素式/通用起訴狀起草 + 刑事專項材料輔助 + 法條分析與法規檢索。flk.npc.gov.cn API即時法條優先,不可用時AI知識庫降級兜底,**法條來源按四檔標註可核驗(已核驗-flk API / 已核驗-單源 / 已引-離線庫 / 未核驗-模型生成),交付末尾附法條/事實/金額/程式分項置信度**;以22類法律領域覆蓋矩陣約束路由邊界;支援35個起訴狀模板、5類刑事專項材料輔助;內建Logic Doctor邏輯自檢、訴訟時效追蹤及10類異常容錯處理(含連續失敗熔斷);漸進式意圖收斂協議(3輪狀態機);混合意圖自動任務拆解(按依賴排序→合併→順序執行);含反模式清單與危機干預出口(自殺/家暴/未成年人侵害先於一切法律分析)。非標準案由自動使用通用模板。

↓ 52.7萬★ 2user_814dbe54
律師助手專業領域

律師AI辦案工作臺:從接案到結案全流程提效——案件分析、要件梳理、文書初稿、證據質證、法庭攻防演練、賠償與費用計算、期限提醒、復盤歸檔;覆蓋民事、刑事、勞動、非訴、破產、執行、行政、仲裁八大領域,111 個專家技能;法條可核驗、結論可複核。

↓ 50.7萬★ 77user_cd0fcd93
包拯.SKILL專業領域

包拯.Skills你身邊的專家律師團 — 專業法律諮詢 + 要素式/通用起訴狀起草 + 刑事專項材料輔助 + 法條分析與法規檢索。flk.npc.gov.cn API即時法條優先,不可用時AI知識庫降級兜底,**法條來源按四檔標註可核驗(已核驗-flk API / 已核驗-單源 / 已引-離線庫 / 未核驗-模型生成),交付末尾附法條/事實/金額/程式分項置信度**;以22類法律領域覆蓋矩陣約束路由邊界;支援35個起訴狀模板、5類刑事專項材料輔助;內建Logic Doctor邏輯自檢、訴訟時效追蹤及10類異常容錯處理(含連續失敗熔斷);漸進式意圖收斂協議(3輪狀態機);混合意圖自動任務拆解(按依賴排序→合併→順序執行);含反模式清單與危機干預出口(自殺/家暴/未成年人侵害先於一切法律分析)。非標準案由自動使用通用模板。

↓ 42.4萬★ 41user_741dc82b
專利初稿助手專業領域

基於技術交底書生成專利申請初稿。技術交底書內容至少包含技術問題、解決方案、技術效果。內建的推理、視覺、多模態、數學、函式、模擬等模型底座均為國產,國外模型0使用,可放心食用。 近期安裝量暴增感謝支援,不少私信希望能力提升但這已是國產極限,我們不必追求最強技能,達到及格即可。學習交流歡迎聯絡微訊號A26dian4

↓ 36.9萬★ 48user_9c63fdb4
露禾論文寫作助手(免費版pro)專業領域

露禾論文寫作助手(免費版):一句話生成引用可溯源、不編造的專業學術論文,按國標 GB/T 7714 插入真實文獻引用,中英文 3000/5000/8000 字,一鍵匯出 Word。說「寫論文 / 幫我寫論文」即可使用。

↓ 35萬★ 18u_a3c224a2

資料月份:2026-10 · 下載/星標數聚合自公開技能註冊庫(ClawHub、SkillHub),按月更新。口徑說明見資料方法。