Automate headless Chromium browser testing and capture visual evidence.
npx skills add https://github.com/kk20300113-png/my-claude-skills --skill browse-kk20300113-png
Please help me install this Agent Skill. Skill: browse Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/browse Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill browse-kk20300113-png
Manually testing web applications, verifying post-deployment functionality, and gathering visual evidence for bugs is slow, inconsistent, and hard to reproduce. This skill automates those tasks with a persistent headless Chromium browser that executes commands in ~100ms, eliminating repetitive manual work and providing consistent, shareable test results.
Use the browse skill to test your production site's checkout flow, confirm all form fields and payment steps work correctly, and capture an annotated screenshot of the completed purchase page to attach to your QA report if any issues are found.
High-intent search queries and answers about installing and using this skill.
Automate headless browser testing by using a persistent Chromium session to navigate URLs, interact with page elements, and execute commands in ~100ms. This replaces slow manual QA work with consistent, reproducible visual verification across deployment and user flow scenarios.
Yes, you can capture screenshots for bug reporting during user flow testing. The tool takes plain or annotated screenshots, diffs page states before and after actions, and pulls console or network logs to provide detailed, shareable bug evidence.
Headless browser automation supports responsive layout testing across mobile, tablet, and desktop viewports. You can validate form submissions, file uploads, dialogs, and complex multi-step interactions within any designated screen size.
The best way to verify deployments without manual QA is automating a headless Chromium browser to dogfood end-to-end user flows. It provides persistent session state to validate post-deployment functionality and confirm new features work as expected.
Yes, you can test complex user interactions like OAuth handoffs in a headless browser. The automation supports multi-step forms, file uploads, dialog validation, and persistent session state required for completing authentication handoffs.
robertzengcnControl a persistent headless Chromium browser for automated QA testing.
Intension-usDrive headless browsers to load URLs, interact with elements, and verify page state.
smallnestAutomate browser tasks and testing with Playwright for web QA.
KubrickCodeDesign REST API endpoints with pagination, sorting, and RFC 7807 error responses.
