browse

Drive automated QA browser tasks with navigation, interaction, and state checks.

37|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/DariusCorvus/iqualize --skill browse-dariuscorvus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/DariusCorvus/iqualize/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/DariusCorvus/iqualize --skill browse-dariuscorvus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automate QA browser tasks by driving a headless or headed browser to navigate, interact, and verify page state across web apps.

Core Features & Use Cases

  • Navigate, click, fill, and verify elements across pages with deterministic command execution.
  • Diff pages, capture annotated screenshots, and test responsive layouts for bug reproduction and regression checks.
  • Use for site dogfooding, feature verification, and bug reproduction by scripting end-to-end user flows.

Quick Start

Launch a session and issue commands like goto, click, and screenshot to automate a QA task.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate QA browser tasks for verifying web app page state?

Automate QA browser tasks by driving a headless or headed browser to execute deterministic command sequences that navigate, interact, and verify page state across web apps.

Can I capture annotated screenshots and generate diffs for bug reproduction?

Yes, you can capture annotated screenshots and generate page diffs for bug reproduction. The runtime verifies page states and documents visual regressions across responsive layouts.

Does this browser automation tool support complex UI flows and form interactions?

This browser automation tool supports complex UI flows and form interactions by executing deterministic commands like goto, click, and fill to script end-to-end user sequences.

How does the runtime handle sensitive inputs during automated testing?

The runtime handles sensitive inputs during automated testing by enforcing privacy through automatic redaction of sensitive data while logging activity for auditing and debugging purposes.

What is the best way to script end-to-end user flows for feature verification?

The best way to script end-to-end user flows for feature verification is to launch a session and issue deterministic commands like goto and click to drive navigation, interaction, and state checks.