browse

Name: browse
Availability: InStock
Author: sealion-hub

Create persistent headless browser sessions for automated web QA testing.

Updated Feb 16, 2026

Search Tags:#automation #testing #QA #playwright #headless #browsing #browse

Ready to run

npx skills add https://github.com/SeaLion-hub/DICEE --skill browse-sealion-hub

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/SeaLion-hub/DICEE/tree/main/.agents/skills/gstack/browse
Command: npx skills add https://github.com/SeaLion-hub/DICEE --skill browse-sealion-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual QA and bug reproduction slow release cycles. This skill provides a persistent headless browser to automate repetitive site testing, capture evidence, and reproduce issues quickly.

Core Features & Use Cases

Persistent headless Chromium maintains state (cookies, tabs, and login sessions) across commands for seamless long-running tests.
Automated interactions supports navigation, form filling, dialogs, diffing page states, and annotated screenshots to validate behavior.
Dogfooding & demos enables rapid QA feedback during deployment, previews, and CI workflows by replaying user flows with evidence.

Quick Start

Load the skill and start by navigating to a page with goto and capture a snapshot to verify state.

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 with a persistent headless browser?▼

Automate QA testing by launching a persistent headless Chromium session that maintains cookies and login state across commands. You can navigate pages, fill forms, capture screenshots, and diff page states to verify behavior during regression testing.

Can I use Playwright to maintain login sessions across multiple test commands?▼

Yes, Playwright-driven automation supports persistent headless browser sessions that retain state, cookies, and tabs across multiple commands. This allows seamless execution of long-running tests without needing to re-authenticate for every interaction.

What is the best way to capture evidence during web app regression testing?▼

The best way to capture evidence during regression testing is using automated interactions that annotate screenshots and diff page states. This validates web app behavior by replaying user flows and recording visual and semantic changes.

Does headless browser automation support headed mode for demo dogfooding?▼

Yes, the headless browser automation supports both headless and headed modes. You can switch to headed mode to provide rapid QA feedback during deployment previews, CI workflows, and demo dogfooding by visually replaying user flows.

How do I handle failures and privacy when running automated web browsing tests?▼

Automated web browsing tests include robust failure handling and privacy-aware logging to manage exceptions securely. This ensures that automated interactions, form inputs, and semantic searches execute reliably without exposing sensitive session data.

When do I need a persistent browser session for QA automation?▼

You need a persistent browser session for QA automation when performing long-running tests or regression testing that require continuous state retention. It eliminates manual bug reproduction by maintaining tabs and login sessions across sequential navigation commands.