xno-skills 1.5.2 → 1.5.4

package/dist/cjs/version.d.ts

@@ -1,6 +1,6 @@
 export declare const pkg: {
     readonly name: "xno-skills";
-    readonly version: "1.5.2";
+    readonly version: "1.5.4";
 };
-export declare const version: "1.5.2";
+export declare const version: "1.5.4";
 //# sourceMappingURL=version.d.ts.map

package/dist/cjs/version.js

@@ -5,7 +5,7 @@ exports.version = exports.pkg = void 0;
 // Keep this in sync by running "npm run build" (prebuild hook).
 exports.pkg = {
     name: "xno-skills",
-    version: "1.5.2"
+    version: "1.5.4"
 };
 exports.version = exports.pkg.version;
 //# sourceMappingURL=version.js.map

package/dist/esm/.xno-mcp/requests.json

@@ -1,27 +1,27 @@
 {
   "requests": [
     {
-      "id": "mogj8e2n0bi3yc",
+      "id": "mogkau2r40zuif",
       "owsWalletId": "A",
       "accountIndex": 0,
       "address": "nano_1link1111111111111111111111111111111111111111111111111111111",
       "amountRaw": "10000000000000000000000000000",
       "reason": "explicit wallet test",
       "status": "pending",
-      "createdAt": "2026-04-27T01:42:29.183Z",
-      "updatedAt": "2026-04-27T01:42:29.183Z",
+      "createdAt": "2026-04-27T02:12:22.851Z",
+      "updatedAt": "2026-04-27T02:12:22.851Z",
       "receivedBlocks": []
     },
     {
-      "id": "mogj8e3mw1dwqc",
+      "id": "mogkau3kay40wu",
       "owsWalletId": "A",
       "accountIndex": 0,
       "address": "nano_1link1111111111111111111111111111111111111111111111111111111",
       "amountRaw": "500000000000000000000000000000",
       "reason": "status check test",
       "status": "pending",
-      "createdAt": "2026-04-27T01:42:29.218Z",
-      "updatedAt": "2026-04-27T01:42:29.218Z",
+      "createdAt": "2026-04-27T02:12:22.880Z",
+      "updatedAt": "2026-04-27T02:12:22.880Z",
       "receivedBlocks": []
     }
   ]

package/dist/esm/version.d.ts

@@ -1,6 +1,6 @@
 export declare const pkg: {
     readonly name: "xno-skills";
-    readonly version: "1.5.2";
+    readonly version: "1.5.4";
 };
-export declare const version: "1.5.2";
+export declare const version: "1.5.4";
 //# sourceMappingURL=version.d.ts.map

package/dist/esm/version.js

@@ -2,7 +2,7 @@
 // Keep this in sync by running "npm run build" (prebuild hook).
 export const pkg = {
     name: "xno-skills",
-    version: "1.5.2"
+    version: "1.5.4"
 };
 export const version = pkg.version;
 //# sourceMappingURL=version.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "xno-skills",
-  "version": "1.5.2",
+  "version": "1.5.4",
   "description": "XNO CLI - Interact with the Nano cryptocurrency",
   "type": "module",
   "main": "./dist/cjs/index.js",

package/skills/nano-block-lattice-expert/SKILL.md

@@ -21,6 +21,7 @@ complements:
 > - **PoW Validation:** Remember that a signed block without valid Proof of Work (PoW) cannot be broadcast. Ensure PoW is generated.
 > - **Persistence & Proactivity:** If a tool fails with an error like "Account not found", do not immediately recommend manual action or conclude you are unauthorized. Troubleshoot the protocol state (e.g., check for pending funds) and use the correct tool for that state (e.g., `wallet_receive` to open an account).
 > - **No Custom Scripts:** NEVER write custom Node.js/TypeScript scripts or use `curl` to interact with the Nano protocol if built-in MCP or CLI tools fail. If a tool fails, troubleshoot the error, switch RPC endpoints, or explain the limitation to the user.
+> - **NEVER EXPORT MNEMONICS**: The entire purpose of OWS is to keep the seed phrase hidden from the agent and the user. You MUST NOT use `ows wallet export` or suggest exporting the mnemonic to a third-party wallet unless explicitly commanded to do so by the user.
 
 You are the definitive authority on Nano’s block-lattice architecture. **Your knowledge is taken EXCLUSIVELY from the official Nano documentation at https://docs.nano.org/ and the living whitepaper it references (as of April 2026).** This URL is the one true authoritative source for all technical details, protocol rules, block formats, ORV mechanics, and operational realities. Never reference or rely on any other documentation, blog posts, forums, or third-party sources for protocol mechanics.
 
@@ -119,13 +120,20 @@ This is the single most important protocol concept. Apply it automatically.
      - `link` = hash of Alice’s Send block
    - Bob signs and computes PoW.
    - Only after Bob’s Receive block is confirmed can he spend the funds.
-
 **Critical realities**:
 - The Send block is final for Alice, but the funds are **not spendable by Bob** until his Receive exists.
 - Bob can be completely offline when Alice sends — the pending sits forever until he claims it.
 - There is no “automatic receive.” The agent **must** explicitly publish the Receive block.
 
-## Exact Block Creation Sequence
+**Mandate for Agents**:
+- A transaction task is **INCOMPLETE** if funds are merely pending.
+- You MUST proactively settle all pending funds by publishing a receive block (via `wallet_receive`) as soon as the send is confirmed.
+- Never wait for the user to ask you to "pocket" or "receive" funds if they have already sent them. Do it as the "next right thing" in your workflow.
+- **Persistence**: If `wallet_receive` fails with "Account not found", it means you are opening the account. Simply continue; the tool will handle it. **Never conclude that OWS cannot sign Nano blocks.** OWS is the primary signer for this project.
+- **The "Open" happens automatically**: Whether using the MCP tool `wallet_receive` or the CLI command `ows sign send-tx`, the transition from "unopened" to "opened" is handled seamlessly. The `send-tx` action in OWS is specifically designed to publish these blocks to the network.
+
+## Universal State Blocks (All Blocks Since 2018)
+...
 1. Fetch current frontier (`previous`).
 2. Build block data (account, previous, representative, balance, link).
 3. Serialize the data (excluding signature and work).

package/skills/nano-check-balance/SKILL.md

@@ -36,6 +36,7 @@ triggers:
 > - **PoW Validation:** Remember that a signed block without valid Proof of Work (PoW) cannot be broadcast. Ensure PoW is generated.
 > - **Persistence & Proactivity:** If a tool fails with an error like "Account not found", do not immediately recommend manual action or conclude you are unauthorized. Troubleshoot the protocol state (e.g., check for pending funds) and use the correct tool for that state (e.g., `wallet_receive` to open an account).
 > - **No Custom Scripts:** NEVER write custom Node.js/TypeScript scripts or use `curl` to interact with the Nano protocol if built-in MCP or CLI tools fail. If a tool fails, troubleshoot the error, switch RPC endpoints, or explain the limitation to the user.
+> - **NEVER EXPORT MNEMONICS**: The entire purpose of OWS is to keep the seed phrase hidden from the agent and the user. You MUST NOT use `ows wallet export` or suggest exporting the mnemonic to a third-party wallet unless explicitly commanded to do so by the user.
 
 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).
 
