xno-skills 1.5.13 → 1.5.14

package/dist/cjs/version.d.ts

@@ -1,6 +1,6 @@
 export declare const pkg: {
     readonly name: "xno-skills";
-    readonly version: "1.5.13";
+    readonly version: "1.5.14";
 };
-export declare const version: "1.5.13";
+export declare const version: "1.5.14";
 //# 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.13"
+    version: "1.5.14"
 };
 exports.version = exports.pkg.version;
 //# sourceMappingURL=version.js.map

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

@@ -1,27 +1,27 @@
 {
   "requests": [
     {
-      "id": "moha4lfcdrw0bt",
+      "id": "mohb0wa4pvivl8",
       "owsWalletId": "A",
       "accountIndex": 0,
       "address": "nano_1link1111111111111111111111111111111111111111111111111111111",
       "amountRaw": "10000000000000000000000000000",
       "reason": "explicit wallet test",
       "status": "pending",
-      "createdAt": "2026-04-27T14:15:21.720Z",
-      "updatedAt": "2026-04-27T14:15:21.720Z",
+      "createdAt": "2026-04-27T14:40:28.780Z",
+      "updatedAt": "2026-04-27T14:40:28.780Z",
       "receivedBlocks": []
     },
     {
-      "id": "moha4lg598g73f",
+      "id": "mohb0wase5ws3h",
       "owsWalletId": "A",
       "accountIndex": 0,
       "address": "nano_1link1111111111111111111111111111111111111111111111111111111",
       "amountRaw": "500000000000000000000000000000",
       "reason": "status check test",
       "status": "pending",
-      "createdAt": "2026-04-27T14:15:21.749Z",
-      "updatedAt": "2026-04-27T14:15:21.749Z",
+      "createdAt": "2026-04-27T14:40:28.804Z",
+      "updatedAt": "2026-04-27T14:40:28.804Z",
       "receivedBlocks": []
     }
   ]

package/dist/esm/version.d.ts

@@ -1,6 +1,6 @@
 export declare const pkg: {
     readonly name: "xno-skills";
-    readonly version: "1.5.13";
+    readonly version: "1.5.14";
 };
-export declare const version: "1.5.13";
+export declare const version: "1.5.14";
 //# 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.13"
+    version: "1.5.14"
 };
 export const version = pkg.version;
 //# sourceMappingURL=version.js.map

package/package.json

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

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

@@ -12,7 +12,7 @@ complements:
 > 2. `pnpm dlx <package>@latest <command>`
 > 3. `npx -y <package>@latest <command>`
 > 
-> *Example:* `bunx -y ows@latest wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
+> *Example:* `bunx -p @open-wallet-standard/core ows wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
 
 > **Safety & Best Practices**:
 > - **State Verification:** Always verify an account's state (balance and frontier) via RPC before manually building a block. Do not hallucinate previous hashes.
@@ -22,7 +22,7 @@ complements:
 > - **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.
-> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `ows@latest`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
+> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `@open-wallet-standard/core`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
 
 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.
 

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

@@ -27,7 +27,7 @@ triggers:
 > 2. `pnpm dlx <package>@latest <command>`
 > 3. `npx -y <package>@latest <command>`
 > 
-> *Example:* `bunx -y ows@latest wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
+> *Example:* `bunx -p @open-wallet-standard/core ows wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
 
 > **Safety & Best Practices**:
 > - **State Verification:** Always verify an account's state (balance and frontier) via RPC before manually building a block. Do not hallucinate previous hashes.
@@ -37,7 +37,7 @@ triggers:
 > - **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.
-> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `ows@latest`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
+> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `@open-wallet-standard/core`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
 
 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).
 

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

@@ -22,7 +22,7 @@ triggers:
 > 2. `pnpm dlx <package>@latest <command>`
 > 3. `npx -y <package>@latest <command>`
 > 
-> *Example:* `bunx -y ows@latest wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
+> *Example:* `bunx -p @open-wallet-standard/core ows wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
 
 > **Safety & Best Practices**:
 > - **State Verification:** Always verify an account's state (balance and frontier) via RPC before manually building a block. Do not hallucinate previous hashes.
