browse

Drive a persistent headless Chromium browser to verify pages, capture screenshots, and interact with UI.

Updated Mar 26, 2026

Search Tags:#automation #qa #ui-testing #web-testing #browser #headless

Ready to run

npx skills add https://github.com/mrkhachaturov/rkstack --skill browse-mrkhachaturov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/mrkhachaturov/rkstack/tree/main/skills/browse
Command: npx skills add https://github.com/mrkhachaturov/rkstack --skill browse-mrkhachaturov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates web QA tasks by driving a persistent headless Chromium instance to load pages, verify content, capture screenshots, and interact with UI elements.

Core Features & Use Cases

Persistent headless Chromium daemon that preserves cookies, tabs, and login state across commands.
Fast command latency (~100ms per action) and auto-start on first use, with automatic shutdown after 30 minutes of inactivity.
Supports navigation, element interaction, form handling, screenshot capture, responsive checks, and basic debugging.

Quick Start

Install the rkstack browse plugin and start the session to begin using the headless browser.

Frequently Asked Questions about browse

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

FAQPage Schema

How do I automate web QA tasks using a headless browser?▼

Automate web QA by driving a persistent headless Chromium daemon to load pages, interact with UI elements, and verify page state. It handles navigation, form submissions, and visual capture with low latency.

Can I preserve login state and cookies across multiple UI testing commands?▼

Yes, UI testing preserves login state, cookies, and tabs across commands using a persistent headless Chromium daemon. The browser maintains session continuity until automatic shutdown after 30 minutes of inactivity.

How do I capture screenshots for responsive web testing?▼

Capture screenshots for responsive web testing by commanding the headless browser to load pages and perform visual capture. The tool supports responsive checks and basic debugging across different application contexts.

Does headless browser automation require manual startup for deployment verification?▼

No, headless browser automation auto-starts the Chromium daemon on first use for deployment verification. It operates with fast command latency around 100ms per action and requires no manual initialization.

What are the limitations of using a persistent Chromium daemon for web testing?▼

A limitation of this persistent Chromium daemon is automatic shutdown after 30 minutes of inactivity, which may interrupt long idle periods. It focuses on basic debugging and standard web interactions rather than complex network mocking.

What is the best way to verify page state after a deployment?▼

The best way to verify page state after deployment is using a headless browser to automate navigation and inspect UI elements. This approach validates application behavior, collects screenshots, and confirms successful rendering.