browse

Automate website testing with persistent headless Chromium sessions.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill browse-jia-hong-peng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/Jia-Hong-Peng/jolike.com/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill browse-jia-hong-peng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, playwright-core, diff, and includes scripts (resource) components.

What problem does it solve?

Testing websites manually is slow and hard to reproduce. This Skill gives you a persistent headless Chromium browser that navigates pages, interacts with elements, and captures visual evidence in ~100ms per command.

Core Features & Use Cases

  • QA Testing & Dogfooding: Navigate any URL, click buttons, fill forms, and verify page state changes with snapshot diffs.
  • Visual Evidence: Take plain or annotated screenshots, check responsive layouts across mobile/tablet/desktop, and crop to specific elements.
  • Automation & Debugging: Handle dialogs, upload files, import cookies from real browsers, run JavaScript, and inspect CSS cascades via CDP.

Quick Start

Use the browse skill to navigate to your staging site, take an annotated screenshot of the homepage, and verify that the main content loads without console errors.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate web testing and capture screenshots with Playwright?

Automate web testing by using a persistent headless Chromium session to navigate URLs, interact with elements, and capture screenshots in about 100ms per command. It handles navigation, form filling, and visual evidence capture for QA workflows.

Can I check responsive layouts across mobile, tablet, and desktop during browser automation?

Responsive layout checks are supported across mobile, tablet, and desktop viewports. The browser automation captures plain or annotated screenshots and crops to specific elements to verify UI rendering across different screen sizes.

Does this browser automation tool support CSS inspection and dialog management?

CSS inspection and dialog management are fully supported. You can inspect CSS cascades via Chrome DevTools Protocol and handle browser dialogs programmatically while running automated website verification workflows.

Do I need Playwright installed to run headless Chromium sessions for QA testing?

Playwright is required as a dependency to run headless Chromium sessions for QA testing. The automation framework relies on Playwright and playwright-core to manage persistent browser contexts, element interaction, and navigation.

What is the best way to verify page state changes during deployment validation?

Verify page state changes by taking snapshot diffs after interacting with pages. This approach captures visual evidence of DOM updates and element state transitions to ensure deployment validation succeeds without manual reproduction.

Can I import cookies from a real browser into a headless Chromium session?

Importing cookies from real browsers into the headless Chromium session is supported. This allows the automated browser to inherit authenticated states and session data for testing behind login walls or testing staged environments.