browse

Drive a Playwright-backed headless browser to navigate pages and verify UI state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, curl, perl, shasum, git, playwright, and includes scripts (resource) components.

What problem does it solve?

Manual QA is slow and error-prone when testing web interfaces. This Skill provides a programmable browser to navigate pages, interact with elements, verify outcomes, and diff changes.

Core Features & Use Cases

  • Navigate to URLs and interact with UI elements
  • Capture diffs, take annotated screenshots, verify responsive layouts
  • Test forms, dialogs, and dynamic content across devices

Quick Start

Open a URL with a browse command, then run snapshot to generate an annotated view and compare results.

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 pages using a headless browser?

Automate QA testing by driving a headless browser to navigate URLs, interact with UI elements, and verify page state. This replaces slow manual testing with programmable validation for feature checks and regression suites.

Does Playwright support capturing annotated screenshots and visual diffs during web automation?

Playwright supports capturing annotated screenshots and generating visual diffs during web automation. You can snapshot pages, annotate views, and compare results to detect visual regressions across arbitrary URLs.

Can I test forms, dialogs, and responsive layouts across different devices with browser automation?

Browser automation allows you to test forms, dialogs, and dynamic content across responsive layouts. You can drive interactions and verify page states across different device simulations to ensure consistent UI behavior.

What dependencies do I need to run Playwright-based web automation and regression testing?

Playwright-based web automation requires a Playwright-backed browser, bun, curl, perl, shasum, and git. A frontmatter-driven SKILL.md loads operational instructions, with optional scripts, references, and assets loaded on demand.

What is the best way to reproduce web UI bugs using automated browser interactions?

The best way to reproduce web UI bugs is using automated browser interactions to navigate the problematic URL, trigger the specific element interactions, and capture the resulting page state for verification.