Skip to main content
hc
Submit
skillsFirst-partyReview first Safety ✓ Privacy ✓

Playwright MCP Browser Automation Engineer Skill

Build resilient browser automations using Playwright MCP with robust selectors, retries, and deterministic task execution.

by JSONbored·added 2026-04-10·
Claude CodeCodexWindsurfGeminiCursorCLI
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:advancedType:generalVerified:draft
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/skills/playwright-mcp-browser-automation-engineer
Source URLs
https://playwright.dev/docs/getting-started-mcp, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/playwright-mcp-browser-automation-engineer.mdx
Package URL
/downloads/skills/playwright-mcp-browser-automation-engineer.zip
Package SHA256
debb75ce2997bba8fcd5fbe24eb7b8cae6cfec0f34f8619611134906f2993b1e
Safety notes
Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions., Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
Privacy notes
Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots., Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
Platform compatibility
claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
Author
JSONbored
Claim status
unclaimed
Last verified
2026-04-10

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as first-party.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    Package marked verified.

    Done

  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

Install command

Provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

3 to clear

Platforms

6 listed

Difficulty

75/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    Listing has review metadata.

    Done

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup. Have accounts and credentials ready first.

0/3 ready
Account & credentials1Configuration1General1

Safety & privacy surface

Safety & privacy surface

2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens.

3 areas
  • SafetyExecution & processesCan design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
  • SafetyCredentials & tokensKeep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
  • PrivacyData retentionInputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
  • PrivacyCredentials & tokensRedact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.

Safety notes

  • Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
  • Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.

Privacy notes

  • Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
  • Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.

Prerequisites

  • Browser automation target URL(s)
  • Playwright MCP server configured in your agent environment
  • Test credentials with least required permissions

Schema details

Install type
package
Reading time
7 min
Difficulty score
75
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
debb75ce2997bba8fcd5fbe24eb7b8cae6cfec0f34f8619611134906f2993b1e
Skill and platform metadata
Skill type
general
Skill level
advanced
Verification
draft
Verified at
2026-04-10
Retrieval sources
https://playwright.dev/docs/getting-started-mcp
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Use the Playwright MCP browser automation engineer skill for this workflow."

# Required output
1) Action graph with checkpoints
2) Stable selector strategy
3) Retry/fallback logic
4) Failure artifact plan (trace, screenshot, logs)

About this resource

Overview

This skill turns browser automation requests into deterministic workflows. It emphasizes robust selectors, explicit waits, idempotent actions, and forensic artifacts for fast debugging.

Compatibility

Native

  • Claude Code / Claude: native skill usage via SKILL.md.
  • Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.

Manual Adaptation

  • Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
  • Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
  • OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.

Prerequisites

  • Stable environment URLs (dev/stage/prod)
  • Clear task objective and completion criteria
  • Permission-safe test accounts

What This Skill Delivers

  • Workflow decomposition into atomic browser steps
  • Selector hierarchy strategy (semantic > role > data attr > css fallback)
  • Retry/backoff and timeout policy
  • Artifact capture plan for diagnostics

How to Use This Skill

  1. Define task intent and completion assertions.
  2. Build selector map with priority/fallback order.
  3. Add deterministic waits and post-action checks.
  4. Attach failure artifacts for every critical step.
  5. Run replay validation to verify flake resistance.

Troubleshooting

Issue: Selectors break after UI updates
Fix: Prefer role/data attributes and maintain fallback selector chains.

Issue: Workflow fails intermittently
Fix: Replace fixed sleeps with condition-based waits and bounded retries.

Issue: Hard to diagnose failures
Fix: Persist trace, screenshot, and action logs per step with correlation IDs.

Knowledge Freshness

Treat tooling details as time-sensitive. Re-validate APIs, limits, pricing, auth models, and deployment flags immediately before implementation. If docs conflict with prior memory, follow current official docs and release notes.

Retrieval Sources

Output Contract

  1. Return a concrete plan with implementation order.
  2. Provide production-ready commands/config/code snippets (not placeholders).
  3. Include explicit assumptions and unresolved risks.
  4. Include a verification checklist with pass/fail criteria.

Quality Gates

  • All commands are copy/paste ready.
  • Security-sensitive steps call out secret handling and least privilege.
  • Version-sensitive guidance cites current docs used.
  • Rollback path is included for risky changes.
  • Final output includes quick validation commands/tests.
#playwright#mcp#browser-automation#testing#ai-agents

Source citations

Add this badge to your README

