Browser Extension Enabler
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This skill is clearly meant to enable a browser extension, but it can automatically control the real mouse and run a PowerShell helper that is missing from the reviewed package.
Install only if you intentionally want an agent to move and click your real mouse to reconnect the browser extension. Before using it, verify that the missing PowerShell script is actually included and reviewed, run TestMode, calibrate coordinates, and require user confirmation before any real click.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent could move your cursor and click something in Chrome or another foreground UI unexpectedly.
The skill tells the agent it may automatically execute a command that controls the real mouse and clicks browser UI when a connection check fails. Because it relies on screen coordinates and does not require immediate user confirmation, a wrong window or layout could cause unintended clicks.
当 Agent 检测到扩展未连接时，可以自动调用 ... exec: { command: "powershell -File ...enable-browser-extension.ps1" }Use only with explicit confirmation, run TestMode first, calibrate coordinates carefully, and consider disabling autonomous invocation for this skill.
The skill may simply fail, or it could execute an unrelated local file at the referenced path if one exists, outside the reviewed package contents.
The reviewed package contains no scripts directory or enable-browser-extension.ps1, even though SKILL.md and PUBLISH.md instruct the agent/user to run that script. This creates a provenance gap for the runnable behavior.
3 file(s): PUBLISH.md ... SKILL.md ... _meta.json
Publish the referenced script with the skill, make the dependency and OS requirements consistent in registry metadata, and avoid automatic execution until the helper code can be inspected.