@weavetab/skills 2.5.0 → 2.5.1

package/dist/bundled/weavetab-desktop.md

@@ -1,176 +1,176 @@
-# Weavetab Domain Profile: DESKTOP
-
-Generated for @weavetab/skills v2.5.0-beta.5
-
-
-## desktop-targeting
-
-# 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")`.
-
-
-## electron-discovery
-
-# 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.
+# Weavetab Domain Profile: DESKTOP
+
+Generated for @weavetab/skills v2.5.1
+
+
+## desktop-targeting
+
+# 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.1 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")`.
+
+
+## electron-discovery
+
+# 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.

package/dist/bundled/weavetab-developer.md

@@ -1,67 +1,84 @@
-# Weavetab Domain Profile: DEVELOPER
-
-Generated for @weavetab/skills v2.5.0-beta.5
-
-
-## github-forensics
-
-# GitHub Forensics & Repository Architecture Inspection
-
-Navigating GitHub repositories via web browsing burns massive token budgets loading HTML chrome, comment threads, and diff trees. Weavetab includes a dedicated `browser_github` tool that interacts directly with git metadata and raw endpoints.
-
----
-
-## 1. High-Level Repository Analysis (action: "analyze")
-
-Quickly summarize repo structure, languages, dependency graphs, and recent commit frequency:
-
-```json
-{
-  "action": "analyze",
-  "repo": "Weavetab/MCP"
-}
-```
-
----
-
-## 2. Reading Repository Source Files (action: "read")
-
-Directly stream files and directories from any public or authenticated GitHub repo without cloning or burning API rate limits:
-
-```json
-{
-  "action": "read",
-  "repo": "Weavetab/MCP",
-  "paths": ["src/server.ts"],
-  "line_range": [1, 200]
-}
-```
-
----
-
-## 3. Pull Request Forensics (action: "pr")
-
-Retrieve PR diffs, changed files, review comments, CI checks, and mergeability status:
-
-```json
-{
-  "action": "pr",
-  "repo": "Weavetab/MCP",
-  "number": 42
-}
-```
-
----
-
-## 4. Issue Triage & Search (action: "issues")
-
-Query repository issue trackers with state, label, and keyword filters:
-
-```json
-{
-  "action": "issues",
-  "repo": "Weavetab/MCP",
-  "state": "open",
-  "labels": ["bug", "priority"]
-}
-```
+# Weavetab Domain Profile: DEVELOPER
+
+Generated for @weavetab/skills v2.5.1
+
+
+## github-forensics
+
+# GitHub Forensics & Repository Architecture Inspection
+
+Navigating GitHub repositories via web browsing burns massive token budgets loading HTML chrome, comment threads, and diff trees. The official `@weavetab/plugin-github` plugin provides a dedicated `github` tool that talks to the GitHub REST API and raw content endpoints directly — no browser DOM, no cloning.
+
+Responses are cached on disk (`~/.weavetab-system/github_cache`) and subject to GitHub's API rate limits.
+
+---
+
+## 1. High-Level Repository Analysis (action: "analyze")
+
+Fetches repo metadata, the default branch, a flat recursive file tree, and a README snippet (first 100 lines). Results are cached and reused by `read`:
+
+```json
+{
+  "action": "analyze",
+  "repo": "Weavetab/MCP"
+}
+```
+
+Returns fields such as `owner`, `repo`, `default_branch`, `description`, `language`, `file_tree` (array of `{path, type, size, sha}`), and `readme_snippet`.
+
+If `repo` is omitted, the active tab's repository is used.
+
+---
+
+## 2. Reading Repository Source Files (action: "read")
+
+Stream specific files from a public or authenticated repo via `raw.githubusercontent.com`. Requires a prior `analyze` (to cache the default branch and tree), or it will run one automatically:
+
+```json
+{
+  "action": "read",
+  "repo": "Weavetab/MCP",
+  "paths": ["src/server.ts"],
+  "line_range": [1, 200]
+}
+```
+
+`paths` is relative to the repo root; `line_range` is an optional `[start, end]` (1-indexed).
+
+---
+
+## 3. Pull Request Forensics (action: "pr")
+
+Retrieve PR details, changed files, and review comments:
+
+```json
+{
+  "action": "pr",
+  "repo": "Weavetab/MCP",
+  "number": 42
+}
+```
+
+Passing `number` fetches that PR; omitting it lists recent PRs.
+
+---
+
+## 4. Issue Triage & Search (action: "issues")
+
+Query the issue tracker with state, label, keyword, and limit filters:
+
+```json
+{
+  "action": "issues",
+  "repo": "Weavetab/MCP",
+  "state": "open",
+  "labels": ["bug"],
+  "limit": 5
+}
+```
+
+- **`number`** fetches a single issue plus its comments.
+- **`search`** runs a keyword search across issues.
+- **`state`** (`open`/`closed`/`all`) and **`labels`** filter the listing; `limit` caps results (default 5).
+
+> The GitHub **search** API is rate-limited more aggressively than raw/GET reads. `read` and `analyze` file fetches do not consume search-quota calls. If a call fails with a rate-limit message, wait until the reported reset time before retrying.