Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Communication & Collaboration
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".
skill openclawclawhub Free
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".
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, references/endpoints.md, scripts/sage-config.sh, scripts/sage-rpc.sh, scripts/test-config.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- Koba42Corp
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
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
PlatformCert PathKey Pathmac~/Library/Application Support/com.rigidnetwork.sage/ssl/wallet.crt...wallet.keylinux~/.local/share/sage/ssl/wallet.crt...wallet.keywindows%APPDATA%\com.rigidnetwork.sage\ssl\wallet.crt...wallet.key When platform is "auto", detect via uname -s.
Configuration
CommandAction/sage statusShow config and test connection/sage configDisplay 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 resetReset to defaults
Operations
Route to appropriate sub-skill based on domain: DomainSub-SkillExample CommandsAuth & Keyssage-auth/sage login, /sage logout, /sage keysXCHsage-xch/sage send xch, /sage balance, /sage combineCAT Tokenssage-cat/sage cats, /sage send cat, /sage issue catNFTssage-nft/sage nfts, /sage mint nft, /sage transfer nftDIDssage-did/sage dids, /sage create didOfferssage-offers/sage offers, /sage make offer, /sage take offerOptionssage-options/sage options, /sage mint optionCoinssage-coins/sage coins, /sage check addressTransactionssage-txn/sage pending, /sage submitNetworksage-network/sage peers, /sage networkSystemsage-system/sage sync, /sage versionWalletConnectsage-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-SkillWhen to Loadsage-authLogin, logout, key management, mnemonicssage-xchSend/receive XCH, combine, split coinssage-catCAT token operationssage-nftNFT minting, transfers, collectionssage-didDID creation and managementsage-offersOffer creation, acceptance, cancellationsage-optionsOptions protocol operationssage-coinsCoin queries, address validationsage-txnTransaction signing, submissionsage-networkPeer and network settingssage-systemSync status, version, databasesage-walletconnectWalletConnect integration
First Run
On first invocation: Check for config file; create if missing Detect platform if set to "auto" Verify cert/key files exist If missing, prompt user to configure paths 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"
Category context
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs3 Scripts
- SKILL.md
- README.md
- references/endpoints.md
- scripts/sage-config.sh
- scripts/sage-rpc.sh
- scripts/test-config.sh