browse

Control a headless Chromium browser to load and inspect web pages.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/LaPaGaYo/nexus --skill browse-lapagayo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/support/browse
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill browse-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams and developers need reliable, repeatable tests of web interfaces without manual browser interactions. Browse lets you drive a headless browser to load pages, interact with UI, capture state, and verify results at scale.

Core Features & Use Cases

  • Headless navigation and scripted interactions across URLs for regression testing.
  • Automated screenshot capture with annotations and diffs to document UI changes.
  • Quick cycle for bug reproduction, feature verification, and deployment dogfooding.

Quick Start

Run the browse skill to start a headless browser and load a URL for automated QA checks.

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 with a headless browser for feature verification?

Automated web testing with a headless browser lets you script navigation and UI interactions to verify features. You can drive a headless browser to load pages, inspect elements, and validate results at scale without manual interaction.

What is the best way to capture automated screenshots for regression testing?

The best way to capture automated screenshots for regression testing is by scripting a headless browser to load URLs and take snapshots. This skill supports screenshot capture with annotations and diffs to document UI changes.

Do I need a Chromium-compatible environment to run headless QA tests?

Yes, you need a Chromium-compatible environment to run headless QA tests with this skill. It requires a compatible browser setup to execute commands like goto, text, screenshot, and diff for automated validation.

Can I use headless navigation to reproduce bugs across multiple deployments?

Yes, you can use headless navigation to reproduce bugs across multiple deployments. The skill supports scripted interactions across URLs, allowing you to load pages, capture state, and verify results for quick bug reproduction.

What commands are available for UI inspection during automated web testing?

Available commands for UI inspection during automated web testing include goto, text, screenshot, diff, and is_visible. These commands let you navigate pages, extract content, capture state, and perform validation tasks.

Does headless browser testing work for deployment dogfooding and site verification?

Yes, headless browser testing works for deployment dogfooding and site verification. You can script a headless browser to load and inspect web pages, capture state, and verify results quickly across different deployments.