← Back to Skills Marketplace
126
Downloads
0
Stars
1
Active Installs
2
Versions
Install in OpenClaw
/install tabbit-devtools
Description
Use Tabbit with agent-browser by reading Tabbit's live DevToolsActivePort file, deriving the browser wsEndpoint, and routing browser actions through agent-br...
Usage Guidance
This skill appears internally consistent and does only what it advertises: read Tabbit's DevToolsActivePort and hand a WebSocket endpoint to agent-browser. Before installing: (1) confirm you want an agent to control your browser — agent-browser will be able to inspect and interact with pages (so only use with content you trust being accessible); (2) ensure Tabbit is running with remote debugging enabled and that the DevToolsActivePort path is the expected macOS path (the scripts target ~/Library/Application Support/...); (3) if you do not want code fetched at runtime, install agent-browser yourself so the script doesn't fall back to 'npx'; (4) don't set AGENT_BROWSER_BIN to an untrusted command, since the wrapper will run whatever that points to. If you want extra assurance, review or run the included Python scripts locally to confirm behavior before letting an agent invoke them.
Capability Analysis
Type: OpenClaw Skill
Name: tabbit-devtools
Version: 1.0.1
The tabbit-devtools skill bundle is designed to facilitate browser automation by connecting the OpenClaw agent to a running Tabbit browser instance. It achieves this by reading the local 'DevToolsActivePort' file (scripts/discover_tabbit_cdp.py) to identify the WebSocket debugging endpoint and then wrapping the 'agent-browser' utility to execute commands against that endpoint (scripts/run_agent_browser_on_tabbit.py). The code logic and instructions in SKILL.md are consistent with the stated purpose, and no indicators of data exfiltration, malicious execution, or unauthorized persistence were found.
Capability Assessment
Purpose & Capability
Name, description, and code all align: the scripts read Tabbit's DevToolsActivePort, derive port/browserPath/wsEndpoint, and hand that endpoint to agent-browser. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md and scripts only instruct reading the specific DevToolsActivePort files under ~/Library/Application Support and launching agent-browser with the discovered wsEndpoint. They do not attempt to read arbitrary user files, harvest secrets, or contact external endpoints beyond launching the local agent-browser client.
Install Mechanism
The skill is instruction-only (no install spec) and includes simple Python helpers — low risk. One runtime behavior to note: the wrapper will prefer a locally installed 'agent-browser' but will fall back to 'npx --yes agent-browser' if npx is available, which can fetch and execute code from the npm registry at runtime (supply-chain risk if you don't trust that package).
Credentials
No required env vars. The scripts honor optional vars (TABBIT_DEVTOOLS_ACTIVE_PORT_FILE, TABBIT_DISCOVERY_WAIT_SECONDS, TABBIT_DISCOVERY_POLL_INTERVAL_SECONDS, AGENT_BROWSER_BIN) which are proportional to discovery and launcher configuration. Be aware AGENT_BROWSER_BIN can point to any command (so ensure it's set only to a trusted binary).
Persistence & Privilege
Skill is not always-enabled and doesn't request elevated or persistent system privileges, nor does it modify other skills or system-wide agent settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install tabbit-devtools - After installation, invoke the skill by name or use
/tabbit-devtools - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Adds fallback: if ~/Library/Application Support/Tabbit/DevToolsActivePort does not exist, also check ~/Library/Application Support/Tabbit Browser/DevToolsActivePort.
- Updates guidance to search the macOS Tabbit support directory first, then Tabbit Browser.
- No functional changes beyond supporting both Tabbit data directories for improved compatibility.
v1.0.0
Initial release of tabbit-devtools skill:
- Enables connecting agent-browser to the Tabbit browser via Tabbit's live DevToolsActivePort file.
- Automatically derives and returns the correct wsEndpoint, handling cases where Tabbit doesn't expose standard HTTP discovery APIs.
- Provides structured connection facts (port, browser path, wsEndpoint) before encouraging use of agent-browser for all page automation.
- Strongly prefers the built-in agent-browser workflow for browser actions; does not implement a custom CDP client or daemon.
- Includes guidance, workflow, and references for integrating Tabbit with agent-browser-based automation.
Metadata
Frequently Asked Questions
What is tabbit-devtools?
Use Tabbit with agent-browser by reading Tabbit's live DevToolsActivePort file, deriving the browser wsEndpoint, and routing browser actions through agent-br... It is an AI Agent Skill for Claude Code / OpenClaw, with 126 downloads so far.
How do I install tabbit-devtools?
Run "/install tabbit-devtools" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is tabbit-devtools free?
Yes, tabbit-devtools is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does tabbit-devtools support?
tabbit-devtools is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created tabbit-devtools?
It is built and maintained by Carri1Sun (@carri1sun); the current version is v1.0.1.
More Skills