browse

Automate headless browser navigation, interaction, and visual verification with Playwright-based Chromium.

Updated Jul 21, 2025
One-click install
npx skills add https://github.com/robertzengcn/aiFetchly --skill browse-robertzengcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/robertzengcn/aiFetchly/tree/main/.agents/skills/gstack/browse
Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill browse-robertzengcn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manual browser testing is slow and hard to reproduce, while capturing visual evidence for bugs requires juggling multiple tools and manual steps. This Skill replaces that workflow with a fast, scriptable headless browser that automates navigation, interaction, and verification.

Core Features & Use Cases

  • Instant Browser Automation: Navigate to any URL, click elements, fill forms, and verify page state in ~100ms per command.
  • Visual Bug Reporting: Take annotated screenshots, diff before/after states, and capture console and network logs for evidence.
  • Responsive & Accessibility Testing: Check layouts across viewports, validate ARIA trees, and test dialogs or file uploads.
  • Use Case: A developer verifying a deployment can snapshot the homepage, click through the login flow, diff the dashboard before and after a data load, and capture a screenshot of any layout issues all in one continuous session.

Quick Start

Use the browse skill to navigate to your application's login page, fill in the test credentials, and take an annotated screenshot of the dashboard to verify the deployment succeeded.

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 web applications?

Headless browser testing automates navigation, interaction, and visual verification using Playwright-based Chromium. You can navigate to any URL, click elements, fill forms, and verify page state in approximately 100ms per command without manual browser operation.

How to capture annotated screenshots for bug reports during QA testing?

Annotated screenshots for bug reports are captured by taking snapshot references, diffing before and after states, and collecting console and network logs. This provides visual evidence of layout issues or unexpected behavior during a continuous testing session.

Can I use Playwright to check responsive layouts across different viewports?

Playwright supports responsive layout checks across various viewports. The automation validates page behavior, tests dialogs or file uploads, and inspects ARIA trees to ensure accessibility and layout consistency without opening a manual browser window.

What is the best way to verify deployment success without manual browser checks?

Deployment verification is best handled by automating a headless browser session to snapshot the homepage, click through the login flow, diff the dashboard before and after a data load, and capture screenshots of any layout issues.

Does headless browser automation work for validating forms and capturing console logs?

Headless browser automation validates forms by filling in test credentials and verifying page state. It simultaneously captures console and network logs alongside annotated screenshots to provide comprehensive evidence for QA testing.

Are there limitations when using a headless browser for visual verification?

Visual verification using a headless browser relies on snapshot references and state diff capabilities. It requires Playwright-based Chromium automation and does not support manual browser operation, limiting its use to scriptable automated workflows.