BR

browser-test

Enables interactive, real-time feature verification using Playwright without creating static test files.

Install

mkdir -p .claude/skills/browser-test && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4181" && unzip -o skill.zip -d .claude/skills/browser-test && rm skill.zip

Installs to .claude/skills/browser-test

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Validate a feature works by driving a real browser with Playwright MCP. No test files — just interactive verification.
118 charsno explicit “when” trigger
Beginner

Key capabilities

  • →Parse feature descriptions into concrete checklists
  • →Detect and initialize dev server ports automatically
  • →Generate directory structure for test artifacts
  • →Execute browser-driven sub-agents for verification

How it works

Spawns a specialized sub-agent to drive a browser instance based on parsed feature files or custom input requirements.

Inputs & outputs

You give it
Feature description or path to.feature file
You get back
Verification checklist and screenshot artifacts

When to use browser-test

  • →Smoke testing new features
  • →Verifying UI behavior interactively
  • →Running existing feature file scenarios
  • →Validating dashboard rendering after authentication

About this skill

Browser test: walk the scenarios, report the evidence

This skill is the recipe from "scenarios" to "report". It does not drive the browser itself. haven browser is the one way to drive a browser (see haven-browser; sign-in is --as admin, see haven-auth; seeded logins are haven-seed). Playwright's MCP tools and playwright-cli are refused where haven is installed, and MCP browser tools are never used by lanes. Use plain Playwright only for something haven cannot reach, and say so in the report.

1. Prepare

  • A feature file path: read it and turn each scenario into a numbered step with an expected result. A plain description: use it as the one step list. Neither: smoke test (app loads, admin sign-in works, the dashboard renders).
  • Stack: haven status. If none runs, start one only when asked (haven-lifecycle), and say if you did. The base URL is whatever haven status prints; use that one origin for the whole run. A different hostname for the same app (127.0.0.1, say) fails sign-in with a 403.
  • A plain pnpm dev stack serves the built UI; pnpm dev:hmr serves Vite. First loads can take tens of seconds under Vite.
  • Workspace: browser-tests/<feature>/<YYYY-MM-DD>/ (gitignored; never commit it).

2. Seed only what the steps need

Decide which data must exist (a suite with one scenario, one trace, a completed run). Create it through the UI where practical; use the API or a seed (haven db seed, haven-seed) for bulk data. Keep it minimal. Credentials for ingestion come from a seeded login or a personal scoped key, never a project key read from settings, and never pasted into a prompt or a report.

3. Walk it

Use one lane per run (--lane bt-<feature> --as admin). For each step: act, check the expected result in the diff or a snapshot --grep, and record PASS or FAIL.

  • Take a screenshot for each step that checks how something looks (drawer width, card padding, colour, clipping, dark mode) and for every failure. A snapshot finds controls; it cannot show paint. Save with --out browser-tests/<feature>/<date>/NN-name.png.
  • On a failure: screenshot, haven browser console --level error, haven browser network --failed, mark it FAIL and go on. Do not debug the app or edit code during the walk.
  • Overlays are a routed singleton with a back stack: assert that one overlay is open, that back returns to the caller and that a draft survives. Two stacked copies of the same drawer is a defect to report, not a quirk to press Escape past.
  • Waits are --wait-for 'text=...', never sleeps. Close the lane when done.

4. Report

Write browser-tests/<feature>/<date>/report.md:

# Browser test: <feature>

**Date / stack URL / branch / PR (if known)**

| #   | Scenario | Result | Evidence    |
| --- | -------- | ------ | ----------- |
| 1   | <name>   | PASS   | 01-name.png |

## Failures

- **2:** expected X, saw Y (console and network lines).

Return the table to the caller. Publishing is a separate act, done only when asked: upload screenshots with gh issue comment --attach file#alt (see the repository's PR rules) and put the table in a PR comment, not the squash-merge body.

Rules

  • Never ask the user for a port, account or browser: resolve them as above.
  • Read HOW_TO.md beside this file for gotchas before the first run.
  • Do not create test files. To turn a walk into an e2e test use haven browser record (haven-browser), then record export.
  • For a live session with a person watching, see browser-pair.

When not to use it

  • →When testing backend logic without a UI
  • →For performance benchmarking or load testing

Prerequisites

Playwright MCP installedScripts/dev-up.sh script available

Limitations

  • →Requires a running local development server
  • →Dependent on Playwright capability accuracy

How it compares

It eliminates manual browser interaction by programmatically orchestrating a sub-agent to follow defined scenarios.

Compared to similar skills

browser-test side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
browser-test (this skill)18moReviewBeginner
webapp-testing3537moReviewIntermediate
dev-browser538moReviewIntermediate
playwright-browser-automation2911moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

webapp-testing

anthropics

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

353585

dev-browser

SawyerHood

Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.

53176

playwright-browser-automation

lackeyjb

Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.

29146

windows-ui-automation

martinholovsky

Expert in Windows UI Automation (UIA) and Win32 APIs for desktop automation. Specializes in accessible, secure automation of Windows applications including element discovery, input simulation, and process interaction. HIGH-RISK skill requiring strict security controls for system access.

17126

unity-mcp-orchestrator

CoplayDev

Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.

1795

agent-browser

vercel-labs

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

3075

Search skills

Search the agent skills registry