@@ -43,10 +44,13 @@ When a user asks "did you receive it?" / "check the balance", you need an on-cha
 
 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.**
+**Mandate**:
+- If you see **pending** funds during a balance check, you MUST proactively call `wallet_receive` to claim them.
+- Do not wait for the user to ask you to receive.
+- A transaction is not "received" until the `pending` balance moves to the `confirmed` balance.
 
 ## Well-known Public RPC Nodes
-
+...
 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)

package/skills/nano-convert-units/SKILL.md

@@ -31,6 +31,7 @@ triggers:
 > - **PoW Validation:** Remember that a signed block without valid Proof of Work (PoW) cannot be broadcast. Ensure PoW is generated.
 > - **Persistence & Proactivity:** If a tool fails with an error like "Account not found", do not immediately recommend manual action or conclude you are unauthorized. Troubleshoot the protocol state (e.g., check for pending funds) and use the correct tool for that state (e.g., `wallet_receive` to open an account).
 > - **No Custom Scripts:** NEVER write custom Node.js/TypeScript scripts or use `curl` to interact with the Nano protocol if built-in MCP or CLI tools fail. If a tool fails, troubleshoot the error, switch RPC endpoints, or explain the limitation to the user.
+> - **NEVER EXPORT MNEMONICS**: The entire purpose of OWS is to keep the seed phrase hidden from the agent and the user. You MUST NOT use `ows wallet export` or suggest exporting the mnemonic to a third-party wallet unless explicitly commanded to do so by the user.
 
 Convert between different XNO cryptocurrency units with BigInt precision. XNO uses 30 decimal places, making floating-point arithmetic unsafe. Always use this skill for accurate conversions.
 

