@vibebrowser/mcp 0.2.5 → 0.2.7

package/openclaw/vibe-local-browser/SKILL.md

@@ -1,132 +0,0 @@
----
-name: vibe-local-browser
-description: Control the user's local browser through the Vibe Browser CLI bridge. Use this when the task must run against the user's real Vibe-connected browser session, tabs, cookies, or installed extensions.
-metadata:
-  {
-    "openclaw":
-      {
-        "emoji": "🌐",
-        "requires":
-          {
-            "bins": ["npx"],
-            "env": ["VIBE_EXTENSION_UUID"],
-          },
-      },
-  }
----
-
-# Vibe Local Browser
-
-Use the `vibebrowser-cli` command when the user wants OpenClaw to drive their real local browser through the Vibe extension.
-
-Prefer this skill when the task depends on:
-
-- the user's real browser profile
-- existing logged-in sessions
-- local tabs already open on the user's machine
-- browser extensions or stored site state
-
-Do not use this skill for OpenClaw tenant cloud browsing.
-
-## Required environment
-
-The shell running OpenClaw must have:
-
-```bash
-export VIBE_EXTENSION_UUID="<extension-uuid>"
-
-# Optional if you use a custom relay URL.
-# export VIBE_RELAY_URL="wss://relay.api.vibebrowser.app"
-
-# Optional compatibility label. Vibe always targets the real local browser path.
-# export VIBE_BROWSER_PROFILE="user"
-```
-
-## Command form
-
-Prefer this exact command pattern:
-
-```bash
-npx -y --package @vibebrowser/mcp vibebrowser-cli --remote "$VIBE_EXTENSION_UUID" --json <subcommand> ...
-```
-
-If the package is already installed locally, you can use:
-
-```bash
-vibebrowser-cli --remote "$VIBE_EXTENSION_UUID" --json <subcommand> ...
-```
-
-If you set `VIBE_RELAY_URL`, append:
-
-```bash
---relay-url "$VIBE_RELAY_URL"
-```
-
-## Safe operating rules
-
-- Prefer `browser tabs` or `browser snapshot` before acting.
-- Use `browser open <url>` to create a fresh page when possible.
-- Use `browser evaluate --fn ...` only for simple compatibility-safe expressions such as:
-  - `() => 21 + 21`
-  - `() => document.title`
-  - `() => location.href`
-  - `() => location.hostname`
-  - `() => location.origin`
-- Avoid destructive actions unless the user explicitly asks.
-- If the CLI returns a connection error, report it clearly and stop guessing.
-- The OpenClaw-compatible `--browser-profile` flag is accepted by the CLI, but Vibe always targets the user's real browser path rather than an isolated managed browser.
-
-## Common commands
-
-Status:
-
-```bash
-npx -y --package @vibebrowser/mcp vibebrowser-cli --remote "$VIBE_EXTENSION_UUID" --json status
-```
-
-List pages:
-
-```bash
-npx -y --package @vibebrowser/mcp vibebrowser-cli --remote "$VIBE_EXTENSION_UUID" --json tabs
-```
-
-Open a new page:
-
-```bash
-npx -y --package @vibebrowser/mcp vibebrowser-cli --remote "$VIBE_EXTENSION_UUID" --json open https://example.com
-```
-
-Take the default AI snapshot:
-
-```bash
-npx -y --package @vibebrowser/mcp vibebrowser-cli --remote "$VIBE_EXTENSION_UUID" --json snapshot
-```
-
-Take the ARIA / interactive snapshot:
-
-```bash
-npx -y --package @vibebrowser/mcp vibebrowser-cli --remote "$VIBE_EXTENSION_UUID" --json snapshot --format aria --interactive
-```
-
-Click and type using OpenClaw-style refs:
-
-```bash
-npx -y --package @vibebrowser/mcp vibebrowser-cli --remote "$VIBE_EXTENSION_UUID" --json click 12
-npx -y --package @vibebrowser/mcp vibebrowser-cli --remote "$VIBE_EXTENSION_UUID" --json type 23 "hello" --submit
-```
-
-Evaluate JavaScript:
-
-```bash
-npx -y --package @vibebrowser/mcp vibebrowser-cli --remote "$VIBE_EXTENSION_UUID" --json evaluate --fn '() => document.title'
-```
-
-## Success criteria
-
-A successful run usually looks like:
-
-1. confirm the relay is reachable
-2. list current tabs or create a fresh one
-3. navigate or snapshot if needed
-4. evaluate `document.title` or `location.href` to verify the result
-5. summarize what happened for the user