skills.rest
yocxy2
yocxy2COMMUNITY
Explore all skills by this author →
GitHub

browse

Operate a headless Chromium browser for automated QA testing and site interaction.

Updated Jul 26, 2026
Search Tags:#automation#testing#qa#browser#headless#chromium
One-click install
npx skills add https://github.com/yocxy2/gstack3 --skill browse-yocxy2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/yocxy2/gstack3/tree/main/browse
Command: npx skills add https://github.com/yocxy2/gstack3 --skill browse-yocxy2

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the difficulty of testing modern, dynamic web applications that rely on complex JavaScript, portals, and non-semantic elements which standard accessibility tools often miss.

Core Features & Use Cases

  • Interactive Element Detection: Automatically identifies clickable elements, including those hidden in portals or lacking ARIA roles.
  • Visual & State Verification: Supports annotated screenshots, responsive layout testing, and DOM diffing to verify UI changes.
  • Use Case: Use this skill to dogfood a new feature deployment by navigating the site, filling out forms, and asserting that the dashboard state updates correctly after submission.

Quick Start

Use the browse skill to navigate to the application URL and take an annotated 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 QA testing for dynamic web applications with complex JavaScript?▼

Automated QA testing for dynamic web applications is handled through a persistent headless Chromium environment that supports navigation, element manipulation, and visual state verification across JavaScript-heavy portals.

Can headless browser testing detect interactive elements hidden in portals without ARIA roles?▼

Headless browser testing detects non-semantic interactive elements by automatically scanning for clickable components, including those hidden in portals or lacking ARIA roles that standard accessibility tools often miss.

How do I verify UI state changes after form submission in a headless Chromium environment?▼

Verifying UI state changes in headless Chromium involves navigating the application, filling out forms, and asserting dashboard updates using annotated screenshots, responsive layout testing, and DOM diffing.

Does Playwright support automated visual state verification and DOM diffing for site testing?▼

Playwright supports automated visual state verification by enabling annotated screenshots, responsive layout testing, and DOM diffing to verify UI changes within a persistent headless Chromium environment.

What is the best way to dogfood a new feature deployment using headless browser automation?▼

Dogfooding a new feature deployment with headless browser automation requires navigating the target site, interacting with forms, and asserting state updates to verify the deployment functions correctly under real conditions.

What are the limitations of automated testing for non-semantic interactive elements in portal-based UIs?▼

Automated testing for non-semantic interactive elements in portal-based UIs faces limitations when standard accessibility tools fail to identify components, requiring advanced scanning techniques to detect elements lacking ARIA roles.

Related Skills

Explore More Software Engineering Skills→
a29paula29paul
1

gstack

Automate website testing and deployment verification with persistent headless browser control.

Community
Advanced
JaykaijackJaykaijack

browse

Automate headless Chromium browsing and UI verification with screenshots and diffs.

Community
Advanced
ruska-airuska-ai
17

agent-browser

Automate browser navigation, form filling, screenshots, and data extraction via agent-browser CLI.

Official
Advanced
i-standard1i-standard1
6

browse

Report visible elements, layout, and accessibility structure of a web page.

Official
Intermediate