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".

Security Scan

The skill's code, instructions, and runtime requirements are coherent for a local Sage (Chia) wallet RPC integrator — it legitimately needs access to the wallet's RPC URL, client certificate, and key and the scripts only call the declared local RPC endpoints.

Purpose & Capability

Name/description (Sage Chia wallet RPC) matches the included scripts and sub-skills. Config management and an mTLS RPC helper are expected for this purpose; listed endpoints and sub-skills correspond to wallet operations (XCH, CATs, NFTs, DIDs, offers, etc.). There are no unrelated credentials or binaries requested.

Instruction Scope

SKILL.md and the scripts instruct the agent to read and write a local config file and to read client certificate and key files (platform-specific defaults under user home or APPDATA). These actions are necessary for mTLS RPC calls and wallet operations, but they are sensitive: the skill exposes endpoints that can return mnemonics and perform transfers (e.g., get_secret_key/login/send_xch). The instructions do not attempt to read unrelated system files or call external endpoints beyond the configured RPC URL.

Install Mechanism

No install spec is provided (instruction-only with bundled scripts). That is low-risk compared to arbitrary downloads; the included shell scripts are plain and sourceable. No external archives or obscure URLs are used.

Credentials

The skill requests no environment variables in registry metadata, but its scripts will read configuration (SAGE_CONFIG_DIR/SAGE_CONFIG_FILE if set) and default to user-local cert/key locations (home or APPDATA). Access to wallet cert, key, and the ability to call RPC endpoints is necessary for the stated functionality. These are sensitive assets (private keys, mnemonics); their presence is proportionate to a wallet RPC skill but requires user caution.

Persistence & Privilege

Skill has no 'always: true' flag and is user-invocable. It does not attempt to modify other skills or system-wide agent settings. It writes/reads only its own config file under user config directories; that is expected behavior for a skill that manages wallet config.

Assessment

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.

Sage Wallet Skill

RPC interface to Sage wallet for Chia blockchain operations.

Configuration

User settings stored in {workspace}/config/sage-wallet.json:

{
  "platform": "auto",
  "rpc_url": "https://127.0.0.1:9257",
  "cert_path": null,
  "key_path": null,
  "fingerprint": null,
  "auto_login": false
}

Platform Defaults

Platform	Cert Path	Key Path
mac	~/Library/Application Support/com.rigidnetwork.sage/ssl/wallet.crt	...wallet.key
linux	~/.local/share/sage/ssl/wallet.crt	...wallet.key
windows	%APPDATA%\com.rigidnetwork.sage\ssl\wallet.crt	...wallet.key

When platform is "auto", detect via uname -s.

Slash Commands

Configuration

Command	Action
/sage status	Show config and test connection
/sage config	Display current settings
/sage config platform <auto|mac|linux|windows>	Set platform
/sage config rpc <url>	Set RPC URL
/sage config cert <path>	Set SSL cert path
/sage config key <path>	Set SSL key path
/sage config fingerprint <fp>	Set default wallet fingerprint
/sage config autologin <on|off>	Toggle auto-login
/sage config reset	Reset to defaults

Operations

Route to appropriate sub-skill based on domain:

Domain	Sub-Skill	Example Commands
Auth & Keys	sage-auth	/sage login, /sage logout, /sage keys
XCH	sage-xch	/sage send xch, /sage balance, /sage combine
CAT Tokens	sage-cat	/sage cats, /sage send cat, /sage issue cat
NFTs	sage-nft	/sage nfts, /sage mint nft, /sage transfer nft
DIDs	sage-did	/sage dids, /sage create did
Offers	sage-offers	/sage offers, /sage make offer, /sage take offer
Options	sage-options	/sage options, /sage mint option
Coins	sage-coins	/sage coins, /sage check address
Transactions	sage-txn	/sage pending, /sage submit
Network	sage-network	/sage peers, /sage network
System	sage-system	/sage sync, /sage version
WalletConnect	sage-walletconnect	/sage wc sign

Global Parameters

All commands accept optional overrides:

• --fingerprint <fp> — Use specific wallet
• --rpc <url> — Override RPC URL
• --cert <path> — Override cert path
• --key <path> — Override key path

Scripts

• scripts/sage-config.sh — Config management
• scripts/sage-rpc.sh — RPC caller with mTLS

Making RPC Calls

# Source the RPC helper
source scripts/sage-rpc.sh

# Call an endpoint
sage_rpc "get_sync_status" '{}'
sage_rpc "send_xch" '{"address":"xch1...","amount":"1000000000000","fee":"100000000"}'

Sub-Skills

Each sub-skill handles a specific domain. Load the appropriate one based on the operation:

Sub-Skill	When to Load
sage-auth	Login, logout, key management, mnemonics
sage-xch	Send/receive XCH, combine, split coins
sage-cat	CAT token operations
sage-nft	NFT minting, transfers, collections
sage-did	DID creation and management
sage-offers	Offer creation, acceptance, cancellation
sage-options	Options protocol operations
sage-coins	Coin queries, address validation
sage-txn	Transaction signing, submission
sage-network	Peer and network settings
sage-system	Sync status, version, database
sage-walletconnect	WalletConnect integration

First Run

On first invocation:

1. Check for config file; create if missing
2. Detect platform if set to "auto"
3. Verify cert/key files exist
4. If missing, prompt user to configure paths
5. Test connection with GetVersion

If certs not found, guide user:

Sage certificates not found. Configure with:
  /sage config cert /path/to/wallet.crt
  /sage config key /path/to/wallet.key

Error Handling

RPC errors return HTTP status codes:

• 400 — Bad request (invalid params)
• 401 — Unauthorized (cert mismatch)
• 404 — Not found
• 500 — Internal error

Always check response for error field before processing data.

Amount Formatting

Sage uses mojos (1 XCH = 1,000,000,000,000 mojos). The Amount type in requests/responses is a string representing mojos. Convert for display:

1 XCH = "1000000000000"
0.001 XCH = "1000000000"