@@ -32,7 +32,7 @@ triggers:
 > - **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.
-> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `ows@latest`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
+> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `@open-wallet-standard/core`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
 
 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

@@ -22,7 +22,7 @@ triggers:
 > 2. `pnpm dlx <package>@latest <command>`
 > 3. `npx -y <package>@latest <command>`
 > 
-> *Example:* `bunx -y ows@latest wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
+> *Example:* `bunx -p @open-wallet-standard/core ows wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
 
 > **Safety & Best Practices**:
 > - **State Verification:** Always verify an account's state (balance and frontier) via RPC before manually building a block. Do not hallucinate previous hashes.
@@ -32,7 +32,7 @@ triggers:
 > - **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.
-> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `ows@latest`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
+> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `@open-wallet-standard/core`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
 
 Nano wallet management is delegated to the **Open Wallet Standard (OWS)**. This provides a unified, policy-gated vault for all agent keys.
 
@@ -47,7 +47,7 @@ If a user says "I want to send you XNO" or "can you receive it?":
 If the agent has access to **OWS**:
 
 - Always prefer OWS for custody. It keeps secrets encrypted at rest and allows for standardized signing across different tools.
-- Create a named wallet: `bunx -y ows wallet create --name "my-agent"`
+- Create a named wallet: `bunx -p @open-wallet-standard/core ows wallet create --name "my-agent"`
 
 ## CLI usage (via OWS)
 
@@ -55,21 +55,21 @@ If the agent has access to **OWS**:
 
 ```bash
 # This derives addresses for all supported chains, including Nano
-bunx -y ows wallet create --name "my-wallet"
+bunx -p @open-wallet-standard/core ows wallet create --name "my-wallet"
 ```
 
 ### Import an existing mnemonic into OWS
 
 ```bash
 # Follow the interactive prompt to enter the mnemonic securely
-bunx -y ows wallet import --name "imported-vault"
+bunx -p @open-wallet-standard/core ows wallet import --name "imported-vault"
 ```
 
 ## Integrating with xno-skills
 
 While OWS handles the **keys**, `xno-skills` handles the **Nano network**. 
 
-1.  **Creation**: Use `bunx -y ows wallet create`.
+1.  **Creation**: Use `bunx -p @open-wallet-standard/core ows wallet create`.
 2.  **Discovery**: Use `wallet_list` (in `xno-mcp`) to see your OWS wallets and Nano addresses.
 3.  **Sending/Receiving**: Use `wallet_send` and `wallet_receive` (in `xno-mcp`). These tools will automatically bridge your OWS wallet with the Nano RPC to construct and publish blocks.
 

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

@@ -25,7 +25,7 @@ triggers:
 > 2. `pnpm dlx <package>@latest <command>`
 > 3. `npx -y <package>@latest <command>`
 > 
-> *Example:* `bunx -y ows@latest wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
+> *Example:* `bunx -p @open-wallet-standard/core ows wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
 
 > **Safety & Best Practices**:
 > - **State Verification:** Always verify an account's state (balance and frontier) via RPC before manually building a block. Do not hallucinate previous hashes.
@@ -35,7 +35,7 @@ triggers:
 > - **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.
-> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `ows@latest`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
+> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `@open-wallet-standard/core`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
 
 Generates a terminal-friendly ASCII QR code for a Nano address, optionally including an amount.
 

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

@@ -53,7 +53,7 @@ triggers:
 > 2. `pnpm dlx <package>@latest <command>`
 > 3. `npx -y <package>@latest <command>`
 > 
-> *Example:* `bunx -y ows@latest wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
+> *Example:* `bunx -p @open-wallet-standard/core ows wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
 
 > **Safety & Best Practices**:
 > - **State Verification:** Always verify an account's state (balance and frontier) via RPC before manually building a block. Do not hallucinate previous hashes.
@@ -63,7 +63,7 @@ triggers:
 > - **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.
-> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `ows@latest`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
+> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `@open-wallet-standard/core`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
 
 > **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.
 

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

