Find your next open-source project

Search by name, purpose, or keyword — or paste a GitHub repository URL
All skills

browser-automation

Write browser tests that use semantic locators, bounded waits, and isolated test data to verify UI outcomes.

When to use it

You have a web app flow to check and need a reliable automated test instead of fragile CSS selectors that break on layout changes.

For example

You say

Use browser-automation to write a Playwright test for my local shop app: adding an item updates the cart count, and removing it shows an empty cart.

You get
  • Playwright test file
  • Role-based locators
  • Isolated cart assertions

How it works

  • Prefers role, label, and text locators over CSS or XPath tied to page structure.
  • Warns that retrying actions like checkout or deletion can duplicate side effects, so state is checked first.
  • Screenshots, traces, and auth-state files may hold private data, so capture only the authorized scope.

Before installing

A browser automation tool (Playwright, Puppeteer, or Selenium) must already be installed in the project or selected by the user; the skill installs no browser or service.