Catalog
github/playwright-explore-website

github

playwright-explore-website

Website exploration for testing using Playwright MCP

v1.0Latest
New~156Updated Jun 26, 2026

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.
Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

58/100

Grade

C

Adequate

Safety

75

Quality

48

Clarity

55

Completeness

45

Summary

A Playwright-based website exploration skill that guides an agent through manual browser testing workflows. The skill instructs the agent to navigate to a target URL, interact with 3-5 core features, document UI elements and their locators, and generate test cases from observed behavior.

Detected Capabilities

browser navigation via Playwright MCPUI element inspection and locator extractionuser interaction simulation (clicks, form input)browser context closuretest case generation from observations

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

explore websiteplaywright testingmanual web testinggenerate test casesfind ui elementsdocument user flows

Use Cases

  • Explore and document website user flows before writing automated tests
  • Identify key UI elements and their selectors for test automation
  • Generate test case outlines from manual exploration
  • Test website functionality across multiple user interactions

Quality Notes

  • Skill is very brief — missing key details on HOW to interact with elements, HOW to document findings, and HOW to generate test cases
  • No guidance on output format — agent unclear on structure for 'concise summary' or test case template
  • No error handling documented — what if URL is unreachable, Playwright MCP unavailable, or elements are dynamic?
  • No example workflows or code snippets provided to illustrate expected behavior
  • Scope is clear (website exploration + test case generation) but implementation details are vague
  • No edge case handling — missing guidance for SPA navigation, authentication flows, or waiting for dynamic content
Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use github/playwright-explore-website in your dev environment

Command Palette

Search for a command to run...