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 位。

列表默认按累计下载量排序,也可按星标排序;详情页排名按累计下载量计算。

累计下载
7,836
星标
109
全站下载量排名
#3,547
全站前 33% · 「专业领域」前 32%
平台累计下载星标评论
ClawHub ↗5,284109-
SkillHub ↗7,836109—

各平台的计数口径不同,统计时间不一致。

这个技能是做什么的

该技能涵盖市场分析、兑换、永续合约、转账、入金、提现、限价单和自动交易等流程。技能卡提醒凭据或钱包状态处理不当可能泄露信息,交易、提现、转账、杠杆和自动交易会移动资金或改变风险敞口。凭据应保存在受保护位置;每次涉及资金或敞口变化的操作都须重新取得用户明确确认,不使用跳过确认的参数。 需要经审查的 Minara CLI 和技能启用配置;仅在所求命令需要账户访问时认证,不为公开发现强制登录。分析与资金操作分回合。每次确认前检查余额、实际链、原生或跨链代币及完整收款地址,参数变更即确认失效;永续自动驾驶开启时先处理再进入订单确认。CLI 更新与持久路由修改均应先审查。

资料发布于 2026-10-29

可以用来做什么

  • 查看加密市场信息并进行分析
  • 查询钱包相关操作或资产流程
  • 在用户明确授权后处理交易类请求

什么时候用

  • 用户明确要求使用 Minara CLI 处理加密资产时
  • 确认账户、资产、金额和交易方向后,并对每次资金移动或风险敞口变化重新确认时

示例提示词

以下是根据技能文档生成的示例,不代表实际运行结果。

仅查看指定资产的市场信息,不连接钱包、不交易、不转账、不调整杠杆;说明所用数据和限制。

月度数据趋势

累计下载7,836
3,3485,7588,1682026-03 · 累计下载 3,6802026-05 · 累计下载 4,2882026-06 · 累计下载 4,4232026-07 · 累计下载 4,5532026-08 · 累计下载 4,8552026-09 · 累计下载 5,0602026-10 · 累计下载 7,83626-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-107,836—109
2026-095,060—109
2026-084,855+6.6%109
2026-074,553+2.9%109
2026-064,423+3.1%109
2026-054,288—109
2026-033,680—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.0万★ 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.0万★ 18u_a3c224a2

数据月份:2026-10 · 下载/星标数聚合自公开技能注册库(ClawHub、SkillHub),按月更新。口径说明见数据方法。