domains / families / software-engineering / playwright

playwright

combined

Browser automation and web scraping with Playwright. Forms, screenshots, data extraction. Works standalone or via MCP. Testing included. Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

When to use

• **Scrape a website** (static or JavaScript-rendered)
• **Automate form filling** (login, checkout, data entry)
• **Test a web application** (E2E tests, visual regression)
• **Take screenshots or PDFs** of web pages
• **Extract data** from tables, lists, or dynamic content
• This skill is applicable to execute the workflow or actions described in the overview.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The copies describe three different Playwright automation procedures. The first two are identical and drive a real browser via a terminal CLI wrapper (playwright-cli) with snapshot-based element refs. The third writes custom Playwright JavaScript to /tmp and executes it via a local run.js, with dev-server detection. The fourth is a general Playwright/MCP/scraper guide focused on selectors, scraping, and MCP server setup. Crowning one would hide the CLI-first, script-execution, and MCP/scraping alternatives.