← Back to Skills Marketplace
498
Downloads
0
Stars
6
Active Installs
1
Versions
Install in OpenClaw
/install playwright-mcp-skill
Description
Run browser automation through @playwright/mcp over UXC stdio MCP, with daemon-friendly session reuse and safe action guardrails. Use when tasks need determi...
Usage Guidance
This skill appears to do what it says (drive Playwright MCP over uxc/npx) but has some concerning gaps. Before installing or running it: 1) review and decide whether you trust on-demand npm execution (npx @playwright/mcp@latest); consider pinning a specific version instead of @latest; 2) be aware the skill suggests creating persistent CLI links and a profile directory (~/.uxc/playwright-profile) that will store session state (cookies/tokens) — only use shared-profile mode if you understand and accept persistent credentials; 3) note the docs reference UXC_DAEMON_EXCLUSIVE though no env vars are declared — verify what your environment will expose to the CLI and whether the skill will read/write that path; 4) run first-time usage in an isolated environment (container or VM) if you want to limit potential exposure from remote package fetches; and 5) if you lack trust in the @playwright/mcp source, inspect the package or vendor a vetted binary instead of relying on npx @latest.
Capability Analysis
Type: OpenClaw Skill
Name: playwright-mcp-skill
Version: 1.0.0
The skill is classified as suspicious due to its inherent high-risk capabilities, despite including guardrails. It utilizes `npx -y @playwright/mcp@latest` (SKILL.md, references/usage-patterns.md), introducing a supply chain risk by fetching and executing the latest version of an external package. The `browser_run_code` operation (references/usage-patterns.md) allows arbitrary JavaScript execution within the browser, a powerful feature that could be abused if the agent were compromised. Additionally, the `uxc daemon stop` command (SKILL.md, references/usage-patterns.md) is used for process management, which, depending on the `uxc` implementation, could have broader implications. While these capabilities are aligned with browser automation, they present significant vulnerabilities without clear evidence of intentional malicious behavior from the skill's author.
Capability Assessment
Purpose & Capability
Name/description, CLI examples, and uxc link guidance align with the stated goal of running @playwright/mcp via stdio. However the docs repeatedly reference a shared profile directory (~/.uxc/playwright-profile) and a daemon-exclusive env var (UXC_DAEMON_EXCLUSIVE) even though the skill metadata declares no config paths or env requirements — that's an unexplained config access pattern.
Instruction Scope
The SKILL.md instructs the agent to create fixed CLI links (uxc link), manipulate a local profile directory (~/.uxc/playwright-profile), stop the uxc daemon, and suggests setting UXC_DAEMON_EXCLUSIVE — these are side effects beyond simple stateless automation. The skill references an environment variable (UXC_DAEMON_EXCLUSIVE) and a filesystem path but the public requirements do not declare those, and the instructions grant the skill authority to read/write persistent profile state.
Install Mechanism
There is no install spec in the registry (instruction-only). Runtime execution relies on npx -y @playwright/mcp@latest which will fetch and run code from npm on first use. This is expected for a Node CLI integration but is a moderate operational risk (remote code execution on first run) and would be safer if a pinned version or explicit install step were recommended.
Credentials
The skill declares no required env vars but the docs reference UXC_DAEMON_EXCLUSIVE and instruct storing user-data under ~/.uxc/playwright-profile. Requesting or relying on a persistent user-data-dir can expose cookies/tokens and is not declared in metadata; absence of declared env/config requirements is an inconsistency.
Persistence & Privilege
always is false and model invocation is allowed (normal). The skill's recommended setup creates persistent CLI links (uxc link) and optional shared-profile storage, which gives it ongoing presence (stored profile data and created command wrappers). This is plausible for the use case but increases the blast radius compared to a purely ephemeral workflow.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install playwright-mcp-skill - After installation, invoke the skill by name or use
/playwright-mcp-skill - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of playwright-mcp-skill for deterministic browser automation via @playwright/mcp over UXC stdio MCP.
- Supports daemon-friendly session reuse and safe action guardrails.
- Default workflow includes headless, isolated sessions; persistent shared profiles are optionally supported.
- Provides fixed command linking with `playwright-mcp-cli` for streamlined usage.
- Enforces JSON envelope protocol parsing and explicit guardrails for safe browser actions.
- Designed for CLI integration with prerequisites for Node.js, npx, and uxc.
Metadata
Frequently Asked Questions
What is Playwright Mcp Skill?
Run browser automation through @playwright/mcp over UXC stdio MCP, with daemon-friendly session reuse and safe action guardrails. Use when tasks need determi... It is an AI Agent Skill for Claude Code / OpenClaw, with 498 downloads so far.
How do I install Playwright Mcp Skill?
Run "/install playwright-mcp-skill" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Playwright Mcp Skill free?
Yes, Playwright Mcp Skill is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Playwright Mcp Skill support?
Playwright Mcp Skill is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Playwright Mcp Skill?
It is built and maintained by jolestar (@jolestar); the current version is v1.0.0.
More Skills