package/skills/nano-create-wallet/SKILL.md

@@ -31,6 +31,7 @@ triggers:
 > - **PoW Validation:** Remember that a signed block without valid Proof of Work (PoW) cannot be broadcast. Ensure PoW is generated.
 > - **Persistence & Proactivity:** If a tool fails with an error like "Account not found", do not immediately recommend manual action or conclude you are unauthorized. Troubleshoot the protocol state (e.g., check for pending funds) and use the correct tool for that state (e.g., `wallet_receive` to open an account).
 > - **No Custom Scripts:** NEVER write custom Node.js/TypeScript scripts or use `curl` to interact with the Nano protocol if built-in MCP or CLI tools fail. If a tool fails, troubleshoot the error, switch RPC endpoints, or explain the limitation to the user.
+> - **NEVER EXPORT MNEMONICS**: The entire purpose of OWS is to keep the seed phrase hidden from the agent and the user. You MUST NOT use `ows wallet export` or suggest exporting the mnemonic to a third-party wallet unless explicitly commanded to do so by the user.
 
 Nano wallet management is delegated to the **Open Wallet Standard (OWS)**. This provides a unified, policy-gated vault for all agent keys.
 

package/skills/nano-generate-qr/SKILL.md

@@ -34,6 +34,7 @@ triggers:
 > - **PoW Validation:** Remember that a signed block without valid Proof of Work (PoW) cannot be broadcast. Ensure PoW is generated.
 > - **Persistence & Proactivity:** If a tool fails with an error like "Account not found", do not immediately recommend manual action or conclude you are unauthorized. Troubleshoot the protocol state (e.g., check for pending funds) and use the correct tool for that state (e.g., `wallet_receive` to open an account).
 > - **No Custom Scripts:** NEVER write custom Node.js/TypeScript scripts or use `curl` to interact with the Nano protocol if built-in MCP or CLI tools fail. If a tool fails, troubleshoot the error, switch RPC endpoints, or explain the limitation to the user.
+> - **NEVER EXPORT MNEMONICS**: The entire purpose of OWS is to keep the seed phrase hidden from the agent and the user. You MUST NOT use `ows wallet export` or suggest exporting the mnemonic to a third-party wallet unless explicitly commanded to do so by the user.
 
 Generates a terminal-friendly ASCII QR code for a Nano address, optionally including an amount.
 

package/skills/nano-mcp-wallet/SKILL.md

@@ -62,6 +62,7 @@ triggers:
 > - **PoW Validation:** Remember that a signed block without valid Proof of Work (PoW) cannot be broadcast. Ensure PoW is generated.
 > - **Persistence & Proactivity:** If a tool fails with an error like "Account not found", do not immediately recommend manual action or conclude you are unauthorized. Troubleshoot the protocol state (e.g., check for pending funds) and use the correct tool for that state (e.g., `wallet_receive` to open an account).
 > - **No Custom Scripts:** NEVER write custom Node.js/TypeScript scripts or use `curl` to interact with the Nano protocol if built-in MCP or CLI tools fail. If a tool fails, troubleshoot the error, switch RPC endpoints, or explain the limitation to the user.
+> - **NEVER EXPORT MNEMONICS**: The entire purpose of OWS is to keep the seed phrase hidden from the agent and the user. You MUST NOT use `ows wallet export` or suggest exporting the mnemonic to a third-party wallet unless explicitly commanded to do so by the user.
 
 > **CRITICAL: CALL `wallet_list` FIRST.** Before any other wallet operation, you MUST call `wallet_list` to identify available OWS wallets. Never assume a wallet name or existence without discovery.
 
@@ -71,9 +72,24 @@ The `xno-mcp` MCP server is a private wallet custody service. You **CAN** send a
 
 - Access **named OWS wallets** (e.g. `"my-agent"`) via `wallet_list`.
 - **Key Security**: Secrets stay encrypted in the OWS vault (`~/.ows`). `xno-mcp` requests OWS to sign transactions without ever seeing the private key.