Show that Playwright MCP Browser Automation Engineer Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/skills/playwright-mcp-browser-automation-engineer.svg)](https://heyclau.de/entry/skills/playwright-mcp-browser-automation-engineer)

How it compares

Playwright MCP Browser Automation Engineer Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Field
Playwright MCP Browser Automation Engineer Skill

Build resilient browser automations using Playwright MCP with robust selectors, retries, and deterministic task execution.

Open dossier
Browser Agent Workflow Automation Skill

Build robust browser automation workflows for AI agents with deterministic selectors, retries, and safe action boundaries.

Open dossier
Playwright E2E Testing Automation Skill

Write and maintain reliable end-to-end tests with Playwright — Microsoft's browser automation library that auto-waits for actionable elements and runs the same suite against Chromium, Firefox, and WebKit.

Open dossier
Playwright Trace Failure Triage Capability Pack Skill

Expert skill for reviewing Playwright trace artifacts, screenshots, action timelines, network events, retries, and CI evidence to classify flaky browser test failures without guessing from logs alone.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage verified2026-04-10Package verified2026-04-10Package verified2025-10-16Package not verified
Source provenanceDiffersSource-backedNo submission linkNo submission linkSource-backed
SubmitterDiffers———JSONbored
Install riskReview firstLow riskLow riskReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand————
Categoryskillsskillsskillsskills
Sourcefirst-partyfirst-partyfirst-partysource-backed
AuthorJSONboredJSONboredJSONboredJSONbored
Added2026-04-102026-04-102025-10-162026-06-05
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo————
Safety notes✓Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions. Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.✓Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions. Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.✓`npx playwright install --with-deps` downloads browser binaries (~500 MB for Chromium, Firefox, and WebKit) from Playwright's CDN and on Linux installs system-level packages. Review your network and environment policies before running in restricted infrastructure. Generated tests have full browser-level access to any URL they target. Review test scripts before running them against authenticated sessions or production environments — Playwright can submit forms, click buttons, and make network requests as a real user.✓Trace artifacts can include screenshots, DOM text, URLs, request metadata, console output, and application state; review them before sharing publicly. Do not fix a trace-only symptom by adding broad waits, retries, or timeouts unless the trace evidence supports that change. Keep destructive browser actions and production-like credentials out of replayed failure reproduction.
Privacy notes✓Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots. Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.✓Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots. Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.✓Playwright runs entirely on your local machine. Traces, screenshots, and HTML test reports are written to local disk only and are not uploaded to Microsoft or any external service. Trace files and failure screenshots may capture sensitive content from the application under test (form data, rendered PII, session tokens visible in URLs). Store and rotate these files appropriately.✓Playwright traces can expose user names, emails, tokens in URLs, internal hostnames, test data, screenshots, and API payload fragments. Public PR comments should summarize trace evidence without uploading private trace files or pasting sensitive network details.
Prerequisites
  • Browser automation target URL(s)
  • Playwright MCP server configured in your agent environment
  • Test credentials with least required permissions
  • Target web workflow with clear start and success states
  • Ability to run browser automation in local or CI environment
  • Access to auth/session strategy if login is required
  • Node.js 18+
  • Playwright 1.40+ with the @playwright/test package
  • Browser binaries installed via `npx playwright install` (Chromium, Firefox, WebKit)
  • A web application accessible for testing (local dev server, staging, or production URL)
  • Playwright test failure, trace artifact, test report, or CI run under review.
  • Access to test source, Playwright config, browser/project name, retry settings, and relevant artifacts.
  • Permission to inspect screenshots, DOM snapshots, console logs, network events, and request/response metadata.
Install
curl -L https://heyclau.de/downloads/skills/playwright-mcp-browser-automation-engineer.zip -o playwright-mcp-browser-automation-engineer.zip && unzip -o playwright-mcp-browser-automation-engineer.zip -d ./playwright-mcp-browser-automation-engineer
curl -L https://heyclau.de/downloads/skills/browser-agent-workflow-automation.zip -o browser-agent-workflow-automation.zip && unzip -o browser-agent-workflow-automation.zip -d ./browser-agent-workflow-automation
npx playwright install --with-deps
npm init playwright@latest
Config————
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Microsoft logoguides

Microsoft AI Agents for Beginners

Learn AI agents through Microsoft's course covering frameworks, design patterns, tool use, agentic RAG, production, protocols, memory, and security.

Review firstSource-backedReview firstAdded 26d ago
Safety ✓ Privacy ✓by Microsoft
guides

Auditing MCP Client Configuration Before Team Rollout

Audit MCP client configuration before sharing it with a team.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by YB0y
guides

Building In-Process MCP Tools with the Claude Agent SDK

Define in-process MCP tools for the Claude Agent SDK with createSdkMcpServer and the tool helper, then wire them into query.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by JPette1783

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.