browse

Automate browser-based QA testing with headless Chromium navigation and screenshots.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Santiagoisper/BOPE_VERSION_DEFINITIVA --skill browse-santiagoisper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/Santiagoisper/BOPE_VERSION_DEFINITIVA/tree/main/.agents/skills/gstack/browse
Command: npx skills add https://github.com/Santiagoisper/BOPE_VERSION_DEFINITIVA --skill browse-santiagoisper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines QA testing and site dogfooding by providing a fast headless browser for automated interactions, state verification, and screenshot capture.

Core Features & Use Cases

  • Headless Browser Automation: Navigate, interact with elements, verify page states, and take screenshots without a graphical interface.
  • Responsive Layout Testing: Check website layouts on different devices and viewport sizes.
  • Form Testing and Uploads: Test forms, file uploads, and dialogs for functionality.
  • Use Case: Suppose you have a new product page that you want to QA before launch. Use this Skill to navigate through the entire user journey, fill out forms, upload files, and take screenshots to identify any issues.

Quick Start

Use the browse skill to navigate to 'https://yourapp.com' and take a screenshot of the main page.

Frequently Asked Questions about browse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate headless browser testing for website QA?

Perform responsive layout testing by configuring the headless browser with different device viewport sizes. This allows you to check website layouts across multiple screen dimensions and verify responsive design behavior without manual inspection.

Can I test forms and file uploads with a headless browser?

You can test forms and file uploads with a headless browser by automating interactions with input elements and dialogs. The automation script handles form submissions and file upload functionality to verify correct user journey behavior.

Does browser automation work with Playwright for deployment verification?

Browser automation works with Playwright to execute deployment verification by navigating through user journeys and verifying page states. It leverages Playwright interaction libraries to control the headless Chromium instance and capture debugging screenshots.

What is the best way to capture screenshots for UI testing without a display?

The best way to capture screenshots for UI testing without a display is using a headless Chromium instance. It operates without a graphical interface to capture page states throughout the automated navigation process for effective debugging.

Are there limitations when verifying page states with headless browser automation?

Limitations when verifying page states with headless browser automation include the inability to visually catch rendering issues dependent on a graphical interface. Headless execution focuses on functional state verification and screenshot capture rather than visual rendering inspection.