one-wallet CLI Skill

Overview

This skill teaches the agent how to use the one-wallet CLI to manage Ethereum/EVM wallets and perform on-chain actions from the terminal or scripts.

Core capabilities:

• - Manage multiple wallets (create, import, list, set default, remove).
• Query balances for wallets and arbitrary addresses.
• Send native ETH and call or send contract methods (including ERC20/NFT).
• Sign messages and EIP-712 typed data, and verify signatures.
• Configure RPC providers and chain presets.
• Produce machine-readable JSON output suitable for scripts and AI tools.

Always assume Node.js ≥ 18 is available and one-wallet is installed globally, unless the repository indicates another setup.

When to use this skill

Use this skill when:

• - The user mentions one-wallet, wallet CLI, agent wallet, or this repository.
• The user wants to create or import wallets, check balances, or send ETH/tokens from the terminal.
• The user wants to call smart contracts, estimate gas, or inspect transaction status.
• The user needs message or typed-data signing/verification from a CLI.
• The user asks for JSON output for downstream automation or AI tools.

If the task is Ethereum/EVM related and can be done via CLI, prefer one-wallet over writing ad-hoc scripts.

Installation

Global install (recommended)

Use one of:

CODEBLOCK0

Verify:

CODEBLOCK1

From this repository

When working inside this project:

CODEBLOCK2

Prefer the global binary (one-wallet) when possible; use ./bin/run.js only when explicitly requested or when testing local changes.

Quick start workflow

1. 1. Set provider (RPC)

     one-wallet provider set mainnet
     

1. 2. Create a wallet and set as default

1. 3. Check balance and send ETH

Use --json on commands when the user wants machine-readable output for further processing.

Wallet management

Create or import wallets

• - Create a new wallet:

  one-wallet wallet create <name>
  

• - Create and set as default:

  one-wallet wallet create <name> --set-default
  

• - Create with password-protected storage:

  one-wallet wallet create <name> --password --set-default
  

• - Import from private key:

  one-wallet wallet import <name> --private-key 0xYourPrivateKey
  

• - Import with password:

List and select wallets

• - Human-readable list:

  one-wallet wallet list
  

• - JSON list:

  one-wallet wallet list --json
  

• - Show current default wallet:

  one-wallet wallet set default
  

• - Set default wallet:

Wallet storage path

Show where wallets and config are stored:

CODEBLOCK16

Balances

• - Balance of default wallet:

  one-wallet wallet balance
  

• - Balance of a named wallet:

  one-wallet wallet balance <name>
  

• - Balance of any address:

  one-wallet wallet balance-of 0xAddress
  

• - Balance as JSON (for scripts/AI tools):

Contract calls and sends

Read-only contract calls

Cast-style without ABI (single quotes to protect parentheses):

CODEBLOCK21

With preset ABI:

CODEBLOCK22

Sending ETH and tokens

Native ETH:

CODEBLOCK23

Skip confirmation for scripts:

CODEBLOCK24

Estimate gas:

CODEBLOCK25

ERC20 transfer and approve:

CODEBLOCK26

NFT transfer:

CODEBLOCK27

JSON output (tx hash and receipt):

CODEBLOCK28

Transaction status

Inspect a transaction by hash:

CODEBLOCK29

Signing and verification

EIP-191 message signing

Sign with default wallet:

CODEBLOCK30

JSON output (message, signature, address):

CODEBLOCK31

EIP-712 typed data

From file:

CODEBLOCK32

From inline JSON:

CODEBLOCK33

Verify signature

Recover signer:

CODEBLOCK34

Verify against expected address:

CODEBLOCK35

Passwords, encryption, and sessions

Password management

• - Encrypt existing wallet:

  one-wallet wallet set-password <name>
  

• - Remove encryption:

  one-wallet wallet remove-password <name>
  

• - Lock (clear session cache):

Environment variables

Key variables:

Use environment variables in CI or non-interactive scripts to avoid prompts and to keep secrets out of the repository.

Provider configuration

Inspect and set provider:

CODEBLOCK39

Prefer presets for common networks; use custom URLs when the user provides a specific RPC endpoint.

Scripting and JSON mode

When the user wants to integrate one-wallet with other tools or automation:

• - Always add --json when available to get structured output.
• Capture stdout and parse as JSON in the surrounding script or tool.
• Combine with password environment variables to avoid interactive prompts.

Examples:

CODEBLOCK40

Safety and best practices

• - Never hard-code real private keys or passwords in source-controlled files.
• Prefer ONE_WALLET_KEY_<NAME> and ONE_WALLET_PASSWORD_<NAME> environment variables for secrets.
• Use --json for automation; omit it for quick human inspection.
• Use -y only in scripts or when the user explicitly wants to skip confirmations.
• When in doubt about the chain or RPC, call one-wallet provider info before sending transactions.

Reference

For deeper details or updates, consult the project's README.md in this repository, which documents features, commands, and examples for one-wallet.