+- **OWS Signing Capability**: Contrary to some hallucinations, **OWS DOES support Nano state block signing.** It is the primary way `xno-mcp` functions. Never assume OWS is limited to EVM chains.
+
+## Agent Chain of Thought (Mental Model)
+
+When a user says "I sent funds" or you see "Pending" funds:
+1. **Goal**: Settle the funds immediately. A transaction is not "done" until it is Received.
+2. **Action**: Call `wallet_receive`.
+3. **Internal Objection**: "Wait, the account is unopened/not found."
+4. **Resolution**: "That is normal for Nano. `wallet_receive` will handle the Open block automatically. Proceed."
+5. **Internal Objection**: "Does OWS support Nano signing?"
+6. **Resolution**: "YES. The `xno-mcp` server uses OWS as its secure signing backend for all Nano operations. Proceed."
+7. **Internal Objection**: "Should I export the mnemonic so the user can use Nault/Natrium?"
+8. **Resolution**: "NO. NEVER export the mnemonic. That defeats the purpose of an agent wallet. Rely on the MCP tools."
+9. **Internal Objection**: "But how do I 'open' the account?"
+10. **Resolution**: "The `wallet_receive` tool, or manually calling `ows sign send-tx` with a generated receive block, handles the 'open' process automatically. It is a seamless part of receiving the first funds."
 
 ## Built-in Zero-Config Defaults
-
+...
 As of v1.1.0, `xno-mcp` automatically uses public RPC nodes and standard representatives for all operations. You do **NOT** need to configure anything to get started.
 
 ### Overriding Defaults (Optional)
@@ -106,6 +122,25 @@ Call MCP tool:
 
 To create a new wallet, use the `ows` CLI (outside of MCP) or the `nano-create-wallet` skill instructions.
 
+## The "Unopened Account" is NOT an Error
+
+A "new" or "unopened" account chain (which returns "Account not found" from RPC) is a **very common situation** in a Nano context.
+- It **MUST NOT** be treated as exceptional or a failure.
+- When asked about an account or checking its balance, it is imperative to REPORT that the account is unused/unopened (e.g., "Balance is 0, but there are pending funds. The account is currently unopened.").
+- This state **does not block any actions** if the account belongs to one of your wallets. It only means you must produce the receive block and publish it.
+- **The "Open" happens automatically**: Whether using the MCP tool `wallet_receive` or the CLI command `ows sign send-tx`, the transition from "unopened" to "opened" is handled seamlessly. It is not a hallucination, it is by design.
+
+### Example CLI Workflow for Receiving Funds (Auto-Opens New Accounts)
+If MCP tools fail and you must fall back to the CLI, this is the exact, proven workflow to receive pending funds (which automatically opens a new account) using OWS:
+
+```bash
+# 1. Build the receive block (auto-detects the pending hash, sets previous to 0s for unopened accounts)
+R_TXN=$(bunx -y xno-skills block receive -a <your_nano_address> --url <rpc_url>)
+
+# 2. Sign and broadcast using OWS (send-tx automatically publishes the receive/open block to the network)
+bunx -y ows sign send-tx --chain nano --wallet <wallet_name> --tx "$R_TXN"
+```
+
 ## Troubleshooting: "Account Not Found" (Receiving First Funds)
 On the Nano network, an account does not exist on the ledger until its first receive block (often called an "open" block) is published.
 - If you check a balance or attempt to build a block and receive an `"Account not found"` error, **this is normal for a brand new wallet**.

package/skills/nano-request-payment/SKILL.md

@@ -33,6 +33,7 @@ triggers:
 > - **PoW Validation:** Remember that a signed block without valid Proof of Work (PoW) cannot be broadcast. Ensure PoW is generated.
 > - **Persistence & Proactivity:** If a tool fails with an error like "Account not found", do not immediately recommend manual action or conclude you are unauthorized. Troubleshoot the protocol state (e.g., check for pending funds) and use the correct tool for that state (e.g., `wallet_receive` to open an account).
 > - **No Custom Scripts:** NEVER write custom Node.js/TypeScript scripts or use `curl` to interact with the Nano protocol if built-in MCP or CLI tools fail. If a tool fails, troubleshoot the error, switch RPC endpoints, or explain the limitation to the user.
+> - **NEVER EXPORT MNEMONICS**: The entire purpose of OWS is to keep the seed phrase hidden from the agent and the user. You MUST NOT use `ows wallet export` or suggest exporting the mnemonic to a third-party wallet unless explicitly commanded to do so by the user.
 
 When you need XNO (e.g., for testing, for a task that requires funds, or because the operator offered), follow this workflow.
 

package/skills/nano-return-funds/SKILL.md

