skills.rest
amanik
amanikCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

browse

Drive a headless browser to validate web flows and collect evidence.

Updated Mar 31, 2026
Search Tags:#automation#testing#qa#playwright#browser
One-click install
npx skills add https://github.com/amanik/sailor-score-debug --skill browse-amanik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/amanik/sailor-score-debug/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/amanik/sailor-score-debug --skill browse-amanik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automate QA testing by driving a headless browser to validate web flows and collect evidence.

Core Features & Use Cases

  • Automated navigation, element interaction, and page state verification for feature validation and bug reproduction.
  • Evidence collection through screenshots, DOM diffs, and logs (console, network, and dialogs) to accompany bug reports.
  • Hand-off capability to users in headed mode for manual inspection when automation hits edge cases.

Quick Start

Launch the browser, navigate to a URL, perform a simple action, and capture evidence.

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 web flows using a headless browser?▼

Automate QA testing by driving a headless browser to validate web flows, interact with elements, verify page states, and collect evidence like screenshots and logs for bug reports.

How do I collect evidence for bug reproduction during browser automation?▼

Collect bug reproduction evidence by capturing screenshots, DOM diffs, console logs, network logs, and dialog records during automated browser navigation and interaction.

Can I hand off a headless browser session to manual inspection when automation hits edge cases?▼

Yes, you can hand off the headless browser session to a headed mode for manual human inspection and interaction when automation encounters unexpected edge cases.

Do I need Playwright to drive a headless browser for feature validation?▼

Yes, Playwright-based browser control is required to drive deterministic actions, manage state restoration, and execute automated feature validation across multiple pages.

What is the best way to validate deployments and reproduce bugs across multiple pages?▼

The best way to validate deployments and reproduce bugs is using automated browser control to execute deterministic actions, verify page states, and restore state across multiple interactions.

Related Skills

Explore More Software Engineering Skills→
aresbitaresbit
46

agent-browser

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

Community
Intermediate
ComputerConnectionComputerConnection

browse

Drive a persistent headless Chromium browser for QA testing and site dogfooding.

Community
Advanced
4lerman4lerman

senior-devops

Automates DevOps workflows including CI/CD pipelines, infrastructure as code, and container deployments with rollback support.

Community
Advanced
Arupbiswas09Arupbiswas09

architecture-diagram

Generate dark-themed HTML and SVG architecture diagrams from text descriptions.

Community
Advanced