Skills/ClawHub/chrome-mcp

chrome-mcp@0.1.0

CAUTION· static only

Publisher claims: "通过 Chrome DevTools MCP 控制本机 Chrome 浏览器(已登录的真实会话)。 适用场景: - 浏览、阅读任意网页内容 - 操作 X (Twitter):浏览 feed、发推文、转帖、点赞、删帖 - 操作任何需要登录的网站(保留已有登录状态) - 截图、读取页面结构、执行 JS - "帮我看看..." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher lumint · publishing for 247 daysInstalls 2,114Last detonated 1 h ago

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-17 and scored it 70/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

No findings across 154 lines in 2 files.

Cost to the agent

Instructions loaded
≈522 tok
1 file · 2 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim lumint: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim lumintPropose a patch to the maintainer