← Back to Skills Marketplace
Chrome Debug Launcher
by
chengzongxin
· GitHub ↗
· v1.0.1
· MIT-0
600
Downloads
0
Stars
1
Active Installs
2
Versions
Install in OpenClaw
/install chrome-debug-launcher
Description
Launch two independent Chrome browser instances — one normal and one with remote debugging enabled on port 9222. Activate when user says "打开两个浏览器", "开调试浏览器",...
README (SKILL.md)
Chrome Debug Launcher
Launch two independent Chrome instances: one normal, one with remote debugging on port 9222.
Steps
- Kill all Chrome processes
- Launch normal Chrome (no extra args)
- Wait 2 seconds, then launch debug Chrome
Commands by Platform
Windows (PowerShell)
# Step 1: Kill Chrome
taskkill /F /IM chrome.exe /T 2>$null
Start-Sleep -Seconds 2
# Step 2: Normal Chrome
Start-Process "C:\Program Files\Google\Chrome\Application\chrome.exe"
# Step 3: Debug Chrome (after 2s)
Start-Sleep -Seconds 2
Start-Process "C:\Program Files\Google\Chrome\Application\chrome.exe" -ArgumentList '--remote-debugging-port=9222', '--user-data-dir=C:\selenum\ChromeProfile'
macOS (bash)
# Step 1: Kill Chrome
pkill -f "Google Chrome" 2>/dev/null; sleep 2
# Step 2: Normal Chrome
open -a "Google Chrome"
# Step 3: Debug Chrome (after 2s)
sleep 2
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--remote-debugging-port=9222 \
--user-data-dir="$HOME/selenium/ChromeProfile" &
Result
- Instance 1: Normal Chrome, default profile, regular use
- Instance 2: Debug Chrome, port 9222, isolated user data dir
- Connect via Selenium/Playwright:
http://localhost:9222
- Connect via Selenium/Playwright:
Usage Guidance
This skill appears to do what it says, but review and consider the following before installing or running: 1) The commands kill all Chrome processes — this may close windows/tabs with unsaved data; run manually if you need to preserve sessions. 2) Verify and/or change the hardcoded paths (Windows: C:\Program Files\..., profile path C:\selenum\ChromeProfile; macOS: /Applications/... and $HOME/selenium/ChromeProfile) to safe locations. 3) Remote debugging opens port 9222 on the host — ensure you are not exposing that port to untrusted networks. 4) Because this is instruction-only, the agent would need permission to run shell/PowerShell commands; only allow the skill if you trust it to execute these OS commands. If you're unsure, run the provided commands yourself rather than giving the agent automatic execution privileges.
Capability Analysis
Type: OpenClaw Skill
Name: chrome-debug-launcher
Version: 1.0.1
The skill in SKILL.md performs high-risk actions including the forced termination of all running Chrome processes (taskkill/pkill) and the activation of a remote debugging port (9222). While these behaviors are aligned with the stated purpose of setting up a development environment for Selenium/Playwright, they introduce significant security risks such as potential data loss and unauthorized remote browser control if the port is exposed to a network.
Capability Assessment
Purpose & Capability
Name/description match the concrete instructions: the SKILL.md explicitly kills Chrome and launches two instances (one with --remote-debugging-port=9222 and a separate user-data-dir). There are no unrelated environment variables, binaries, or installs requested.
Instruction Scope
The instructions remain within the stated goal but are somewhat heavy-handed: they unconditionally kill all Chrome processes (taskkill/pkill) which can cause data loss or disruption of other browser sessions. They also create/use fixed user-data-dir paths (C:\selenum\ChromeProfile and $HOME/selenium/ChromeProfile) and assume default install locations. The remote-debugging port is exposed on localhost — expected for the purpose but potentially sensitive if the machine forwards ports.
Install Mechanism
Instruction-only skill with no install spec and no code to write to disk; lowest-risk install profile. The regex scanner found no code to analyze.
Credentials
The skill declares no required environment variables, credentials, or config paths and the instructions do not reference secrets. Requested file paths are local and relate to isolating the debug profile.
Persistence & Privilege
always is false and the skill does not request persistent system configuration or modify other skills. Autonomous invocation is allowed by default but not unusually privileged.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install chrome-debug-launcher - After installation, invoke the skill by name or use
/chrome-debug-launcher - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Added _meta.json file for improved metadata management.
- No changes to core functionality or documentation content.
v1.0.0
打开两个浏览器
Metadata
Frequently Asked Questions
What is Chrome Debug Launcher?
Launch two independent Chrome browser instances — one normal and one with remote debugging enabled on port 9222. Activate when user says "打开两个浏览器", "开调试浏览器",... It is an AI Agent Skill for Claude Code / OpenClaw, with 600 downloads so far.
How do I install Chrome Debug Launcher?
Run "/install chrome-debug-launcher" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Chrome Debug Launcher free?
Yes, Chrome Debug Launcher is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Chrome Debug Launcher support?
Chrome Debug Launcher is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Chrome Debug Launcher?
It is built and maintained by chengzongxin (@chengzongxin); the current version is v1.0.1.
More Skills