@oriro/orirocli 0.1.9 → 0.1.11

package/skills/model-usage/scripts/test_model_usage.py

@@ -1,40 +1,40 @@
-#!/usr/bin/env python3
-"""
-Tests for model_usage helpers.
-"""
-
-import argparse
-from datetime import date, timedelta
-from unittest import TestCase, main
-
-from model_usage import filter_by_days, positive_int
-
-
-class TestModelUsage(TestCase):
-    def test_positive_int_accepts_valid_numbers(self):
-        self.assertEqual(positive_int("1"), 1)
-        self.assertEqual(positive_int("7"), 7)
-
-    def test_positive_int_rejects_zero_and_negative(self):
-        with self.assertRaises(argparse.ArgumentTypeError):
-            positive_int("0")
-        with self.assertRaises(argparse.ArgumentTypeError):
-            positive_int("-3")
-
-    def test_filter_by_days_keeps_recent_entries(self):
-        today = date.today()
-        entries = [
-            {"date": (today - timedelta(days=5)).strftime("%Y-%m-%d"), "modelBreakdowns": []},
-            {"date": (today - timedelta(days=1)).strftime("%Y-%m-%d"), "modelBreakdowns": []},
-            {"date": today.strftime("%Y-%m-%d"), "modelBreakdowns": []},
-        ]
-
-        filtered = filter_by_days(entries, 2)
-
-        self.assertEqual(len(filtered), 2)
-        self.assertEqual(filtered[0]["date"], (today - timedelta(days=1)).strftime("%Y-%m-%d"))
-        self.assertEqual(filtered[1]["date"], today.strftime("%Y-%m-%d"))
-
-
-if __name__ == "__main__":
-    main()
+#!/usr/bin/env python3
+"""
+Tests for model_usage helpers.
+"""
+
+import argparse
+from datetime import date, timedelta
+from unittest import TestCase, main
+
+from model_usage import filter_by_days, positive_int
+
+
+class TestModelUsage(TestCase):
+    def test_positive_int_accepts_valid_numbers(self):
+        self.assertEqual(positive_int("1"), 1)
+        self.assertEqual(positive_int("7"), 7)
+
+    def test_positive_int_rejects_zero_and_negative(self):
+        with self.assertRaises(argparse.ArgumentTypeError):
+            positive_int("0")
+        with self.assertRaises(argparse.ArgumentTypeError):
+            positive_int("-3")
+
+    def test_filter_by_days_keeps_recent_entries(self):
+        today = date.today()
+        entries = [
+            {"date": (today - timedelta(days=5)).strftime("%Y-%m-%d"), "modelBreakdowns": []},
+            {"date": (today - timedelta(days=1)).strftime("%Y-%m-%d"), "modelBreakdowns": []},
+            {"date": today.strftime("%Y-%m-%d"), "modelBreakdowns": []},
+        ]
+
+        filtered = filter_by_days(entries, 2)
+
+        self.assertEqual(len(filtered), 2)
+        self.assertEqual(filtered[0]["date"], (today - timedelta(days=1)).strftime("%Y-%m-%d"))
+        self.assertEqual(filtered[1]["date"], today.strftime("%Y-%m-%d"))
+
+
+if __name__ == "__main__":
+    main()

package/skills/nano-pdf/SKILL.md

