BrowserAgent

ReviewAudited by ClawScan on May 10, 2026.

Overview

BrowserAgent is a coherent Playwright automation guide, but it needs review because it explicitly promotes stealth/anti-bot behavior and persistent login-session reuse.

Install only if you need authorized Playwright browser automation and are comfortable managing logged-in sessions. Do not use it to bypass third-party site protections, and treat any saved session.json file like a password.

Findings (3)

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.

What this means

Using this skill on third-party sites could violate site rules, trigger account penalties, or enable automation that site operators intended to block.

Why it was flagged

The skill explicitly frames human-like automation and optional stealth tooling as a way to avoid bot detection, which can bypass site controls rather than merely automate authorized browser tasks.

Skill content
description: "... Simulates real user behavior to avoid bot detection." ... "Sites with bot detection (with human simulation)" ... "npm install -g playwright-extra playwright-extra-plugin-stealth"
Recommendation

Use only on sites you own or are explicitly authorized to test. Avoid stealth/anti-detection features unless they are part of an authorized test, and require explicit user approval before logged-in actions.

What this means

A saved session file can let future automation act as the logged-in user, and anyone who obtains the file may be able to reuse that session.

Why it was flagged

The instructions show saving reusable authenticated browser state to a local file, but do not describe scoping, protection, deletion, or confirmation before later account use.

Skill content
// Save cookies/storage for reuse
await page.context().storageState({ path: './session.json' }); ... storageState: './session.json' ... // Already logged in!
Recommendation

Store session files only when necessary, keep them site-scoped and protected, delete them after use, and prompt the user before any action performed with a saved login.

What this means

Global unpinned packages can change over time and affect the local environment beyond this one skill.

Why it was flagged

The install steps are user-directed and purpose-aligned for Playwright, but they use global, unpinned npm installs and include an optional stealth dependency.

Skill content
npm install -g playwright ... npx playwright install ... npm install -g playwright-extra playwright-extra-plugin-stealth
Recommendation

Prefer a local project install, pin dependency versions where possible, and verify optional packages before installing them globally.