Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
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.
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.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
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).
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.
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.
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.
Validate chainId and recipient. Respect per-tx and daily limits from config. Always provide a block explorer link when a tx is confirmed.
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.
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.
wallets.defaults.spending.mode: "notify" (default) or "auto" (sends without approval). wallets.defaults.spending.limitPerTx, dailyLimit, allowedChains, allowedRecipients, notifyChannels: enforced for send/ERC20/contract calls. wallets.notify.primaryChannel: where pending approvals are notified. wallets.interactWithUnverifiedContracts: if false, only allow verifiedTokenAddresses and verifiedContractAddresses.
After approval and broadcast, always include a tx link. Use: /tx/<txHash> for transactions /address/<address> for addresses Base URL comes from wallets.chains.<chainId>.blockExplorerUrl when configured, otherwise fallback well-known explorers.
If host tooling is available, prefer these tools: wallet_send, wallet_balance, wallet_txStatus, wallet_approve wallet_erc20_approve, wallet_erc20_transfer, wallet_contract_call If the host provides CLI instead, use the host wallet CLI for create/address/send/approve and recover/import flows.
Starter config: wallet-config.json Install skill in project: openclast-wallet install-skill
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.