browser

Control a browser to inspect and interact with live web pages.

10|2|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/nullskymc/Aurevoy --skill browser-nullskymc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser
Source: https://github.com/nullskymc/Aurevoy/tree/main/apps/agent/skills/builtin/browser
Command: npx skills add https://github.com/nullskymc/Aurevoy --skill browser-nullskymc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you interact with live web pages when static fetching is not enough, especially for JavaScript-heavy sites, UI verification, and browser-based troubleshooting.

Core Features & Use Cases

  • Page navigation and interaction: Open URLs, click buttons, fill forms, scroll, switch tabs, and wait for elements or network idle.
  • Information extraction: Capture screenshots, inspect DOM summaries, and collect console errors or warnings from the browser.
  • Testing and debugging: Verify rendered UI behavior, debug front-end issues, and validate end-to-end user flows.
  • Use Case: Use this Skill when you need to confirm that a page rendered correctly after a change or reproduce a bug that only appears in the browser.

Quick Start

Use the browser skill to open this URL, inspect the rendered page, and summarize any console errors.

Frequently Asked Questions about browser

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

FAQPage Schema
How do I capture screenshots and inspect the DOM of JavaScript-rendered web pages?

To capture screenshots and inspect the DOM of JavaScript-rendered pages, you can use browser automation to navigate URLs, wait for network idle, and extract rendered UI elements. This allows direct visual verification and front-end debugging of dynamic sites.

Can I automate form workflows and verify UI behavior on live web pages?

Yes, you can automate form workflows and verify UI behavior by driving live web pages. The automation supports clicking buttons, filling forms, scrolling, and switching tabs to validate end-to-end user flows and reproduce front-end bugs.

How do I collect console errors and warnings during front-end debugging?

You collect console errors and warnings during front-end debugging by accessing the browser console through automation. This captures JavaScript runtime issues directly from the live page, helping troubleshoot UI rendering problems and script failures.

Do I need Playwright MCP Server support for browser automation tasks?

Yes, you need Playwright MCP Server support to perform browser automation tasks. This server provides the necessary backend for navigation, DOM inspection, console access, and automated interaction required to drive web pages and capture proof.

What is the best way to debug front-end issues that only appear in the browser?

The best way to debug front-end issues that only appear in the browser is using automated browser interaction to reproduce the bug. This approach verifies rendered UI behavior, inspects DOM summaries, and validates user flows that static fetching cannot reach.

Why does static fetching fail for JavaScript-heavy sites and when do I need browser automation?

Static fetching fails for JavaScript-heavy sites because it cannot execute scripts to render dynamic content. You need browser automation when a page requires JavaScript rendering, UI verification, or browser-based troubleshooting to display its true state.