| name | Playwright (Automation + MCP + Scraper) |
| slug | playwright |
| version | 1.0.3 |
| homepage | https://clawic.com/skills/playwright |
| description | Browser automation via Playwright MCP. Navigate websites, click elements, fill forms, take screenshots, extract data, and debug real browser workflows. Use when (1) you need a real browser, not static fetch; (2) the task involves Playwright MCP, browser tools, Playwright tests, scripts, or JS-rendered pages; (3) the user wants navigation, forms, screenshots, PDFs, downloads, or browser-driven extraction turned into a reliable outcome. |
| whenToUse | User needs real browser automation: JS-rendered pages, multi-step forms, screenshots, PDFs, or Playwright tests |
| changelog | Clarified the MCP-first browser automation flow and improved quick-start guidance for forms, screenshots, and extraction. |
| metadata | {"clawdbot":{"emoji":"P","requires":{"bins":["node","npx"]},"os":["linux","darwin","win32"],"install":[{"id":"npm-playwright","kind":"npm","package":"playwright","bins":["playwright"],"label":"Install Playwright"},{"id":"npm-playwright-mcp","kind":"npm","package":"@playwright/mcp","bins":["playwright-mcp"],"label":"Install Playwright MCP (optional)"}]}} |
When to Use
Use this skill for real browser tasks: JS-rendered pages, multi-step forms, screenshots or PDFs, UI debugging, Playwright test authoring, MCP-driven browser control, and structured extraction from rendered pages.
Prefer it when static fetch is insufficient or when the task depends on browser events, visible DOM state, authentication context, uploads or downloads, or user-facing rendering.
If the user mainly wants the agent to drive a browser with simple actions like navigate, click, fill, screenshot, download, or extract, treat MCP as a first-class path.
Use direct Playwright for scripts and tests. Use MCP when browser tools are already in the loop, the user explicitly wants MCP, or the fastest path is browser actions rather than writing new automation code.
Primary fit is repo-owned browser work: tests, debugging, repros, screenshots, and deterministic automation. Treat rendered-page extraction as a secondary use case, not the default identity.
Architecture
This skill is instruction-only. It does not create local memory, setup folders, or persistent profiles by default.
Load only the smallest reference file needed for the task. Keep auth state temporary unless the repository already standardizes it and the user explicitly wants browser-session reuse.
Quick Start
MCP browser path
npx @playwright/mcp --headless
Use this path when the agent already has browser tools available or the user wants browser automation without writing new Playwright code.
Common MCP actions
Typical Playwright MCP tool actions include:
browser_navigate for opening a pagebrowser_click and browser_press for interactionbrowser_type and browser_select_option for formsbrowser_snapshot and browser_evaluate for inspection and extractionbrowser_choose_file for uploads- screenshot, PDF, trace, and download capture through the active browser workflow
Common browser outcomes
| Goal | Typical MCP-style action |
|---|
| Open and inspect a site | navigate, wait, inspect, screenshot |
| Complete a form | navigate, click, fill, select, submit |
| Capture evidence | screenshot, PDF, download, trace |
|
