skills.rest
florianhorner
florianhornerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

browse

Automate headless browser navigation, element interaction, and state verification for QA testing.

4|2|Updated Mar 29, 2026
Search Tags:#screenshots#playwright#responsive#browse#web-automation#qa-testing
One-click install
npx skills add https://github.com/florianhorner/mammamiradio --skill browse-florianhorner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/florianhorner/mammamiradio/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/florianhorner/mammamiradio --skill browse-florianhorner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, and capture evidence of results.

Core Features & Use Cases

  • Navigate to URLs, interact with page elements, and assert states
  • Take screenshots, diff changes, and verify responsive layouts
  • Test forms and uploads, dialogs, and other UI flows
  • Produce ready-to-share evidence for bug reports, demos, and QA gates

Quick Start

Install and run the skill to start a headless browser you can script with commands like goto and screenshot.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I capture screenshots for automated QA testing across different viewports?▼

Automated QA testing captures screenshots across multiple viewports by navigating to URLs in a headless browser, interacting with elements, and saving visual evidence of the rendered page state for diff comparisons.

What is headless browser testing used for in web-automation workflows?▼

Headless browser testing in web-automation verifies UI flows, asserts page states, and interacts with elements like forms and dialogs without a graphical interface, producing shareable evidence for bug reports and QA gates.

Can I test responsive layouts and verify before/after UI changes?▼

Responsive layouts are verified by navigating to URLs across multiple viewports in a headless browser, capturing screenshots, and diffing before and after changes to detect visual regressions in the UI.

Does this headless browser tool require any external dependencies to run?▼

No external dependencies are required to run this headless browser tool. It operates independently to execute deterministic navigation, element interaction, and state verification scripts for site dogfooding.

What's the best way to automate form uploads and dialog interactions for QA gates?▼

Automating form uploads and dialog interactions for QA gates is best handled by scripting deterministic headless browser commands to navigate URLs, interact with UI elements, and assert resulting page states.

When should I not use a headless browser for site dogfooding?▼

A headless browser should not be used for site dogfooding when you need manual visual inspection of complex rendering issues or when verifying behaviors heavily dependent on a graphical interface rather than automated state assertions.

Related Skills

Explore More Software Engineering Skills→
p-sree-sai-pavanp-sree-sai-pavan
5

gemini

Execute headless one-shot prompts and route across models with Gemini CLI.

Community
Intermediate
antriksh-29antriksh-29

qa-only

Generate structured QA reports with health scores, screenshots, and reproducible steps.

Community
Advanced
fajshahfajshah
1

browsing-with-playwright

Automate browser navigation, form interactions, and data extraction via Playwright MCP.

Community
Intermediate
smarmen86smarmen86

gstack

Automate headless Chromium browser interactions for QA and site testing.

Community
Advanced