browser-test

Automate browser UI tests with Playwright MCP and Chrome Bridge.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/nille/shipkit --skill browser-test-nille
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-test
Source: https://github.com/nille/shipkit/tree/main/shipkit/advanced/skills/browser-test
Command: npx skills add https://github.com/nille/shipkit --skill browser-test-nille

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interactive browser testing using Playwright MCP with Chrome Bridge extension allows you to run UI tests in your actual browser context, leveraging your active sessions and cookies rather than synthetic headless runs.

Core Features & Use Cases

  • Real-browser testing: Use your current browser state to verify UI flows across local, staging, and production-like environments.
  • Playwright MCP integration: Coordinate with the Playwright MCP server and Chrome Bridge extension for seamless test execution.
  • Deterministic workflows: Create repeatable test plans, capture screenshots, and observe exact user interactions to diagnose failures.

Quick Start

Start an interactive browser-test session by ensuring Playwright MCP is configured in your mcp.json and the Chrome Bridge extension is connected to your browser.

Frequently Asked Questions about browser-test

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

FAQPage Schema
How do I run Playwright UI tests using my existing authenticated browser session?

Playwright UI testing in a real browser session uses Playwright MCP and the Chrome Bridge extension to access your active cookies. This lets you execute test plans against authenticated local, staging, or production-like environments without synthetic logins.

Can I capture screenshots during automated browser testing to diagnose UI failures?

Yes, automated browser testing captures screenshots and observes exact user interactions to diagnose failures. This deterministic workflow creates repeatable test plans for visual checks across your web applications.

What is Playwright MCP and how does it work with Chrome Bridge for UI testing?

Playwright MCP is a server that coordinates with the Chrome Bridge extension to enable interactive browser testing. It applies to web applications requiring authenticated sessions, leveraging your actual browser context rather than headless runs.

Does browser automation testing work across local and staging environments?

Browser automation testing supports UI flows across local, staging, and production-like environments. It uses your current browser state to verify visual checks and user interactions deterministically.

Do I need to configure anything before starting interactive browser UI tests?

You need Playwright MCP configured in your mcp.json and the Chrome Bridge extension connected to your browser. This setup enables phase-based test execution with error handling and reporting.

Why use real browser testing instead of headless automated runs?

Real browser testing leverages your active sessions and cookies rather than synthetic headless runs. This verifies UI flows accurately across environments, ensuring authenticated states remain intact during phase-based test execution.