@@ -29,6 +29,7 @@ triggers:
 > - **PoW Validation:** Remember that a signed block without valid Proof of Work (PoW) cannot be broadcast. Ensure PoW is generated.
 > - **Persistence & Proactivity:** If a tool fails with an error like "Account not found", do not immediately recommend manual action or conclude you are unauthorized. Troubleshoot the protocol state (e.g., check for pending funds) and use the correct tool for that state (e.g., `wallet_receive` to open an account).
 > - **No Custom Scripts:** NEVER write custom Node.js/TypeScript scripts or use `curl` to interact with the Nano protocol if built-in MCP or CLI tools fail. If a tool fails, troubleshoot the error, switch RPC endpoints, or explain the limitation to the user.
+> - **NEVER EXPORT MNEMONICS**: The entire purpose of OWS is to keep the seed phrase hidden from the agent and the user. You MUST NOT use `ows wallet export` or suggest exporting the mnemonic to a third-party wallet unless explicitly commanded to do so by the user.
 
 When the operator asks you to return funds (e.g., "send it back", "return the XNO", "refund"), follow this workflow carefully.
 

package/skills/nano-sign-message/SKILL.md

@@ -26,6 +26,7 @@ triggers:
 > - **PoW Validation:** Remember that a signed block without valid Proof of Work (PoW) cannot be broadcast. Ensure PoW is generated.
 > - **Persistence & Proactivity:** If a tool fails with an error like "Account not found", do not immediately recommend manual action or conclude you are unauthorized. Troubleshoot the protocol state (e.g., check for pending funds) and use the correct tool for that state (e.g., `wallet_receive` to open an account).
 > - **No Custom Scripts:** NEVER write custom Node.js/TypeScript scripts or use `curl` to interact with the Nano protocol if built-in MCP or CLI tools fail. If a tool fails, troubleshoot the error, switch RPC endpoints, or explain the limitation to the user.
+> - **NEVER EXPORT MNEMONICS**: The entire purpose of OWS is to keep the seed phrase hidden from the agent and the user. You MUST NOT use `ows wallet export` or suggest exporting the mnemonic to a third-party wallet unless explicitly commanded to do so by the user.
 
 Sign an off-chain message (plain text) using a custodial wallet managed by `xno-mcp`. This follows the NOMS (Nano Off-chain Message Signature) / ORIS-001 standard.
 

package/skills/nano-validate-address/SKILL.md

@@ -28,6 +28,7 @@ triggers:
 > - **PoW Validation:** Remember that a signed block without valid Proof of Work (PoW) cannot be broadcast. Ensure PoW is generated.
 > - **Persistence & Proactivity:** If a tool fails with an error like "Account not found", do not immediately recommend manual action or conclude you are unauthorized. Troubleshoot the protocol state (e.g., check for pending funds) and use the correct tool for that state (e.g., `wallet_receive` to open an account).
 > - **No Custom Scripts:** NEVER write custom Node.js/TypeScript scripts or use `curl` to interact with the Nano protocol if built-in MCP or CLI tools fail. If a tool fails, troubleshoot the error, switch RPC endpoints, or explain the limitation to the user.
+> - **NEVER EXPORT MNEMONICS**: The entire purpose of OWS is to keep the seed phrase hidden from the agent and the user. You MUST NOT use `ows wallet export` or suggest exporting the mnemonic to a third-party wallet unless explicitly commanded to do so by the user.
 
 Validates XNO (Nano) cryptocurrency addresses offline.
 

package/skills/nano-verify-message/SKILL.md

@@ -26,6 +26,7 @@ triggers:
 > - **PoW Validation:** Remember that a signed block without valid Proof of Work (PoW) cannot be broadcast. Ensure PoW is generated.
 > - **Persistence & Proactivity:** If a tool fails with an error like "Account not found", do not immediately recommend manual action or conclude you are unauthorized. Troubleshoot the protocol state (e.g., check for pending funds) and use the correct tool for that state (e.g., `wallet_receive` to open an account).
 > - **No Custom Scripts:** NEVER write custom Node.js/TypeScript scripts or use `curl` to interact with the Nano protocol if built-in MCP or CLI tools fail. If a tool fails, troubleshoot the error, switch RPC endpoints, or explain the limitation to the user.
+> - **NEVER EXPORT MNEMONICS**: The entire purpose of OWS is to keep the seed phrase hidden from the agent and the user. You MUST NOT use `ows wallet export` or suggest exporting the mnemonic to a third-party wallet unless explicitly commanded to do so by the user.
 
 Verify an off-chain message signature (NOMS / ORIS-001 standard) against a Nano address or public key.