@@ -1,42 +1,42 @@
----
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-watermark: ORIRO
-disable-model-invocation: true
-name: nano-pdf
-description: "Edit PDFs with natural-language instructions using the nano-pdf CLI."
-homepage: https://pypi.org/project/nano-pdf/
-metadata:
-  {
-    "oriro":
-      {
-        "emoji": "📄",
-        "requires": { "bins": ["nano-pdf"] },
-        "install":
-          [
-            {
-              "id": "uv",
-              "kind": "uv",
-              "package": "nano-pdf",
-              "bins": ["nano-pdf"],
-              "label": "Install nano-pdf (uv)",
-            },
-          ],
-      },
-  }
----
-
-# nano-pdf
-
-Use `nano-pdf` to apply edits to a specific page in a PDF using a natural-language instruction.
-
-## Quick start
-
-```bash
-nano-pdf edit deck.pdf 1 "Change the title to 'Q3 Results' and fix the typo in the subtitle"
-```
-
-Notes:
-
-- Page numbers are 0-based or 1-based depending on the tool's version/config; if the result looks off by one, retry with the other.
-- Always sanity-check the output PDF before sending it out.
+---
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+watermark: ORIRO
+disable-model-invocation: true
+name: nano-pdf
+description: "Edit PDFs with natural-language instructions using the nano-pdf CLI."
+homepage: https://pypi.org/project/nano-pdf/
+metadata:
+  {
+    "oriro":
+      {
+        "emoji": "📄",
+        "requires": { "bins": ["nano-pdf"] },
+        "install":
+          [
+            {
+              "id": "uv",
+              "kind": "uv",
+              "package": "nano-pdf",
+              "bins": ["nano-pdf"],
+              "label": "Install nano-pdf (uv)",
+            },
+          ],
+      },
+  }
+---
+
+# nano-pdf
+
+Use `nano-pdf` to apply edits to a specific page in a PDF using a natural-language instruction.
+
+## Quick start
+
+```bash
+nano-pdf edit deck.pdf 1 "Change the title to 'Q3 Results' and fix the typo in the subtitle"
+```
+
+Notes:
+
+- Page numbers are 0-based or 1-based depending on the tool's version/config; if the result looks off by one, retry with the other.
+- Always sanity-check the output PDF before sending it out.

package/skills/node-connect/SKILL.md

@@ -1,147 +1,147 @@
----
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-watermark: ORIRO
-disable-model-invocation: true
-name: node-connect
-description: "Diagnose ORIRO Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures."
----
-
-# Node Connect
-
-Goal: find the one real route from node -> gateway, verify Oriro is advertising that route, then fix pairing/auth.
-
-## Topology first
-
-Decide which case you are in before proposing fixes:
-
-- same machine / emulator / USB tunnel
-- same LAN / local Wi-Fi
-- same Tailscale tailnet
-- public URL / reverse proxy
-
-Do not mix them.
-
-- Local Wi-Fi problem: do not switch to Tailscale unless remote access is actually needed.
-- VPS / remote gateway problem: do not keep debugging `localhost` or LAN IPs.
-
-## If ambiguous, ask first
-
-If the setup is unclear or the failure report is vague, ask short clarifying questions before diagnosing.
-
-Ask for:
-
-- which route they intend: same machine, same LAN, Tailscale tailnet, or public URL
-- whether they used QR/setup code or manual host/port
-- the exact app text/status/error, quoted exactly if possible
-- whether `oriro devices list` shows a pending pairing request
-
-Do not guess from `can't connect`.
-
-## Canonical checks
-
-Prefer `oriro qr --json`. It uses the same setup-code payload Android scans.
-
-```bash
-oriro config get gateway.mode
-oriro config get gateway.bind
-oriro config get gateway.tailscale.mode
-oriro config get gateway.remote.url
-oriro config get gateway.auth.mode
-oriro config get gateway.auth.allowTailscale
-oriro config get plugins.entries.device-pair.config.publicUrl
-oriro qr --json
-oriro devices list
-oriro nodes status
-```
-
-If this Oriro instance is pointed at a remote gateway, also run:
-
-```bash
-oriro qr --remote --json
-```
-
-If Tailscale is part of the story:
-
-```bash
-tailscale status --json
-```
-
-## Read the result, not guesses
-
-`oriro qr --json` success means:
-
-- `gatewayUrl`: this is the actual endpoint the app should use.
-- `urlSource`: this tells you which config path won.
-
-Common good sources:
-
-- `gateway.bind=lan`: same Wi-Fi / LAN only
-- `gateway.bind=tailnet`: direct tailnet access
-- `gateway.tailscale.mode=serve` or `gateway.tailscale.mode=funnel`: Tailscale route
-- `plugins.entries.device-pair.config.publicUrl`: explicit public/reverse-proxy route
-- `gateway.remote.url`: remote gateway route
-
-## Root-cause map
-
-If `oriro qr --json` says `Gateway is only bound to loopback`:
-
-- remote node cannot connect yet
-- fix the route, then generate a fresh setup code
-- `gateway.bind=auto` is not enough if the effective QR route is still loopback
-- same LAN: use `gateway.bind=lan`
-- same tailnet: prefer `gateway.tailscale.mode=serve` or use `gateway.bind=tailnet`
-- public internet: set a real `plugins.entries.device-pair.config.publicUrl` or `gateway.remote.url`
-
-If `gateway.bind=tailnet set, but no tailnet IP was found`:
-
-- gateway host is not actually on Tailscale
-
-If `qr --remote requires gateway.remote.url`:
-
-- remote-mode config is incomplete
-
-If the app says `pairing required`:
-
-- network route and auth worked
-- approve the pending device
-
-```bash
-oriro devices list
-oriro devices approve --latest   # preview only; copy the requestId from output
-oriro devices approve <requestId>
-```
-
-If the app says `bootstrap token invalid or expired`:
-
-- old setup code
-- generate a fresh one and rescan
-- do this after any URL/auth fix too
-
-If the app says `unauthorized`:
-
-- wrong token/password, or wrong Tailscale expectation
-- for Tailscale Serve, `gateway.auth.allowTailscale` must match the intended flow
-- otherwise use explicit token/password
-
-## Fast heuristics
-
-- Same Wi-Fi setup + gateway advertises `127.0.0.1`, `localhost`, or loopback-only config: wrong.
-- Remote setup + setup/manual uses private LAN IP: wrong.
-- Tailnet setup + gateway advertises LAN IP instead of MagicDNS / tailnet route: wrong.
-- Public URL set but QR still advertises something else: inspect `urlSource`; config is not what you think.
-- `oriro devices list` shows pending requests: stop changing network config and approve first.
-
-## Fix style
-
-Reply with one concrete diagnosis and one route.
-
-If there is not enough signal yet, ask for setup + exact app text instead of guessing.
-
-Good:
-
-- `The gateway is still loopback-only, so a node on another network can never reach it. Enable Tailscale Serve, restart the gateway, run oriro qr again, rescan, then approve the pending device pairing.`
-
-Bad:
-
-- `Maybe LAN, maybe Tailscale, maybe port forwarding, maybe public URL.`
+---
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+watermark: ORIRO
+disable-model-invocation: true
+name: node-connect
+description: "Diagnose ORIRO Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures."
+---
+
+# Node Connect
+
+Goal: find the one real route from node -> gateway, verify Oriro is advertising that route, then fix pairing/auth.
+
+## Topology first
+
+Decide which case you are in before proposing fixes:
+
+- same machine / emulator / USB tunnel
+- same LAN / local Wi-Fi
+- same Tailscale tailnet
+- public URL / reverse proxy
+
+Do not mix them.
+
+- Local Wi-Fi problem: do not switch to Tailscale unless remote access is actually needed.
+- VPS / remote gateway problem: do not keep debugging `localhost` or LAN IPs.
+
+## If ambiguous, ask first
+
+If the setup is unclear or the failure report is vague, ask short clarifying questions before diagnosing.
+
+Ask for:
+
+- which route they intend: same machine, same LAN, Tailscale tailnet, or public URL
+- whether they used QR/setup code or manual host/port
+- the exact app text/status/error, quoted exactly if possible
+- whether `oriro devices list` shows a pending pairing request
+
+Do not guess from `can't connect`.
+
+## Canonical checks
+
+Prefer `oriro qr --json`. It uses the same setup-code payload Android scans.
+
+```bash
+oriro config get gateway.mode
+oriro config get gateway.bind
+oriro config get gateway.tailscale.mode
+oriro config get gateway.remote.url
+oriro config get gateway.auth.mode
+oriro config get gateway.auth.allowTailscale
+oriro config get plugins.entries.device-pair.config.publicUrl
+oriro qr --json
+oriro devices list
+oriro nodes status
+```
+
+If this Oriro instance is pointed at a remote gateway, also run:
+
+```bash
+oriro qr --remote --json
+```
+
+If Tailscale is part of the story:
+
+```bash
+tailscale status --json
+```
+
+## Read the result, not guesses
+
+`oriro qr --json` success means:
+
+- `gatewayUrl`: this is the actual endpoint the app should use.
+- `urlSource`: this tells you which config path won.
+
+Common good sources:
+
+- `gateway.bind=lan`: same Wi-Fi / LAN only
+- `gateway.bind=tailnet`: direct tailnet access
+- `gateway.tailscale.mode=serve` or `gateway.tailscale.mode=funnel`: Tailscale route
+- `plugins.entries.device-pair.config.publicUrl`: explicit public/reverse-proxy route
+- `gateway.remote.url`: remote gateway route
+
+## Root-cause map
+
+If `oriro qr --json` says `Gateway is only bound to loopback`:
+
+- remote node cannot connect yet
+- fix the route, then generate a fresh setup code
+- `gateway.bind=auto` is not enough if the effective QR route is still loopback
+- same LAN: use `gateway.bind=lan`
+- same tailnet: prefer `gateway.tailscale.mode=serve` or use `gateway.bind=tailnet`
+- public internet: set a real `plugins.entries.device-pair.config.publicUrl` or `gateway.remote.url`
+
+If `gateway.bind=tailnet set, but no tailnet IP was found`:
+
+- gateway host is not actually on Tailscale
+
+If `qr --remote requires gateway.remote.url`:
+
+- remote-mode config is incomplete
+
+If the app says `pairing required`:
+
+- network route and auth worked
+- approve the pending device
+
+```bash
+oriro devices list
+oriro devices approve --latest   # preview only; copy the requestId from output
+oriro devices approve <requestId>
+```
+
+If the app says `bootstrap token invalid or expired`:
+
+- old setup code
+- generate a fresh one and rescan
+- do this after any URL/auth fix too
+
+If the app says `unauthorized`:
+
+- wrong token/password, or wrong Tailscale expectation
+- for Tailscale Serve, `gateway.auth.allowTailscale` must match the intended flow
+- otherwise use explicit token/password
+
+## Fast heuristics
+
+- Same Wi-Fi setup + gateway advertises `127.0.0.1`, `localhost`, or loopback-only config: wrong.
+- Remote setup + setup/manual uses private LAN IP: wrong.
+- Tailnet setup + gateway advertises LAN IP instead of MagicDNS / tailnet route: wrong.
+- Public URL set but QR still advertises something else: inspect `urlSource`; config is not what you think.
+- `oriro devices list` shows pending requests: stop changing network config and approve first.
+
+## Fix style
+
+Reply with one concrete diagnosis and one route.
+
+If there is not enough signal yet, ask for setup + exact app text instead of guessing.
+
+Good:
+
+- `The gateway is still loopback-only, so a node on another network can never reach it. Enable Tailscale Serve, restart the gateway, run oriro qr again, rescan, then approve the pending device pairing.`
+
+Bad:
+
+- `Maybe LAN, maybe Tailscale, maybe port forwarding, maybe public URL.`

package/skills/node-inspect-debugger/SKILL.md

@@ -1,88 +1,88 @@
----
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-watermark: ORIRO
-name: node-inspect-debugger
-description: Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.
-metadata: { "oriro": { "emoji": "🪲", "requires": { "bins": ["node"] } } }
----
-
-# Node Inspect Debugger
-
-Use for Node.js debugging that needs inspector access: hidden locals, async hangs, flaky tests, child processes, startup races, memory growth, or CPU hot paths.
-
-Default to `node inspect` first. Use Chrome DevTools Protocol only when you need scripted breakpoints, automated state capture, heap snapshots, or CPU profiles.
-
-Quick start
-
-- Pause on entry: `node inspect path/to/script.js`
-- TypeScript: `node --inspect-brk --import tsx path/to/script.ts`
-- Existing PID: `kill -SIGUSR1 <pid>` then `node inspect -p <pid>`
-- Inspect target list: `curl -s http://127.0.0.1:9229/json/list | jq`
-- Oriro CLI path: `node --inspect-brk oriro.mjs ...`
-- Oriro test path: `ORIRO_VITEST_MAX_WORKERS=1 node --inspect-brk scripts/run-vitest.mjs <file>`
-
-Debugger REPL
-
-- Continue/step: `cont`, `next`, `step`, `out`, `pause`
-- Breakpoints: `sb('file.js', 42)`, `sb(42)`, `sb('functionName')`, `breakpoints`, `cb('file.js', 42)`
-- Inspect: `bt`, `list(8)`, `watch('expr')`, `exec expr`
-- Current scope: `repl`, then evaluate locals directly; `Ctrl+C` exits repl mode.
-- Exit safely: `cont` before quitting if the process should continue; otherwise `kill`.
-
-Oriro tips
-
-- Prefer `127.0.0.1` inspector binds. Do not expose `--inspect=0.0.0.0` unless the network is isolated.
-- For Vitest, debug one file with one worker. Avoid worker pools while stepping.
-- For TS source breakpoints, use `--enable-source-maps` when useful; `node inspect` can still show emitted paths.
-- For child processes, `NODE_OPTIONS=--inspect-brk` can propagate the inspector, but each child needs its own port.
-- For long-lived gateway or dev processes, attach by PID after confirming the target with `/json/list`.
-
-Programmatic CDP
-
-Install tooling outside the repo unless the project already depends on it:
-
-```bash
-mkdir -p /tmp/cdp-tools
-npm --prefix /tmp/cdp-tools i chrome-remote-interface
-NODE_PATH=/tmp/cdp-tools/node_modules node /tmp/cdp-debug.cjs
-```
-
-Minimal driver:
-
-```js
-const CDP = require("chrome-remote-interface");
-
-(async () => {
-  const client = await CDP({ port: 9229 });
-  const { Debugger, Runtime } = client;
-
-  Debugger.paused(async ({ callFrames, reason }) => {
-    const top = callFrames[0];
-    console.log("paused", reason, top.url, top.location.lineNumber + 1);
-    const { result } = await Debugger.evaluateOnCallFrame({
-      callFrameId: top.callFrameId,
-      expression: "JSON.stringify({ pid: process.pid })",
-    });
-    console.log(result.value ?? result.description);
-    await Debugger.resume();
-  });
-
-  await Runtime.enable();
-  await Debugger.enable();
-  await Debugger.setBreakpointByUrl({ urlRegex: ".*target\\.js$", lineNumber: 41 });
-  await Runtime.runIfWaitingForDebugger();
-})();
-```
-
-Profiles
-
-- CPU: enable `Profiler`, `start`, wait, `stop`, write `/tmp/profile.cpuprofile`, open in Chrome DevTools.
-- Heap: enable `HeapProfiler`, collect `addHeapSnapshotChunk`, call `takeHeapSnapshot`, write `/tmp/heap.heapsnapshot`.
-
-Pitfalls
-
-- `--inspect` does not pause; use `--inspect-brk` when setup must happen before code runs.
-- Default port is `9229`; use `--inspect=0` or a unique port for parallel targets.
-- If a breakpoint misses, confirm file path, source map behavior, and whether execution already passed the line.
-- If the process appears frozen after detaching, it may still be paused in the debugger.
+---
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+watermark: ORIRO
+name: node-inspect-debugger
+description: Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.
+metadata: { "oriro": { "emoji": "🪲", "requires": { "bins": ["node"] } } }
+---
+
+# Node Inspect Debugger
+
+Use for Node.js debugging that needs inspector access: hidden locals, async hangs, flaky tests, child processes, startup races, memory growth, or CPU hot paths.
+
+Default to `node inspect` first. Use Chrome DevTools Protocol only when you need scripted breakpoints, automated state capture, heap snapshots, or CPU profiles.
+
+Quick start
+
+- Pause on entry: `node inspect path/to/script.js`
+- TypeScript: `node --inspect-brk --import tsx path/to/script.ts`
+- Existing PID: `kill -SIGUSR1 <pid>` then `node inspect -p <pid>`
+- Inspect target list: `curl -s http://127.0.0.1:9229/json/list | jq`
+- Oriro CLI path: `node --inspect-brk oriro.mjs ...`
+- Oriro test path: `ORIRO_VITEST_MAX_WORKERS=1 node --inspect-brk scripts/run-vitest.mjs <file>`
+
+Debugger REPL
+
+- Continue/step: `cont`, `next`, `step`, `out`, `pause`
+- Breakpoints: `sb('file.js', 42)`, `sb(42)`, `sb('functionName')`, `breakpoints`, `cb('file.js', 42)`
+- Inspect: `bt`, `list(8)`, `watch('expr')`, `exec expr`
+- Current scope: `repl`, then evaluate locals directly; `Ctrl+C` exits repl mode.
+- Exit safely: `cont` before quitting if the process should continue; otherwise `kill`.
+
+Oriro tips
+
+- Prefer `127.0.0.1` inspector binds. Do not expose `--inspect=0.0.0.0` unless the network is isolated.
+- For Vitest, debug one file with one worker. Avoid worker pools while stepping.
+- For TS source breakpoints, use `--enable-source-maps` when useful; `node inspect` can still show emitted paths.
+- For child processes, `NODE_OPTIONS=--inspect-brk` can propagate the inspector, but each child needs its own port.
+- For long-lived gateway or dev processes, attach by PID after confirming the target with `/json/list`.
+
+Programmatic CDP
+
+Install tooling outside the repo unless the project already depends on it:
+
+```bash
+mkdir -p /tmp/cdp-tools
+npm --prefix /tmp/cdp-tools i chrome-remote-interface
+NODE_PATH=/tmp/cdp-tools/node_modules node /tmp/cdp-debug.cjs
+```
+
+Minimal driver:
+
+```js
+const CDP = require("chrome-remote-interface");
+
+(async () => {
+  const client = await CDP({ port: 9229 });
+  const { Debugger, Runtime } = client;
+
+  Debugger.paused(async ({ callFrames, reason }) => {
+    const top = callFrames[0];
+    console.log("paused", reason, top.url, top.location.lineNumber + 1);
+    const { result } = await Debugger.evaluateOnCallFrame({
+      callFrameId: top.callFrameId,
+      expression: "JSON.stringify({ pid: process.pid })",
+    });
+    console.log(result.value ?? result.description);
+    await Debugger.resume();
+  });
+
+  await Runtime.enable();
+  await Debugger.enable();
+  await Debugger.setBreakpointByUrl({ urlRegex: ".*target\\.js$", lineNumber: 41 });
+  await Runtime.runIfWaitingForDebugger();
+})();
+```
+
+Profiles
+
+- CPU: enable `Profiler`, `start`, wait, `stop`, write `/tmp/profile.cpuprofile`, open in Chrome DevTools.
+- Heap: enable `HeapProfiler`, collect `addHeapSnapshotChunk`, call `takeHeapSnapshot`, write `/tmp/heap.heapsnapshot`.
+
+Pitfalls
+
+- `--inspect` does not pause; use `--inspect-brk` when setup must happen before code runs.
+- Default port is `9229`; use `--inspect=0` or a unique port for parallel targets.
+- If a breakpoint misses, confirm file path, source map behavior, and whether execution already passed the line.
+- If the process appears frozen after detaching, it may still be paused in the debugger.