Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

一键通过9222调试端口启动Chrome

v1.0.0

启动Chrome浏览器,自动通过9222端口开启远程调试模式,方便调试和开发使用。

0· 201·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for aizzaua/chrome9222.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "一键通过9222调试端口启动Chrome" (aizzaua/chrome9222) from ClawHub.
Skill page: https://clawhub.ai/aizzaua/chrome9222
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install chrome9222

ClawHub CLI

Package manager switcher

npx clawhub@latest install chrome9222
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's claimed purpose — start Chrome with remote debugging on port 9222 — aligns with the provided runtime instructions (it kills existing chrome.exe processes and launches chrome.exe with --remote-debugging-port and a user-data-dir). However the SKILL.md contains Windows-specific commands and an explicit Windows Chrome path despite the skill metadata listing no OS restriction; that mismatch is an incoherence the user should be aware of.
!
Instruction Scope
The instructions execute shell commands via child_process.execSync: taskkill /f /im chrome.exe and launching "C:\Program Files\Google\Chrome\Application\chrome.exe" with --user-data-dir=C:\temp\chrome_test. These actions (force-killing all Chrome processes) can cause loss of unsaved data and have side effects on running applications. The instructions also assume write access to C:\temp and the exact Chrome install path. While these commands are necessary to achieve the stated goal, they are destructive and platform-specific and the skill does not warn about these effects.
Install Mechanism
Instruction-only skill with no install spec or external downloads — no code is written to disk by an installer. This is low install risk.
Credentials
The skill does not request environment variables, credentials, or config paths beyond using a local user-data-dir; the required capabilities are proportionate to starting a browser. There are no unexplained credential requests.
Persistence & Privilege
The skill is not always-enabled and does not request elevated persistence or modify other skills. It will run commands when invoked; autonomous invocation is allowed by platform default but not exceptional here.
What to consider before installing
This skill will forcibly kill all running Chrome processes and then start Chrome from the hard-coded path C:\Program Files\Google\Chrome\Application\chrome.exe with --remote-debugging-port=9222 and a user-data-dir of C:\temp\chrome_test. Before installing or running it: (1) confirm you are on Windows and that Chrome is installed at that path (otherwise modify the command); (2) be aware taskkill /f will close Chrome immediately and may cause loss of unsaved tabs or data; (3) ensure C:\temp exists and you accept a new Chrome profile being created there; (4) understand that opening a remote debugging port can expose powerful controls — only use on trusted, local networks and consider firewall/localhost restrictions; (5) if you want safer behavior, run the commands manually or adjust the script to avoid force-killing processes and to use the correct Chrome path. If you need further help adapting the skill to your environment (e.g., macOS/Linux or a different Chrome path), provide your OS and Chrome location.

Like a lobster shell, security has layers — review code before you run it.

latestvk9784n1emq7s38bq3b2w3qm67n833jra
201downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

{ "name": "Chrome9222端口启动", "id": "chrome_9222_launch", "version": "1.0.0", "description": "一键通过9222调试端口启动Chrome", "config": { "browser": { "enabled": true, "type": "chrome", "remoteDebuggingPort": 9222, "headless": false } }, "actions": [ { "name": "启动Chrome(9222端口)", "id": "launch_chrome_9222", "parameters": [], "exec": { "type": "script", "lang": "javascript", "code": "async function execute() { try { // 杀死残留Chrome进程 const { execSync } = require('child_process'); execSync('taskkill /f /im chrome.exe 2>nul'); // 启动Chrome(9222端口) execSync('"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir=C:\temp\chrome_test'); return '✅ Chrome已通过9222端口启动!'; } catch (error) { return ❌ 启动失败:${error.message}; } }" } } ], "triggers": [] }

Comments

Loading comments...