browse

Automate browser-based QA testing with persistent headless Chromium sessions.

Updated May 22, 2026
One-click install
npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill browse-shekerkamma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/shekerkamma/peopletech-marketplace/tree/main/plugins/gstack/browse
Command: npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill browse-shekerkamma

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manual browser testing is slow and error-prone. Verifying deployments, testing user flows, and capturing visual evidence requires switching between tools and contexts. This skill eliminates that friction by providing a persistent headless browser that navigates, interacts, and captures state in milliseconds.

Core Features & Use Cases

  • Persistent Browser Sessions: Maintains cookies, tabs, and login state across commands for realistic multi-step testing.
  • Visual & DOM Inspection: Take annotated screenshots, diff page states, inspect CSS cascades via CDP, and extract structured data from any URL.
  • Interaction & Assertions: Click elements, fill forms, handle dialogs, and assert element states (visible, enabled, checked) to validate user flows end-to-end.
  • Use Case: A developer can verify a deployment by navigating to the staging environment, snapshotting interactive elements, clicking through a login flow, and capturing a before/after diff to confirm the feature works.

Quick Start

Use the browse skill to navigate to your application URL, capture an interactive snapshot of the page elements, and take an annotated screenshot to verify the current state.

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 deployment validation?

Headless browser testing for deployment validation is automated by navigating to staging environments, interacting with user flows, and capturing annotated screenshots to verify application state. This skill uses persistent Chromium sessions to maintain login state across multi-step tests.

Can I take annotated screenshots and diff page states using Playwright?

Yes, you can take annotated screenshots and diff page states using Playwright. The skill captures visual snapshots during browser automation and generates before/after diffs to confirm feature changes and collect visual bug report evidence.

How do I inspect CSS cascades via CDP during web testing?

You inspect CSS cascades by leveraging Chrome DevTools Protocol (CDP) integration during headless browser sessions. This allows direct CSS inspection of web elements while executing QA testing flows and capturing structured page data.

Does this browser automation tool support persistent sessions with cookies?

Yes, browser automation supports persistent sessions that maintain cookies, tabs, and login state across commands. It also allows cookie import from real browsers to enable realistic multi-step testing of authenticated user flows.

What is the best way to test responsive layouts across mobile and desktop viewports?

Responsive layout testing across mobile and desktop viewports is handled by configuring the headless Chromium session to emulate different screen sizes. The skill captures annotated screenshots at each viewport to verify layout adaptation.

Can I handle dialogs and assert element states during end-to-end QA testing?

Yes, you can handle dialogs, fill forms, click elements, and assert element states during end-to-end QA testing. The skill validates whether elements are visible, enabled, or checked to confirm user flows work correctly.