Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Puppeteer@1.0.0
v1.0.0Automate Chrome and Chromium with Puppeteer for scraping, testing, screenshots, and browser workflows.
⭐ 0· 78·1 current·1 all-time
by@1215656
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description align with required binary (node) and the instructions (Puppeteer usage, selectors, waiting patterns). Creating ~/puppeteer/ for scripts and outputs is coherent for a browser-automation skill.
Instruction Scope
SKILL.md and setup.md instruct the agent to run npm install (network fetch) and create/write files under ~/puppeteer/; they also say 'Don't ask — just start naturally' and 'Store in ~/puppeteer/memory.md without mentioning file paths to them.' Those directives push the agent to act autonomously, install packages, and persist memory without explicit user confirmation or transparency about what is stored.
Install Mechanism
There is no formal install spec (instruction-only), which reduces installer-level risk. However setup.md tells the agent to run `npm install puppeteer` or `puppeteer-core` if missing — a normal but network-dependent action that will fetch code from npm. This is expected for Puppeteer but should be performed with user consent.
Credentials
The skill declares no required environment variables or credentials. Mention of 'you provide them per-script' (credentials) is reasonable for site-specific tasks and not requested globally. No unrelated secrets are requested.
Persistence & Privilege
The skill intentionally writes persistent state to the user's home directory (~/puppeteer/) and may install npm packages. While that fits the skill's purpose, the combination of persistent storage plus explicit instruction to proceed without asking increases risk: unexpected file creation, long-lived local state, and network installs could occur without clear user approval.
What to consider before installing
This skill is functionally consistent with a Puppeteer helper, but pay attention before enabling it: it instructs the agent to create ~/puppeteer/, persist a memory file there, and run `npm install` if Puppeteer isn't present — and the docs say to do this 'without asking.' Before installing/use, confirm you are comfortable with the agent writing to your home directory and performing network package installs. Prefer running it in a sandbox or VM, review any generated scripts in ~/puppeteer/scripts/ before execution, and require the agent to ask for explicit permission before installing packages or storing persistent memory. If you want stricter transparency, edit the skill to remove or change the 'Don't ask' directive and require explicit user consent for installs and writes.Like a lobster shell, security has layers — review code before you run it.
latestvk97dnhezrfrcd44mtf2tmb1c2n83jevq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎭 Clawdis
OSLinux · macOS · Windows
Binsnode