Agent skill · writing content · alirezarezvani
browser-automation
Automate a browser: scrape websites, fill forms, pull structured data from web pages. Use whenever the user wants to grab data from a site, fill a web form or extract a table. Browser testing: playwright-pro.
Why this skill is useful
Provides specific patterns and commands for web scraping and automation that the AI wouldn't reliably generate on its own.
What it needs
Requires playwright installed locally. About 6k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
Browser Automation - POWERFUL Overview The Browser Automation skill provides comprehensive tools and knowledge for building production-grade web automation workflows using Playwright. This skill covers data extraction, form filling, screenshot capture, session management, and anti-detection patterns for reliable browser automation at scale. When to use this skill: Scraping structured data from websites (tables, listings, search results) Automating multi-step browser workflows (login, fill forms, download files) Capturing screenshots or PDFs of web pages Extracting data from SPAs and JavaScript-heavy sites Building repeatable browser-based data pipelines When NOT to use this skill: Writing browser tests or E2E test suites — use playwright-pro instead Testing API endpoints — use api-test-suite-builder instead Load testing or performance benchmarking — use performance-profiler instead Why Playwright over Selenium or Puppeteer: Auto-wait built in — no explicit sleep() or waitForElement() needed for most actions Multi-browser from one API — Chromium, Firefox, WebKit with zero config changes Network interception — block ads, mock responses, capture API calls natively Browser contexts — isolated sessions without spinning up new browser instances Codegen — playwright codegen records your actions and generates scripts Async-first — Python async/await for high-throughput scraping Core Competencies 1. Web Scraping Patterns Selector priority (most to least reliable): 1. data-testid, data-id, or custom data attributes — stable across redesigns 2. #id selectors — unique but may change between deploys 3. Semantic selectors: article, nav, main, section — resilient to CSS changes 4. Class-based: .product-card, .price — brittle if classes are generated (e.g., CSS modules) 5. Positional: nth-child(), nth-of-type() — last resort, breaks on layout changes Use XPath only when CSS cannot express the relationship (e.g., ancestor traversal, text-based selection). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/browser-automation--4e61e6