skills.rest
Manu343726
Manu343726COMMUNITY
Explore all skills by this author →
WebsiteGitHub

playwright-explore-website

Explore websites with Playwright to identify user flows and propose test cases.

Updated Apr 17, 2026
Search Tags:#browser automation#mcp#playwright#e2e testing#test case generation#website exploration#ui locators
One-click install
npx skills add https://github.com/Manu343726/audible-exporter --skill playwright-explore-website-manu343726
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-explore-website
Source: https://github.com/Manu343726/audible-exporter/tree/main/.agents/skills/playwright-explore-website
Command: npx skills add https://github.com/Manu343726/audible-exporter --skill playwright-explore-website-manu343726

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly understand a website’s key user journeys by performing guided browser exploration and capturing what matters for testing and automation.

Core Features & Use Cases

  • Guided website exploration: Navigate to a provided URL and identify core features or user flows.
  • UI capture with locators: Document relevant UI elements (including their locators) and what interactions do.
  • Test case generation: Convert findings into proposed test cases with clear expected outcomes.
  • Use case: When you need to write reliable end-to-end tests for an unfamiliar web app, run this exploration to learn the important paths and produce test scenarios.

Quick Start

Ask the skill to explore the target site and report the discovered 3-5 core flows with locators, expected outcomes, and proposed test cases.

Frequently Asked Questions about playwright-explore-website

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

FAQPage Schema
How do I discover user flows on an unfamiliar website for Playwright e2e testing?▼

Guided website exploration maps a target URL by navigating it with a Playwright MCP flow, capturing UI locators and interaction results for 3-5 core features, and proposing actionable test cases with expected outcomes.

Can I automatically generate test cases from website exploration using Playwright?▼

Yes, automated test case generation works by capturing UI locators and interaction results during website exploration, then converting those findings into proposed test cases with clear expected outcomes for browser-driven testing.

What is the best way to map UI locators for core website functionalities?▼

Mapping UI locators is best achieved by using a Playwright MCP browser flow to navigate a provided URL, interact with 3-5 core features, and record the specific UI element locators and their interaction results.

Do I need a Playwright MCP flow to extract UI locators and propose test cases?▼

Yes, a Playwright-based MCP flow is required to navigate the user-provided URL, collect UI locators and interaction results for 3-5 features, close the browser context, and propose actionable test cases.

How many core features does website exploration capture during a single session?▼

During a single session, website exploration captures 3-5 core features or key user flows, documenting their UI locators and interaction results before closing the browser context and proposing test cases.

Related Skills

Explore More Software Engineering Skills→
rodoHasArrivedrodoHasArrived

playwright-explore-website

Explore website workflows via Playwright and generate test cases.

Community
Intermediate
joabgonzalezjoabgonzalez
7

playwright

Automate cross-browser end-to-end testing workflows with Playwright.

Community
Advanced
Svenja-devSvenja-dev
38

e2e-testing

Automate end-to-end browser testing for web applications with Playwright MCP.

Community
Intermediate
IgosukiIgosuki
1

browser-screenshot

Capture full-page, viewport, and element screenshots via Playwright CLI.

Community
Intermediate