Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Web Automation
v1.0.0Automate browsing tasks with advanced navigation, interaction, data scraping, form filling, and high-res screenshot capture using a headless browser.
⭐ 0· 15·1 current·1 all-time
by@rudigta
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name and description claim a full headless-browser automation tool (navigation, JS interaction, screenshots, form logins). However the skill bundle contains no code, no install instructions, and declares no required binaries (Chrome, Chromium, Playwright, Puppeteer, Selenium, etc.). That mismatch means the skill either relies on an undocumented runtime component or is incomplete; either is unexplained and inconsistent with the claimed capabilities.
Instruction Scope
The SKILL.md is high-level and open-ended: it tells agents to use the skill for browsing and to 'login to a portal' but provides no concrete runtime commands, no API endpoints, and no guidance for securely obtaining or storing credentials. This grants the agent broad discretion (which pages to visit, what credentials to use) without safety or scope limits.
Install Mechanism
There is no install spec and no files beyond SKILL.md, so the skill does not write code to disk (low install risk). However, the doc explicitly references a headless browser engine 'optimized for OpenCloudOS' — claiming a runtime dependency that is not declared or documented is an implementation inconsistency to be clarified.
Credentials
The skill requests no environment variables or credentials (proportionate on its face). But because the intended use includes automated logins and form-filling, the lack of any guidance about how credentials should be supplied, validated, or protected is a concern: sensitive secrets may be handled ad hoc in conversation or injected without clear rules.
Persistence & Privilege
always is false and there is no claim of modifying system or other skills' configs. Autonomous invocation remains allowed (platform default) but this alone is not a new risk here.
What to consider before installing
This skill's description and runtime doc promise a headless-browser automation engine but provide no implementation, dependency list, or secret-handling guidance. Before installing or using it, ask the publisher: (1) what runtime/binary provides the headless browser (Chromium/Playwright/Puppeteer/etc.), (2) how the agent obtains and runs that browser (preinstalled runtime, remote service, or package install), and (3) how credentials should be provided and protected during 'login' tasks (do not paste primary account passwords into chat). If you must test it, use a non-sensitive test account and limit scope (no bank, work, or personal accounts). Prefer skills that include explicit install steps, declared dependencies, and secure handling instructions for secrets.Like a lobster shell, security has layers — review code before you run it.
latestvk974v46zhn970542dxnvqy8w8s8506bn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.