OpenClaw

openclast-wallet

Guides the agent in Openclast/Openclaw wallet usage, approvals, and safety rules. Use when users ask about wallet setup, balances, transactions, approvals, or key export.

fabriziogianni70 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install fabriziogianni7/openclast-wallet

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Openclast Wallet Agent Guide

Quick start

Use the CLI to bootstrap:
- openclast-wallet setup creates wallet-config.json in the current folder.
- openclast-wallet setup --config ./wallet-config.json initializes the wallet from that file.
Prefer wallet-config.json in the project root and customize chains and limits before use.
Keep wallet-config.json separate from openclaw.json (Openclaw config does not accept a top-level wallets key).

Approval flow (mandatory)

All send/approve/contract operations create a pending transaction that requires explicit approval. Always:

Create the pending tx (send/erc20/contract call).
Ask the user to approve.
Only after approval, broadcast and confirm.

If the user asks to “just send,” still require approval unless config is explicitly set to auto mode.

Key export warning (mandatory)

Never expose private keys by default. If the user asks for export:

Require explicit confirmation.
Warn that key export is dangerous and should be protected.
Use environment gates if available (e.g., MOLTBOT_ALLOW_WALLET_EXPORT=1) and explicit CLI confirmation.

If export is not supported in this host, say so and offer safer alternatives.

Common tasks

Balance and tokens

Use the correct chainId for the chain the user mentions.
If a chain is not configured, read-only balance may still be possible via well-known public RPCs.

Sending

Validate chainId and recipient.
Respect per-tx and daily limits from config.
Always provide a block explorer link when a tx is confirmed.

Chain name → chainId

Ethereum / Mainnet: 1
Sepolia: 11155111
Polygon: 137
Base: 8453
Arbitrum One: 42161

When the user says “balance on Sepolia” or “send on Ethereum,” always map to a chainId and proceed.

Safety defaults

Default mode is notify/approval, not auto-send.
Restrict unverified contracts when possible.
Store private keys only in OS keychain (macOS) and never in config...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/fabriziogianni7/openclast-wallet
Version: —
Commit: 9e33d31296235c9d078c5d7be6a4712803d34977
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Openclast Wallet Agent Guide

## Quick start

- Use the CLI to bootstrap:
  - `openclast-wallet setup` creates `wallet-config.json` in the current folder.
  - `openclast-wallet setup --config ./wallet-config.json` initializes the wallet from that file.
- Prefer `wallet-config.json` in the project root and customize chains and limits before use.
- Keep `wallet-config.json` separate from `openclaw.json` (Openclaw config does not accept a top-level `wallets` key).

## Approval flow (mandatory)

All send/approve/contract operations create a **pending transaction** that requires explicit approval.
Always:
1. Create the pending tx (send/erc20/contract call).
2. Ask the user to approve.
3. Only after approval, broadcast and confirm.

If the user asks to “just send,” still require approval unless config is explicitly set to auto mode.

## Key export warning (mandatory)

Never expose private keys by default. If the user asks for export:
- Require explicit confirmation.
- Warn that key export is dangerous and should be protected.
- Use environment gates if available (e.g., `MOLTBOT_ALLOW_WALLET_EXPORT=1`) and explicit CLI confirmation.

If export is not supported in this host, say so and offer safer alternatives.

## Common tasks

### Balance and tokens
- Use the correct chainId for the chain the user mentions.
- If a chain is not configured, read-only balance may still be possible via well-known public RPCs.

### Sending
- Validate chainId and recipient.
- Respect per-tx and daily limits from config.
- Always provide a block explorer link when a tx is confirmed.

### Chain name → chainId

- Ethereum / Mainnet: `1`
- Sepolia: `11155111`
- Polygon: `137`
- Base: `8453`
- Arbitrum One: `42161`

When the user says “balance on Sepolia” or “send on Ethereum,” always map to a chainId and proceed.

## Safety defaults

- Default mode is notify/approval, not auto-send.
- Restrict unverified contracts when possible.
- Store private keys only in OS keychain (macOS) and never in config...

搜索