Load URLs in a headless browser and interact with UI elements to verify behavior.
npx skills add https://github.com/mi179/claude-skills --skill browse-mi179
Please help me install this Agent Skill. Skill: browse Source: https://github.com/mi179/claude-skills/tree/main/user/gstack/browse Command: npx skills add https://github.com/mi179/claude-skills --skill browse-mi179
Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states.
Invoke it to load a page, perform interactions, and capture a screenshot for evidence.
High-intent search queries and answers about installing and using this skill.
Automated QA testing for forms and uploads uses a headless browser to navigate URLs, interact with UI elements, and verify behavior without a graphical interface. You can validate form submissions, file uploads, and dialog handling while capturing annotated screenshots as evidence.
Yes, you can test responsive layouts across devices using Playwright. The skill loads URLs in a headless browser to verify page states and diff layouts before and after interactions, ensuring your UI adapts correctly across multiple device viewports.
Headless browser testing in software engineering is used to load web pages, interact with UI elements, and verify page state without rendering a visible UI. It automates QA flows to assert element states, handle dialogs, and capture visual evidence for site dogfooding.
Yes, a running daemon and token are required to drive headless browser commands. The skill relies on these prerequisites to execute Playwright automation flows, load URLs, and interact with page elements during your QA testing sessions.
To capture annotated screenshots and diffs during browser automation, the skill loads a URL in a headless browser, performs UI interactions, and documents the results. It records the page state before and after actions to provide visual evidence of behavior.
The best way to verify UI behavior without a GUI is using a headless browser to automate QA flows. You load a URL, interact with elements, and assert page states to confirm forms, dialogs, and uploads function correctly before deployment.
Chang-Shih-YungRun a persistent headless Chromium daemon with Playwright under Bun via HTTP.
concept2cureDrive a headless browser to validate page state and capture visual diffs.
dandawateyAutomate end-to-end web application testing with Playwright.
machenjieDefine frontend tests for user-visible behavior across roles and UI states.
