What problem does it solve? Browser automation work often fails from conflated Playwright and Puppeteer APIs, missing browser binaries on CI hosts, unstable selectors, and missing diagnostic evidence when tests fail. This Skill provides a structured procedure for choosing the right framework, installing browsers explicitly, writing stable locators, and capturing failure evidence. ## Core Features & Use Cases - Framework Selection: Decision rules for choosing Playwright (test-runner workflows, cross-browser projects, UI mode) versus Puppeteer (focused JavaScript browser-control scripts), with escalation to CDP-level work when needed. - Environment and CI Setup: Explicit browser binary installation in local and CI environments, cache policy, artifact retention, and retry policy guidance. - Diagnostics and Evidence: Standards for capturing traces, screenshots, video, console, and network logs proportionate to failures, with secrets redacted. - Use Case: A team setting up a Playwright E2E suite in GitHub Actions uses this Skill to install browsers deterministically, configure stable locators, and retain trace artifacts for every failed run. ## Quick Start Use the browser-automation-stinger skill to help me set up a Playwright test suite with CI browser installation and trace capture on failure.