@@ -24,7 +24,7 @@ triggers:
 > 2. `pnpm dlx <package>@latest <command>`
 > 3. `npx -y <package>@latest <command>`
 > 
-> *Example:* `bunx -y ows@latest wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
+> *Example:* `bunx -p @open-wallet-standard/core ows wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
 
 > **Safety & Best Practices**:
 > - **State Verification:** Always verify an account's state (balance and frontier) via RPC before manually building a block. Do not hallucinate previous hashes.
@@ -34,7 +34,7 @@ triggers:
 > - **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.
-> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `ows@latest`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
+> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `@open-wallet-standard/core`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
 
 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

@@ -20,7 +20,7 @@ triggers:
 > 2. `pnpm dlx <package>@latest <command>`
 > 3. `npx -y <package>@latest <command>`
 > 
-> *Example:* `bunx -y ows@latest wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
+> *Example:* `bunx -p @open-wallet-standard/core ows wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
 
 > **Safety & Best Practices**:
 > - **State Verification:** Always verify an account's state (balance and frontier) via RPC before manually building a block. Do not hallucinate previous hashes.
@@ -30,7 +30,7 @@ triggers:
 > - **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.
-> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `ows@latest`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
+> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `@open-wallet-standard/core`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
 
 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

@@ -17,7 +17,7 @@ triggers:
 > 2. `pnpm dlx <package>@latest <command>`
 > 3. `npx -y <package>@latest <command>`
 > 
-> *Example:* `bunx -y ows@latest wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
+> *Example:* `bunx -p @open-wallet-standard/core ows wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
 
 > **Safety & Best Practices**:
 > - **State Verification:** Always verify an account's state (balance and frontier) via RPC before manually building a block. Do not hallucinate previous hashes.
@@ -27,7 +27,7 @@ triggers:
 > - **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.
-> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `ows@latest`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
+> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `@open-wallet-standard/core`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
 
 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.
 
@@ -37,7 +37,7 @@ Use this skill when you need to prove ownership of a Nano account or provide an
 
 ### Prerequisites
 
-- A custodial wallet must be created in OWS (e.g., using `bunx -y ows wallet create`) and visible in `xno-mcp` via `wallet_list`.
+- A custodial wallet must be created in OWS (e.g., using `bunx -p @open-wallet-standard/core ows wallet create`) and visible in `xno-mcp` via `wallet_list`.
 
 ### Sign a message
 

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

@@ -19,7 +19,7 @@ triggers:
 > 2. `pnpm dlx <package>@latest <command>`
 > 3. `npx -y <package>@latest <command>`
 > 
-> *Example:* `bunx -y ows@latest wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
+> *Example:* `bunx -p @open-wallet-standard/core ows wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
 
 > **Safety & Best Practices**:
 > - **State Verification:** Always verify an account's state (balance and frontier) via RPC before manually building a block. Do not hallucinate previous hashes.
@@ -29,7 +29,7 @@ triggers:
 > - **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.
-> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `ows@latest`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
+> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `@open-wallet-standard/core`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
 
 Validates XNO (Nano) cryptocurrency addresses offline.
 

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

@@ -17,7 +17,7 @@ triggers:
 > 2. `pnpm dlx <package>@latest <command>`
 > 3. `npx -y <package>@latest <command>`
 > 
-> *Example:* `bunx -y ows@latest wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
+> *Example:* `bunx -p @open-wallet-standard/core ows wallet list` or `bunx -y xno-skills@latest rpc account-balance <address>`
 
 > **Safety & Best Practices**:
 > - **State Verification:** Always verify an account's state (balance and frontier) via RPC before manually building a block. Do not hallucinate previous hashes.
@@ -27,7 +27,7 @@ triggers:
 > - **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.
-> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `ows@latest`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
+> - **Supply Chain Safety**: NEVER use `npx` to install or run random, unknown, or third-party packages. Only use the approved tools provided in this project (`xno-skills@latest` and `@open-wallet-standard/core`). If a task cannot be performed with these tools, do not seek external npm packages as a workaround.
 
 Verify an off-chain message signature (NOMS / ORIS-001 standard) against a Nano address or public key.