Sage Wallet

Interact with the Sage Chia blockchain wallet via RPC. Use for XCH transactions, CAT tokens, NFTs, DIDs, offers, options, coin management, and wallet configuration. Supports cross-platform setups (Mac/Linux/Windows) with configurable RPC endpoints and SSL certificates. Invoke with /sage commands or natural language like "send XCH", "check my NFTs", "create an offer", "mint a CAT token".

This skill appears to be what it claims: a local RPC client for the Sage/Chia wallet. Before installing or using it, consider: 1) The scripts require access to your wallet client certificate and private key (files under your home or APPDATA). Those files enable authenticated RPC calls — if misused they can be used to move funds or reveal mnemonics. 2) The sub-skill 'sage-auth' exposes endpoints such as get_secret_key and login; do not run those commands unless you trust the skill and the environment. 3) Keep rpc_url pointed at a local or trusted node (default is https://127.0.0.1:9257). Do not point the skill to remote or unknown RPC endpoints. 4) Prefer running tests in dry mode first (scripts support --live flags) and verify cert/key file paths before running live operations. 5) Because the repository/source is unknown, prefer obtaining this skill from a trusted source (official Sage or verified registry entry), inspect code locally, and avoid enabling auto-login or saving secrets unless necessary. If you need further checks, provide the omitted sub-skill files for a deeper review or confirm checksum/signature from a trusted upstream repository.

Type: OpenClaw Skill Name: sage-wallet Version: 1.0.0 This skill is designed to interact with a local Sage Chia blockchain wallet via its RPC interface. It uses shell scripts (`sage-config.sh`, `sage-rpc.sh`) to manage configuration and make authenticated RPC calls using `curl`. While it accesses sensitive files like wallet certificates and private keys (`~/.local/share/sage/ssl/wallet.crt`, `~/.local/share/sage/ssl/wallet.key`) and performs network operations, this is a functional requirement for mutual TLS authentication with the local wallet RPC. The documentation (`SKILL.md`, `README.md`, sub-skill markdown files) is transparent about its capabilities, explicitly states it does not store or transmit mnemonics, and provides security best practices. There is no evidence of intentional data exfiltration to external endpoints (default RPC is localhost), malicious execution, persistence mechanisms, or prompt injection attempts against the agent.