Get the FREE Ultimate OpenClaw Setup Guide →

playwright-explore-website

npx machina-cli add skill github/awesome-copilot/playwright-explore-website --openclaw
Files (1)
SKILL.md
681 B

Website Exploration for Testing

Your goal is to explore the website and identify key functionalities.

Specific Instructions

  1. Navigate to the provided URL using the Playwright MCP Server. If no URL is provided, ask the user to provide one.
  2. Identify and interact with 3-5 core features or user flows.
  3. Document the user interactions, relevant UI elements (and their locators), and the expected outcomes.
  4. Close the browser context upon completion.
  5. Provide a concise summary of your findings.
  6. Propose and generate test cases based on the exploration.

Source

git clone https://github.com/github/awesome-copilot/blob/main/plugins/frontend-web-dev/skills/playwright-explore-website/SKILL.mdView on GitHub

Overview

Explores a website with the Playwright MCP Server to map key functionalities. It identifies 3-5 core features or user flows, documents UI elements with locators and expected outcomes, and then closes the browser context. It also generates concise findings and test-case proposals for automation.

How This Skill Works

Using the Playwright MCP Server, the agent navigates to the provided URL, interacts with 3-5 core features, and records element locators and outcomes. It then closes the browser context and outputs a findings summary plus test-case proposals.

When to Use It

  • When you’re assessing a new website to map core user flows quickly.
  • When you need a baseline of 3-5 features to drive automated tests.
  • When documenting UI elements and their locators for later automation.
  • When generating test-case ideas from hands-on exploration.
  • When you want a concise, reproducible summary after exploration and testing prep.

Quick Start

  1. Step 1: Provide the target URL to explore using the Playwright MCP Server.
  2. Step 2: Identify 3-5 core features or user flows and interact with them.
  3. Step 3: Document interactions, locators, outcomes, and generate test-case proposals; then close the browser context.

Best Practices

  • Plan exploration around 3-5 core features, not every page.
  • Capture precise element locators (selectors, roles, ARIA attributes).
  • Document expected outcomes for each interaction (success messages, redirects).
  • Close the browser context after completing exploration to free resources.
  • Generate clear test-case proposals based on observed flows and outcomes.

Example Use Cases

  • Explore an e-commerce site by searching a product, applying a filter, and adding to cart.
  • Walk through a user signup and email verification flow.
  • Navigate a dashboard: resize panels, interact with widgets, and save changes.
  • Test a checkout flow: cart review, address entry, payment, and order confirmation.
  • Update profile settings: change password, upload avatar, and save changes.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers