@weavetab/skills 2.5.0 → 2.5.2

package/dist/granular/browser_tab-and-window.md

@@ -1,136 +1,136 @@
----
-id: tab-and-window
-domain: browser
-triggers:
-  - "switch tab"
-  - "open tab"
-  - "close tab"
-  - "list tabs"
-  - "tab crash recovery"
-  - "heal tabs"
-  - "desktop app tabs"
-tools:
-  - "browser_tabs"
-weavetab: ">=2.5.0-beta.5"
----
-
-# Tab & Window Lifecycle Management
-
-Multi-tab workflows (OAuth popups, payment gateways, documentation references, desktop application windows) require deterministic tab switching, window focusing, and failure recovery. `browser_tabs` controls all CDP page and window targets.
-
----
-
-## 1. Tab Discovery & Target Enumeration
-
-Inspect all active targets, open URLs, and page titles:
-
-```json
-{
-  "action": "list"
-}
-```
-
-To list targets inside a specific desktop app (e.g. Discord, Slack):
-```json
-{
-  "action": "list",
-  "app": "discord"
-}
-```
-
-> [!TIP]
-> Always pass `"app": "<name>"` when inspecting desktop applications. This guarantees that Weavetab does not launch or query the web browser.
-
----
-
-## 2. Opening Tabs & Smart Reuse
-
-Open a target URL. By default, `reuse: true` will focus an existing tab if the URL is already loaded:
-
-```json
-{
-  "action": "open",
-  "url": "https://github.com"
-}
-```
-
-To force opening a brand-new duplicate tab instead of reusing:
-```json
-{
-  "action": "open",
-  "url": "https://github.com",
-  "reuse": false
-}
-```
-
----
-
-## 3. Context Switching
-
-Switch active agent focus between open tabs:
-
-```json
-{
-  "action": "switch",
-  "tabId": "TARGET_PAGE_ID"
-}
-```
-
----
-
-## 4. Closing Tabs & Batch Cleanup
-
-Close a single tab:
-```json
-{
-  "action": "close",
-  "tabId": "TARGET_PAGE_ID"
-}
-```
-
-Close multiple tabs simultaneously in a single round-trip:
-```json
-{
-  "action": "close",
-  "tabIds": ["TARGET_1", "TARGET_2", "TARGET_3"]
-}
-```
-
----
-
-## 5. Native Window Management
-
-List native OS windows:
-```json
-{
-  "action": "list_windows"
-}
-```
-
-Bring a specific native window to the foreground:
-```json
-{
-  "action": "focus_window",
-  "windowId": 1
-}
-```
-
----
-
-## 6. Duplicate Consolidation & Auto-Heal
-
-Deduplicate redundant tabs across the session:
-```json
-{
-  "action": "consolidate"
-}
-```
-
-If a target page crashes or detaches due to memory limits:
-```json
-{
-  "action": "heal"
-}
-```
-
-The auto-heal routine re-establishes CDP protocol sessions, reconnects event listeners, and synchronizes the active page target.
+---
+id: tab-and-window
+domain: browser
+triggers:
+  - "switch tab"
+  - "open tab"
+  - "close tab"
+  - "list tabs"
+  - "tab crash recovery"
+  - "heal tabs"
+  - "desktop app tabs"
+tools:
+  - "browser_tabs"
+weavetab: ">=2.5.0"
+---
+
+# Tab & Window Lifecycle Management
+
+Multi-tab workflows (OAuth popups, payment gateways, documentation references, desktop application windows) require deterministic tab switching, window focusing, and failure recovery. `browser_tabs` controls all CDP page and window targets.
+
+---
+
+## 1. Tab Discovery & Target Enumeration
+
+Inspect all active targets, open URLs, and page titles:
+
+```json
+{
+  "action": "list"
+}
+```
+
+To list targets inside a specific desktop app (e.g. Discord, Slack):
+```json
+{
+  "action": "list",
+  "app": "discord"
+}
+```
+
+> [!TIP]
+> Always pass `"app": "<name>"` when inspecting desktop applications. This guarantees that Weavetab does not launch or query the web browser.
+
+---
+
+## 2. Opening Tabs & Smart Reuse
+
+Open a target URL. By default, `reuse: true` will focus an existing tab if the URL is already loaded:
+
+```json
+{
+  "action": "open",
+  "url": "https://github.com"
+}
+```
+
+To force opening a brand-new duplicate tab instead of reusing:
+```json
+{
+  "action": "open",
+  "url": "https://github.com",
+  "reuse": false
+}
+```
+
+---
+
+## 3. Context Switching
+
+Switch active agent focus between open tabs:
+
+```json
+{
+  "action": "switch",
+  "tabId": "TARGET_PAGE_ID"
+}
+```
+
+---
+
+## 4. Closing Tabs & Batch Cleanup
+
+Close a single tab:
+```json
+{
+  "action": "close",
+  "tabId": "TARGET_PAGE_ID"
+}
+```
+
+Close multiple tabs simultaneously in a single round-trip:
+```json
+{
+  "action": "close",
+  "tabIds": ["TARGET_1", "TARGET_2", "TARGET_3"]
+}
+```
+
+---
+
+## 5. Native Window Management
+
+List native OS windows:
+```json
+{
+  "action": "list_windows"
+}
+```
+
+Bring a specific native window to the foreground:
+```json
+{
+  "action": "focus_window",
+  "windowId": 1
+}
+```
+
+---
+
+## 6. Duplicate Consolidation & Auto-Heal
+
+Deduplicate redundant tabs across the session:
+```json
+{
+  "action": "consolidate"
+}
+```
+
+If a target page crashes or detaches due to memory limits:
+```json
+{
+  "action": "heal"
+}
+```
+
+The auto-heal routine re-establishes CDP protocol sessions, reconnects event listeners, and synchronizes the active page target.

package/dist/granular/desktop_desktop-targeting.md

@@ -1,85 +1,85 @@
----
-id: desktop-targeting
-domain: desktop
-triggers:
-  - "automate desktop app"
-  - "send message in slack"
-  - "edit in vscode"
-  - "switch to discord"
-  - "desktop app routing"
-tools:
-  - "browser_map"
-  - "browser_click"
-  - "browser_type"
-  - "browser_fill"
-  - "browser_detect"
-  - "browser_tabs"
-  - "browser_navigate"
-weavetab: ">=2.5.0-beta.5"
----
-
-# Desktop App Targeting & Multi-Window Routing
-
-Once a desktop application is detected via `browser_detect`, every standard Weavetab tool can be scoped directly to that desktop application without opening or disturbing the user's web browser.
-
----
-
-## 1. Direct App Parameter Routing
-
-Pass `"app": "<application_name>"` to target the Electron application.
-
-### Example: Reading Discord Channels
-```json
-// Tool: browser_map
-{
-  "app": "discord",
-  "scope": "main_content"
-}
-```
-
-### Example: Sending a Message in Discord
-```json
-// Tool: browser_type
-{
-  "app": "discord",
-  "ref": "w:88",
-  "text": "Deployment v2.5.0-beta.3 completed successfully."
-}
-```
-
-### Example: Listing Discord Tabs/Windows
-```json
-// Tool: browser_tabs
-{
-  "action": "list",
-  "app": "discord"
-}
-```
-
-> [!IMPORTANT]
-> Always pass `"app": "discord"` (or the target app name) to `browser_tabs` when working with desktop apps. This prevents Weavetab from accidentally launching or switching to the web browser.
-
----
-
-## 2. Smart Domain Auto-Routing & Sticky Context
-
-Weavetab features automatic target resolution to eliminate accidental browser popups:
-
-### A. Automatic Domain Matching
-If you call `browser_navigate` or `browser_tabs(action: "open")` with a known domain (e.g. `discord.com`, `slack.com`, `linear.app`, `notion.so`), Weavetab automatically routes the command to the configured Electron desktop application.
-
-### B. Sticky App Sessions
-When you interact with an Electron application (e.g., clicking or typing in Discord), Weavetab remembers the active application context. If a subsequent tool call omits `app` and no web browser instance is active, Weavetab stays attached to the active desktop app rather than spawning an unwanted Chrome window.
-
-### C. Explicit Browser Override
-If you specifically want to open a URL in the web browser instead of a desktop application, pass `"app": "browser"`.
-
----
-
-## 3. Multi-Window Focus Management
-
-Some Electron apps open secondary windows (e.g. popout editors, settings panels, or call windows).
-
-1. Use `browser_tabs(action: "list", app: "discord")` to view all open windows and page targets for that specific app.
-2. Switch focus between windows using `browser_tabs(action: "switch", tabId: "<id>", app: "discord")`.
-3. To bring a specific native window to the foreground, use `browser_tabs(action: "focus_window", windowId: <id>, app: "discord")`.
+---
+id: desktop-targeting
+domain: desktop
+triggers:
+  - "automate desktop app"
+  - "send message in slack"
+  - "edit in vscode"
+  - "switch to discord"
+  - "desktop app routing"
+tools:
+  - "browser_map"
+  - "browser_click"
+  - "browser_type"
+  - "browser_fill"
+  - "browser_detect"
+  - "browser_tabs"
+  - "browser_navigate"
+weavetab: ">=2.5.0"
+---
+
+# Desktop App Targeting & Multi-Window Routing
+
+Once a desktop application is detected via `browser_detect`, every standard Weavetab tool can be scoped directly to that desktop application without opening or disturbing the user's web browser.
+
+---
+
+## 1. Direct App Parameter Routing
+
+Pass `"app": "<application_name>"` to target the Electron application.
+
+### Example: Reading Discord Channels
+```json
+// Tool: browser_map
+{
+  "app": "discord",
+  "scope": "main_content"
+}
+```
+
+### Example: Sending a Message in Discord
+```json
+// Tool: browser_type
+{
+  "app": "discord",
+  "ref": "w:88",
+  "text": "Deployment v2.5.2 completed successfully."
+}
+```
+
+### Example: Listing Discord Tabs/Windows
+```json
+// Tool: browser_tabs
+{
+  "action": "list",
+  "app": "discord"
+}
+```
+
+> [!IMPORTANT]
+> Always pass `"app": "discord"` (or the target app name) to `browser_tabs` when working with desktop apps. This prevents Weavetab from accidentally launching or switching to the web browser.
+
+---
+
+## 2. Smart Domain Auto-Routing & Sticky Context
+
+Weavetab features automatic target resolution to eliminate accidental browser popups:
+
+### A. Automatic Domain Matching
+If you call `browser_navigate` or `browser_tabs(action: "open")` with a known domain (e.g. `discord.com`, `slack.com`, `linear.app`, `notion.so`), Weavetab automatically routes the command to the configured Electron desktop application.
+
+### B. Sticky App Sessions
+When you interact with an Electron application (e.g., clicking or typing in Discord), Weavetab remembers the active application context. If a subsequent tool call omits `app` and no web browser instance is active, Weavetab stays attached to the active desktop app rather than spawning an unwanted Chrome window.
+
+### C. Explicit Browser Override
+If you specifically want to open a URL in the web browser instead of a desktop application, pass `"app": "browser"`.
+
+---
+
+## 3. Multi-Window Focus Management
+
+Some Electron apps open secondary windows (e.g. popout editors, settings panels, or call windows).
+
+1. Use `browser_tabs(action: "list", app: "discord")` to view all open windows and page targets for that specific app.
+2. Switch focus between windows using `browser_tabs(action: "switch", tabId: "<id>", app: "discord")`.
+3. To bring a specific native window to the foreground, use `browser_tabs(action: "focus_window", windowId: <id>, app: "discord")`.

package/dist/granular/desktop_electron-discovery.md

@@ -1,115 +1,115 @@
----
-id: electron-discovery
-domain: desktop
-triggers:
-  - "discover electron apps"
-  - "detect desktop apps"
-  - "connect to slack"
-  - "connect to discord"
-  - "connect to vscode"
-  - "electron automation"
-tools:
-  - "browser_detect"
-weavetab: ">=2.5.0-beta.5"
----
-
-# Electron Discovery & Environment Handshake
-
-Modern desktop applications (Discord, Slack, VS Code, Notion, Obsidian, Figma) are built on Chromium and Electron. Weavetab can inspect and drive these native applications through standard CDP interfaces without third-party drivers or OS-level accessibility hacks.
-
-`browser_detect` is the **critical initialization handshake** tool. Every agent should call `browser_detect` before interacting with the user's desktop environment to gain immediate situational awareness.
-
----
-
-## 1. Running Discovery via `browser_detect`
-
-Call `browser_detect` with empty parameters `{}`:
-
-```json
-{}
-```
-
-### Response Schema:
-```json
-{
-  "available": [
-    {
-      "engine": "chromium",
-      "name": "Google Chrome",
-      "path": "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe"
-    }
-  ],
-  "current": "chromium",
-  "configuredApps": [
-    {
-      "name": "discord",
-      "status": "running_no_debug",
-      "configuredPath": "C:\\Users\\username\\AppData\\Local\\Discord\\app-1.0.9256\\Discord.exe"
-    },
-    {
-      "name": "slack",
-      "status": "connected",
-      "port": 9222,
-      "configuredPath": "C:\\Users\\username\\AppData\\Local\\slack\\app-4.38.125\\slack.exe",
-      "activeTabs": [
-        {
-          "id": "PAGE_1",
-          "title": "general - Weavetab Slack",
-          "url": "https://app.slack.com/client/..."
-        }
-      ]
-    },
-    {
-      "name": "vscode",
-      "status": "offline",
-      "configuredPath": "C:\\Users\\username\\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe"
-    }
-  ],
-  "toolCoverage": {
-    "chromium": 100,
-    "firefox": 78,
-    "webkit": 55
-  }
-}
-```
-
----
-
-## 2. Understanding Application Status
-
-Each configured desktop app reports one of three distinct lifecycle statuses:
-
-| Status | Meaning | Agent Action |
-| :--- | :--- | :--- |
-| **`connected`** | App is running with CDP remote debugging active. Weavetab has an active session. | Immediately interact using any tool with `"app": "<name>"`. Tabs and port are available. |
-| **`running_no_debug`** | The app process is currently open on the user's OS, but was launched normally by the user without `--remote-debugging-port`. | Do NOT send click/type commands. To attach, inform the user or close and launch via `browser_navigate(app: "<name>")` so Weavetab supplies the debugging port. |
-| **`offline`** | The application is not currently running on the OS. | Launch and attach in one step by calling `browser_navigate(app: "<name>")`. |
-
----
-
-## 3. Dynamic Squirrel Updates on Windows
-
-On Windows, Squirrel-managed applications (Discord, Slack, Teams) update dynamically into versioned sibling directories (e.g. `Discord\app-1.0.9256\Discord.exe`). 
-
-Weavetab automatically handles this:
-- If a configured path points to an outdated version or the parent folder, Weavetab scans the directory, resolves the highest semantic version folder (`app-1.0.xxxx`), and launches the valid executable.
-- The dynamically resolved path is reported in `browser_detect` under `configuredPath`.
-
----
-
-## 4. Launching Desktop Apps Manually with Debugging
-
-If the user prefers to launch apps manually from a terminal or shortcut with remote debugging enabled:
-
-```bash
-# Discord
-Discord.exe --remote-debugging-port=9222
-
-# Slack
-slack.exe --remote-debugging-port=9223
-
-# VS Code
-code.exe --remote-debugging-port=9225
-```
-
-Once launched with `--remote-debugging-port`, `browser_detect` immediately reflects the application as connectable.
+---
+id: electron-discovery
+domain: desktop
+triggers:
+  - "discover electron apps"
+  - "detect desktop apps"
+  - "connect to slack"
+  - "connect to discord"
+  - "connect to vscode"
+  - "electron automation"
+tools:
+  - "browser_detect"
+weavetab: ">=2.5.0"
+---
+
+# Electron Discovery & Environment Handshake
+
+Modern desktop applications (Discord, Slack, VS Code, Notion, Obsidian, Figma) are built on Chromium and Electron. Weavetab can inspect and drive these native applications through standard CDP interfaces without third-party drivers or OS-level accessibility hacks.
+
+`browser_detect` is the **critical initialization handshake** tool. Every agent should call `browser_detect` before interacting with the user's desktop environment to gain immediate situational awareness.
+
+---
+
+## 1. Running Discovery via `browser_detect`
+
+Call `browser_detect` with empty parameters `{}`:
+
+```json
+{}
+```
+
+### Response Schema:
+```json
+{
+  "available": [
+    {
+      "engine": "chromium",
+      "name": "Google Chrome",
+      "path": "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe"
+    }
+  ],
+  "current": "chromium",
+  "configuredApps": [
+    {
+      "name": "discord",
+      "status": "running_no_debug",
+      "configuredPath": "%LOCALAPPDATA%\\Discord\\app-<version>\\Discord.exe"
+    },
+    {
+      "name": "slack",
+      "status": "connected",
+      "port": 9222,
+      "configuredPath": "%LOCALAPPDATA%\\slack\\app-<version>\\slack.exe",
+      "activeTabs": [
+        {
+          "id": "PAGE_1",
+          "title": "general - Weavetab Slack",
+          "url": "https://app.slack.com/client/..."
+        }
+      ]
+    },
+    {
+      "name": "vscode",
+      "status": "offline",
+      "configuredPath": "%LOCALAPPDATA%\\Programs\\Microsoft VS Code\\Code.exe"
+    }
+  ],
+  "toolCoverage": {
+    "chromium": 100,
+    "firefox": 78,
+    "webkit": 55
+  }
+}
+```
+
+---
+
+## 2. Understanding Application Status
+
+Each configured desktop app reports one of three distinct lifecycle statuses:
+
+| Status | Meaning | Agent Action |
+| :--- | :--- | :--- |
+| **`connected`** | App is running with CDP remote debugging active. Weavetab has an active session. | Immediately interact using any tool with `"app": "<name>"`. Tabs and port are available. |
+| **`running_no_debug`** | The app process is currently open on the user's OS, but was launched normally by the user without `--remote-debugging-port`. | Do NOT send click/type commands. To attach, inform the user or close and launch via `browser_navigate(app: "<name>")` so Weavetab supplies the debugging port. |
+| **`offline`** | The application is not currently running on the OS. | Launch and attach in one step by calling `browser_navigate(app: "<name>")`. |
+
+---
+
+## 3. Dynamic Squirrel Updates on Windows
+
+On Windows, Squirrel-managed applications (Discord, Slack, Teams) update dynamically into versioned sibling directories (e.g. `Discord\app-1.0.9256\Discord.exe`). 
+
+Weavetab automatically handles this:
+- If a configured path points to an outdated version or the parent folder, Weavetab scans the directory, resolves the highest semantic version folder (`app-1.0.xxxx`), and launches the valid executable.
+- The dynamically resolved path is reported in `browser_detect` under `configuredPath`.
+
+---
+
+## 4. Launching Desktop Apps Manually with Debugging
+
+If the user prefers to launch apps manually from a terminal or shortcut with remote debugging enabled:
+
+```bash
+# Discord
+Discord.exe --remote-debugging-port=9222
+
+# Slack
+slack.exe --remote-debugging-port=9223
+
+# VS Code
+code.exe --remote-debugging-port=9225
+```
+
+Once launched with `--remote-debugging-port`, `browser_detect` immediately reflects the application as connectable.