Playwright by Xiaomolong
v1.0.0Browser automation via Playwright MCP. Navigate websites, click elements, fill forms, take screenshots, extract data, and debug real browser workflows. Use w...
⭐ 0· 73·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Playwright + MCP browser automation) align with required binaries (node, npx) and the SKILL.md examples (npx @playwright/mcp, npx playwright, Playwright scripts). Nothing requested appears unrelated to browser automation.
Instruction Scope
SKILL.md explicitly documents running Playwright and MCP, codegen, tests, traces, screenshots, scraping patterns, and CI examples. It does not instruct reading arbitrary user files, exfiltrating secrets, or calling external endpoints unrelated to browser automation. Example references to env vars and auth files are standard examples for Playwright usage.
Install Mechanism
The registry lists no formal install spec (instruction-only), but SKILL.md examples use npx to fetch/execute packages (playwright, @playwright/mcp). Using npx is expected for this functionality but will download and run code from npm at runtime — normal for Playwright but a surface to be aware of.
Credentials
The skill declares no required environment variables or credentials. Examples reference common envs (BASE_URL, CI, process.env.CI) and an example auth file path; these are illustrative and proportionate to E2E/browser testing tasks.
Persistence & Privilege
always:false and default autonomous invocation settings are appropriate. The skill is instruction-only and states it does not create persistent profiles by default. No indication it modifies other skills or requests permanent elevated presence.
Assessment
This skill is coherent for Playwright-based browser automation. Before installing/using: (1) be aware npx will fetch and run npm packages at runtime (normal here); (2) do not provide sensitive credentials to any automation unless necessary — avoid embedding secrets in saved auth files; (3) review any CI or script snippets before running (they may install browsers or run tests that download artifacts); and (4) if you plan to persist auth/session files, confirm you understand where they are stored and who can access them. If you need broader assurance, request an explicit install script or signed package source (e.g., known GitHub release) rather than relying on on-the-fly npx execution.Like a lobster shell, security has layers — review code before you run it.
automationvk97a1a6nbr6ndwtvtexm94bf1h83gygzbrowservk97a1a6nbr6ndwtvtexm94bf1h83gygzlatestvk97a1a6nbr6ndwtvtexm94bf1h83gygzscrapingvk97a1a6nbr6ndwtvtexm94bf1h83gygzwebvk97a1a6nbr6ndwtvtexm94bf1h83gygz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
P Clawdis
OSLinux · macOS · Windows
Binsnode, npx