browser

Drive a real browser to capture console, network, and WebSocket evidence for bug reproduction.

9|9|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/nullmastermind/viber-router --skill browser-nullmastermind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser
Source: https://github.com/nullmastermind/viber-router/tree/main/.claude/skills/browser
Command: npx skills add https://github.com/nullmastermind/viber-router --skill browser-nullmastermind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables reproducible end-to-end browser diagnostics by driving a real browser session to reproduce UI bugs, gather screenshots, console errors, and network/WebSocket traces, and correlate those artifacts with source code for accurate root-cause analysis.

Core Features & Use Cases

  • E2E diagnostic workflow: Guided reproduce → capture → trace loop with mandatory evidence (before/after screenshots, console logs, network captures).
  • Exploratory testing: Proactive UX and responsive checks across flows, including accessibility and edge-case interaction testing.
  • Advanced monitoring: Injects fetch, XHR, and WebSocket monitors, uses snapshotForAI for element discovery, and preserves named pages across scripts for session continuity.
  • Use case: Reproduce an intermittent form submission failure, capture network/http and websocket activity, collect console stack traces, and map evidence to the responsible frontend and backend files.

Quick Start

Run dev-browser against your app URL, get the main page, use snapshotForAI to inspect state, perform the action to reproduce the issue, and save screenshots and network logs for analysis.

Frequently Asked Questions about browser

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

FAQPage Schema
How do I reproduce UI bugs with real browser evidence?

To reproduce UI bugs with real browser evidence, you drive a real browser session to recreate the issue and capture visual, console, network, and WebSocket artifacts. This connects diagnostic evidence directly to source code.

Can I capture WebSocket and network traces during end-to-end testing?

Yes, you can capture WebSocket and network traces during end-to-end testing. The process injects fetch, XHR, and WebSocket monitors into the browser session to log activity alongside console errors and screenshots.

How do I use snapshotForAI for element discovery in Playwright-style automation?

You use snapshotForAI for element discovery by driving a dev-browser against your application URL, inspecting the page state, and capturing snapshots to guide Playwright-style page API interactions during exploratory UX testing.

Does this browser automation approach work for local development servers?

Yes, this browser automation approach works for local development servers. It supports both headed and headless automation via dev-browser to verify fixes and perform exploratory testing across local and deployed web applications.

What is the best way to document intermittent form submission failures?

The best way to document intermittent form submission failures is to run a guided diagnostic loop that captures before and after screenshots, network logs, and console stack traces to map evidence to responsible frontend and backend files.