@weavetab/skills 2.5.0-beta.5 → 2.5.0

package/README.md

@@ -4,7 +4,7 @@
 [![GitHub stars](https://img.shields.io/github/stars/Weavetab/skills.svg?style=social)](https://github.com/Weavetab/skills)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
-Enterprise domain-driven agent intelligence for `@weavetab/mcp` (v2.5.0-beta.5). Drop-in operational guides, failure recovery heuristics, and protocol rules for **Antigravity**, **Cursor**, **Cline**, **Windsurf**, and **OpenClaw**.
+Enterprise domain-driven agent intelligence for `@weavetab/mcp` (v2.5.0). Drop-in operational guides, failure recovery heuristics, and protocol rules for **Antigravity**, **Cursor**, **Cline**, **Windsurf**, and **OpenClaw**.
 
 - **Website:** [weavetab.dev](https://weavetab.dev)
 - **Core MCP Server:** [`@weavetab/mcp`](https://www.npmjs.com/package/@weavetab/mcp)

package/browser/dom-strategy.md

@@ -14,7 +14,7 @@ tools:
   - "browser_scrape"
   - "browser_snapshot"
   - "browser_eval"
-weavetab: ">=2.5.0-beta.5"
+weavetab: ">=2.5.0"
 ---
 
 # DOM Strategy & Token Conservation Engine

package/browser/form-automation.md

@@ -11,7 +11,7 @@ triggers:
 tools:
   - "browser_fill"
   - "browser_select"
-weavetab: ">=2.5.0-beta.5"
+weavetab: ">=2.5.0"
 ---
 
 # Form Automation: Atomic Multi-Field Execution

package/browser/interaction-pipeline.md

@@ -19,7 +19,7 @@ tools:
   - "browser_burst"
   - "browser_highlight"
   - "browser_clipboard"
-weavetab: ">=2.5.0-beta.5"
+weavetab: ">=2.5.0"
 ---
 
 # Interaction Pipeline: Physical & Synthetic Input Engine

package/browser/tab-and-window.md

@@ -11,7 +11,7 @@ triggers:
   - "desktop app tabs"
 tools:
   - "browser_tabs"
-weavetab: ">=2.5.0-beta.5"
+weavetab: ">=2.5.0"
 ---
 
 # Tab & Window Lifecycle Management

package/desktop/desktop-targeting.md

@@ -15,7 +15,7 @@ tools:
   - "browser_detect"
   - "browser_tabs"
   - "browser_navigate"
-weavetab: ">=2.5.0-beta.5"
+weavetab: ">=2.5.0"
 ---
 
 # Desktop App Targeting & Multi-Window Routing

package/desktop/electron-discovery.md

@@ -10,7 +10,7 @@ triggers:
   - "electron automation"
 tools:
   - "browser_detect"
-weavetab: ">=2.5.0-beta.5"
+weavetab: ">=2.5.0"
 ---
 
 # Electron Discovery & Environment Handshake

package/developer/github-forensics.md

@@ -9,7 +9,7 @@ triggers:
   - "inspect repo"
 tools:
   - "browser_github"
-weavetab: ">=2.5.0-beta.5"
+weavetab: ">=2.5.0"
 ---
 
 # GitHub Forensics & Repository Architecture Inspection

package/dist/bundled/weavetab-browser.md

@@ -1,10 +1,10 @@
-# Weavetab Domain Profile: BROWSER
-
-Generated for @weavetab/skills v2.5.0-beta.5
-
-
-## dom-strategy
-
+# Weavetab Domain Profile: BROWSER
+
+Generated for @weavetab/skills v2.5.0-beta.5
+
+
+## dom-strategy
+
 # DOM Strategy & Token Conservation Engine
 
 When parsing modern web applications, naive DOM dumps can consume 50,000+ tokens and cause agent degradation. Weavetab provides a high-efficiency 4-tier reading architecture.
@@ -104,11 +104,11 @@ Weavetab maps elements to ephemeral handles (`w:NN`) and visual marks (`[1]…[N
 1. **Never Construct Speculative CSS Selectors**: If an element has ref `w:14`, pass `"ref": "w:14"` to `browser_click`, `browser_fill`, `browser_type`.
 2. **Visual Mark Targeting**: On canvas or unlabelled elements from `visual: "auto"`, pass `"mark": N` directly to `browser_click({ mark: N })`.
 3. **Lifespan of Handles**: Ref IDs and marks invalidate on page navigation (`browser_navigate`) or heavy SPA re-renders. 
-4. **Recovery on Invalidation**: If an action fails with `ELEMENT_NOT_FOUND` or `MARK_NOT_FOUND`, re-run `browser_map({ visual: "auto" })` to refresh active handles.
-
-
-## form-automation
-
+4. **Recovery on Invalidation**: If an action fails with `ELEMENT_NOT_FOUND` or `MARK_NOT_FOUND`, re-run `browser_map({ visual: "auto" })` to refresh active handles.
+
+
+## form-automation
+
 # Form Automation: Atomic Multi-Field Execution
 
 Submitting complex web forms one field at a time wastes agent turns and increases the probability of layout shifts. Weavetab provides atomic multi-field batching and native dropdown selectors.
@@ -179,11 +179,11 @@ For `<select multiple>` elements, pass an array of option values:
 2. **Submit via Enter Key vs Click**:
    - If the submit button has a dynamic ref or changes during typing, send `"key": "Enter"` via `browser_key` inside the last filled text field.
    - Otherwise, locate the submit button via `browser_find` and click via `browser_click`.
-3. **Wait for Post-Submission Route**: Always follow form submission with `browser_wait` for URL changes or target DOM confirmation rather than immediately firing subsequent actions.
-
-
-## interaction-pipeline
-
+3. **Wait for Post-Submission Route**: Always follow form submission with `browser_wait` for URL changes or target DOM confirmation rather than immediately firing subsequent actions.
+
+
+## interaction-pipeline
+
 # Interaction Pipeline: Physical & Synthetic Input Engine
 
 Weavetab executes browser interactions via direct Chrome DevTools Protocol (CDP) dispatch, bypassing synthetic JavaScript event limitations and anti-automation tripwires.
@@ -374,11 +374,11 @@ Read or write system clipboard text during automation:
   "action": "write",
   "text": "AuthToken_xyz987"
 }
-```
-
-
-## tab-and-window
-
+```
+
+
+## tab-and-window
+
 # 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.
@@ -498,4 +498,4 @@ If a target page crashes or detaches due to memory limits:
 }
 ```
 
-The auto-heal routine re-establishes CDP protocol sessions, reconnects event listeners, and synchronizes the active page target.
+The auto-heal routine re-establishes CDP protocol sessions, reconnects event listeners, and synchronizes the active page target.

package/dist/bundled/weavetab-desktop.md

@@ -1,10 +1,10 @@
-# Weavetab Domain Profile: DESKTOP
-
-Generated for @weavetab/skills v2.5.0-beta.5
-
-
-## desktop-targeting
-
+# 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.
@@ -69,11 +69,11 @@ Some Electron apps open secondary windows (e.g. popout editors, settings panels,
 
 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
-
+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.
@@ -173,4 +173,4 @@ slack.exe --remote-debugging-port=9223
 code.exe --remote-debugging-port=9225
 ```
 
-Once launched with `--remote-debugging-port`, `browser_detect` immediately reflects the application as connectable.
+Once launched with `--remote-debugging-port`, `browser_detect` immediately reflects the application as connectable.

package/dist/bundled/weavetab-developer.md

@@ -1,10 +1,10 @@
-# Weavetab Domain Profile: DEVELOPER
-
-Generated for @weavetab/skills v2.5.0-beta.5
-
-
-## github-forensics
-
+# 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.
@@ -64,4 +64,4 @@ Query repository issue trackers with state, label, and keyword filters:
   "state": "open",
   "labels": ["bug", "priority"]
 }
-```
+```

package/dist/bundled/weavetab-documents.md

@@ -1,10 +1,10 @@
-# Weavetab Domain Profile: DOCUMENTS
-
-Generated for @weavetab/skills v2.5.0-beta.5
-
-
-## canvas-and-visual-capture
-
+# Weavetab Domain Profile: DOCUMENTS
+
+Generated for @weavetab/skills v2.5.0-beta.5
+
+
+## canvas-and-visual-capture
+
 # Visual Capture, Canvas Forensics & Design Extraction
 
 Beyond textual DOM manipulation, modern web applications contain dynamic HTML5 canvas renderings (charts, maps, WebGL games), and agents often need high-fidelity visual artifacts.
@@ -87,11 +87,11 @@ Reverse-engineer UI stylesheets, active CSS custom properties (variables), typog
 }
 ```
 
-Returns structured JSON representing colors, font families, shadows, and spacing tokens.
-
-
-## office-document-ingestion
-
+Returns structured JSON representing colors, font families, shadows, and spacing tokens.
+
+
+## office-document-ingestion
+
 # Office Document Ingestion: Word, Excel & CSV Parsing
 
 Agents frequently need to parse structured spreadsheets or corporate documents downloaded during automation runs. `browser_office` parses `.docx`, `.xlsx`, `.xls`, and `.csv` files directly into clean JSON structures.
@@ -139,4 +139,4 @@ Extract semantic paragraphs, document headings, tables, and lists:
 
 ### Operational Advantages:
 - Eliminates the need for heavy external Python libraries or microservices.
-- Safely sanitizes binary formats before passing content into LLM context.
+- Safely sanitizes binary formats before passing content into LLM context.

package/dist/bundled/weavetab-network-and-perf.md

@@ -1,10 +1,10 @@
-# Weavetab Domain Profile: NETWORK-AND-PERF
-
-Generated for @weavetab/skills v2.5.0-beta.5
-
-
-## device-and-environment
-
+# Weavetab Domain Profile: NETWORK-AND-PERF
+
+Generated for @weavetab/skills v2.5.0-beta.5
+
+
+## device-and-environment
+
 # Device Emulation & Environment Simulation
 
 Auditing mobile responsive layouts, testing geographic restrictions, and simulating degraded network conditions can all be accomplished with `browser_emulate`.
@@ -76,11 +76,11 @@ To reset all overrides back to default host system parameters:
 {
   "reset": true
 }
-```
-
-
-## network-intercept-and-mock
-
+```
+
+
+## network-intercept-and-mock
+
 # Network Interception, Mocking & TLS Forensics
 
 Autonomous testing and debugging often require simulating backend error states (e.g. 500 Internal Server Error, 429 Rate Limit), stubbing third-party analytics, or verifying TLS/SSL certificates.
@@ -149,11 +149,11 @@ Extract cryptographic handshake metadata, cipher suites, expiration dates, and m
     "ttfbMs": 12.8
   }
 }
-```
-
-
-## performance-and-vitals
-
+```
+
+
+## performance-and-vitals
+
 # Performance Forensics & Core Web Vitals
 
 Optimizing agent execution and auditing client performance requires objective metrics rather than arbitrary sleep timers.
@@ -220,4 +220,4 @@ Always synchronize with deterministic browser conditions:
   "selector": "[data-testid=\"checkout-complete\"]",
   "timeout": 15000
 }
-```
+```

package/dist/bundled/weavetab-plugins.md

@@ -1,10 +1,10 @@
-# Weavetab Domain Profile: PLUGINS
-
-Generated for @weavetab/skills v2.5.0-beta.5
-
-
-## hooks-and-overrides
-
+# Weavetab Domain Profile: PLUGINS
+
+Generated for @weavetab/skills v2.5.0-beta.5
+
+
+## hooks-and-overrides
+
 # Plugin Hooks & Lifecycle Overrides
 
 Plugins built with `@weavetab/sdk` register lifecycle hooks that run before and after tool executions. Understanding these hooks helps agents interpret metadata and custom tool responses.
@@ -26,58 +26,58 @@ Plugins built with `@weavetab/sdk` register lifecycle hooks that run before and
 
 ## 2. Agent Operational Awareness
 
-When plugins are active, tool return payloads may include an optional `_pluginMetadata` object containing trace IDs, custom metrics, or security audit timestamps. Agents should treat this object as informational telemetry.
-
-
-## plugin-runtime
-
-# Plugin Runtime: Weavetab Plugin Architecture
-
-Weavetab features an extensible plugin architecture powered by `@weavetab/sdk`. All installed plugins are loaded automatically at server startup — their tools appear directly in the MCP tool list alongside built-in tools. Agents never need to discover or activate plugins manually.
-
----
-
-## 1. How Plugin Tools Appear
-
-Plugin tools are first-class MCP tools. If `@weavetab/plugin-recaptcha-solver` is installed, `captcha_solve_token` appears in the tool list immediately on startup — no discovery step needed.
-
-There are **no** `list_plugins` or `load_plugin` tools. Managing plugins is a CLI operation:
-
-```bash
-# Install a plugin (restart required)
-weavetab plugin add @weavetab/plugin-youtube
-
-# Remove a plugin
-weavetab plugin rm @weavetab/plugin-youtube
-
-# List installed plugins
-weavetab plugin list
-```
-
----
-
-## 2. Plugin Permission Model
-
-Every plugin declares what it can do in `weavetab.json`. The runtime enforces this at load time:
-
-| Permission | What it gates |
-|---|---|
-| `tools.add: true` | Plugin can register new MCP tools |
-| `tools.override: ["browser_navigate"]` | Plugin can wrap/replace that built-in tool |
-| `tools.remove: ["browser_pdf"]` | Plugin can disable that built-in tool |
-| `hooks.onBeforeAction: true` | Plugin can intercept all tool calls before execution |
-| `hooks.onAfterAction: true` | Plugin can inspect/transform all tool results |
-
-Plugins that attempt to exceed their declared permissions are blocked with a stderr warning — they do not crash.
-
----
-
-## 3. Trust Tiers
-
-| Tier | Badge | Condition |
-|---|---|---|
-| Official | `✚ [Official]` | `@weavetab/plugin-*` packages |
-| Verified | `✔ [Verified]` | Listed in the Weavetab verified registry |
-| Unverified | `⚠ [Unverified]` | Unknown community package |
-
-Unverified plugins are loaded but their permissions are logged visibly at startup for user review.
+When plugins are active, tool return payloads may include an optional `_pluginMetadata` object containing trace IDs, custom metrics, or security audit timestamps. Agents should treat this object as informational telemetry.
+
+
+## plugin-runtime
+
+# Plugin Runtime: Weavetab Plugin Architecture
+
+Weavetab features an extensible plugin architecture powered by `@weavetab/sdk`. All installed plugins are loaded automatically at server startup — their tools appear directly in the MCP tool list alongside built-in tools. Agents never need to discover or activate plugins manually.
+
+---
+
+## 1. How Plugin Tools Appear
+
+Plugin tools are first-class MCP tools. If `@weavetab/plugin-recaptcha-solver` is installed, `captcha_solve_token` appears in the tool list immediately on startup — no discovery step needed.
+
+There are **no** `list_plugins` or `load_plugin` tools. Managing plugins is a CLI operation:
+
+```bash
+# Install a plugin (restart required)
+weavetab plugin add @weavetab/plugin-youtube
+
+# Remove a plugin
+weavetab plugin rm @weavetab/plugin-youtube
+
+# List installed plugins
+weavetab plugin list
+```
+
+---
+
+## 2. Plugin Permission Model
+
+Every plugin declares what it can do in `weavetab.json`. The runtime enforces this at load time:
+
+| Permission | What it gates |
+|---|---|
+| `tools.add: true` | Plugin can register new MCP tools |
+| `tools.override: ["browser_navigate"]` | Plugin can wrap/replace that built-in tool |
+| `tools.remove: ["browser_pdf"]` | Plugin can disable that built-in tool |
+| `hooks.onBeforeAction: true` | Plugin can intercept all tool calls before execution |
+| `hooks.onAfterAction: true` | Plugin can inspect/transform all tool results |
+
+Plugins that attempt to exceed their declared permissions are blocked with a stderr warning — they do not crash.
+
+---
+
+## 3. Trust Tiers
+
+| Tier | Badge | Condition |
+|---|---|---|
+| Official | `✚ [Official]` | `@weavetab/plugin-*` packages |
+| Verified | `✔ [Verified]` | Listed in the Weavetab verified registry |
+| Unverified | `⚠ [Unverified]` | Unknown community package |
+
+Unverified plugins are loaded but their permissions are logged visibly at startup for user review.

package/dist/bundled/weavetab-resilience.md

@@ -1,10 +1,10 @@
-# Weavetab Domain Profile: RESILIENCE
-
-Generated for @weavetab/skills v2.5.0-beta.5
-
-
-## loop-breaker
-
+# Weavetab Domain Profile: RESILIENCE
+
+Generated for @weavetab/skills v2.5.0-beta.5
+
+
+## loop-breaker
+
 # Loop Breaker & CAPTCHA Escalation Protocol
 
 Agents can get trapped in repetitive click loops when a button does not advance the state (e.g. failing silent validation, unhandled reCAPTCHA challenges, or modals swallowing events). Weavetab actively monitors repetitive patterns and provides circuit breakers.
@@ -54,11 +54,11 @@ Invoke `browser_captcha` to analyze and manage the challenge:
 
 ### Action Strategy:
 1. If the challenge is interactive and requires human intervention (e.g. image classification), inform the user cleanly or request human bypass.
-2. If the challenge is a simple checkbox Turnstile widget, pass `"action": "solve"` or click the detected widget ref with `browser_click`.
-
-
-## session-time-travel
-
+2. If the challenge is a simple checkbox Turnstile widget, pass `"action": "solve"` or click the detected widget ref with `browser_click`.
+
+
+## session-time-travel
+
 # Session Time-Travel & Instant State Rollback
 
 In complex multi-step workflows (e.g. checkout funnels, multi-page configuration wizards, onboarding questionnaires), an error at Step 7 traditionally forces an agent to reload the root URL, re-authenticate, and waste 10+ turns repeating steps.
@@ -172,11 +172,11 @@ Query or clear `localStorage` and `sessionStorage` keys:
   "action": "get",
   "key": "authToken"
 }
-```
-
-
-## stale-ref-recovery
-
+```
+
+
+## stale-ref-recovery
+
 # Stale Ref Recovery & SPA Hydration Resilience
 
 In modern Single Page Applications (built with React, Next.js, Vue, Nuxt, Svelte), DOM nodes are frequently destroyed and recreated during client-side hydration or reactive state updates. This often causes `STALE_ELEMENT_REFERENCE` or `NODE_DETACHED` errors when an agent attempts an action.
@@ -213,4 +213,4 @@ If an action returns `ERROR: STALE_ELEMENT_REFERENCE` because all 4 recovery tie
 
 1. **Do NOT Repeat the Identical Call**: Retrying the exact same stale `ref` (`w:14`) will fail again.
 2. **Execute a Fast Targeted Lookup**: Run `browser_find` with the text of the button or input field.
-3. **Execute the Action on the New Handle**: Use the updated handle returned by `browser_find`.
+3. **Execute the Action on the New Handle**: Use the updated handle returned by `browser_find`.

package/dist/bundled/weavetab-security.md

@@ -1,10 +1,10 @@
-# Weavetab Domain Profile: SECURITY
-
-Generated for @weavetab/skills v2.5.0-beta.5
-
-
-## rbac-and-policies
-
+# Weavetab Domain Profile: SECURITY
+
+Generated for @weavetab/skills v2.5.0-beta.5
+
+
+## rbac-and-policies
+
 # Role-Based Access Control (RBAC) & Agent Guardrails
 
 Weavetab allows developers to run untrusted or lower-privilege subagents within strict security boundaries to prevent accidental destructive operations or data leaks.
@@ -35,11 +35,11 @@ If an agent attempts an action outside its allocated role tier:
 ### Protocol:
 1. Do not retry the denied tool.
 2. Delegate the interactive action to the parent agent or primary operator.
-3. Limit your output to findings gathered via read-only tools (`browser_scrape`, `browser_map`, `browser_inspect`).
-
-
-## secret-containment-protocol
-
+3. Limit your output to findings gathered via read-only tools (`browser_scrape`, `browser_map`, `browser_inspect`).
+
+
+## secret-containment-protocol
+
 # Secret Containment Protocol & Zero-Bleed Execution
 
 AI agent transcripts, LLM providers, and tool logs represent massive attack surfaces for credential leaks. Weavetab enforces a hardware-grade **Zero-Bleed Security Guarantee** for sensitive inputs.
@@ -84,4 +84,4 @@ When `browser_type_secret` is invoked:
 > - `browser_fill`
 > - `browser_eval`
 > 
-> Doing so causes plaintext secrets to enter unmasked transcripts and tool logs.
+> Doing so causes plaintext secrets to enter unmasked transcripts and tool logs.