skills/check-balance/SKILL.md
Check a Nano account's balance and pending amount. You can check YOUR wallet's balance (via wallet_balance/wallet_probe_balances) or any address (via rpc_account_balance).
npx skillsauth add casualsecurityinc/xno-skills check-balanceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When a user asks "did you receive it?" / "check the balance", you need an on-chain data source. This skill queries a Nano node RPC (user-provided) for balance and pending (both in raw).
Nano can show funds as pending until the receiving wallet publishes the receive/open block. Many wallet apps do this automatically; raw keys alone do not.
If you see pending funds, you must call wallet_receive to pocket them.
If the user doesn't have an RPC URL, suggest these public nodes:
https://rpc.nano.org (Nano Foundation)https://app.natrium.io/api/rpc (Natrium)https://nanonode.cc/api (NanoNode.cc)https://node.somenano.site/api (SomeNano)xno-skills)Set an RPC URL (recommended):
export NANO_RPC_URL="https://rpc.nano.org"
Then:
npx -y xno-skills rpc account-balance <address> --json --xno
Or pass the URL explicitly:
npx -y xno-skills rpc account-balance <address> --url "https://rpc.nano.org" --json --xno
xno-mcp)If the agent has access to the xno-mcp tools:
First, set defaults (recommended):
config_set: { "rpcUrl": "https://rpc.nano.org" }
Then check balance:
rpc_account_balance with { "address": "...", "rpcUrl": "..." }wallet_balance with { "name": "my-wallet", "index": 0 }If you see pending funds, receive them:
wallet_receive with { "name": "my-wallet", "index": 0 }If the user can't provide an RPC URL (or the environment has no network access), ask them to check the address in a block explorer or in their wallet app and report back:
tools
Nano (XNO) cryptocurrency wallet operations, transaction analysis, and explorer lookups. Use for send/receive, balances, pending funds, address validation, unit conversion, tx/hash/account lookup, explorer links, and Nano block-lattice questions. Prefer xno-mcp first; use xno-skills CLI as fallback.
testing
Verify an off-chain message signature (NOMS / ORIS-001 standard) against a Nano (XNO) address or public key. Use this skill whenever the user presents a signed message and wants to verify its authenticity, needs to confirm someone owns a Nano address, or asks 'is this signature valid?' — even if they just say 'check this proof' or 'did they really sign this?'
development
Validate Nano (XNO) addresses offline (format, checksum) — no network required. Use this skill whenever the user provides a Nano address and wants to verify it's well-formed, before sending XNO to an untrusted address, or asks 'is this address real?' — even if they just paste a nano_ address and ask 'is this right?' Always validate before any XNO send operation.
tools
Sign an off-chain message (plain text) using a Nano (XNO) custodial wallet managed by xno-mcp, following the NOMS / ORIS-001 standard. Use this skill whenever the user wants to prove ownership of a Nano address, authenticate themselves cryptographically, sign a statement with their XNO key, or create an off-chain proof — even if they just say 'prove I own this wallet' or 'sign this for me'.