playwright-explore-website
/playwright-explore-website
Explore a website interactively using Playwright MCP to identify key functionalities, user flows, and UI elements for testing purposes. Use when the user wants to understand a website's structure, discover testable features, or prepare for writing tests.
- Author
- atc-net ↗
- Repository
- atc-agentic-toolkit ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Explore a website interactively using Playwright MCP to identify key functionalities, user flows, and UI elements for testing purposes. Use when the user wants to understand a website's structure, discover testable features, or prepare for writing tests.
Original author description
Explore a website interactively using Playwright MCP to identify key functionalities, user flows, and UI elements for testing purposes. Use when the user wants to understand a website's structure, discover testable features, or prepare for writing tests.
How it works
- Workflow
- Exploration Tips
- Output Format
SKILL.md preview
--- name: playwright-explore-website description: Explore a website interactively using Playwright MCP to identify key functionalities, user flows, and UI elements for testing purposes. Use when the user wants to understand a website's structure, discover testable features, or prepare for writing tests. --- # Website Exploration for Testing Explore a website using the Playwright MCP server to identify key functionalities and generate test candidates. ## Workflow 1. **Get the target URL** — If not provided, ask the user for the URL to explore 2. **Navigate and orient** — Use `browser_navigate` to load the page, then `browser_snapshot` to capture the initial state 3. **Identify core features** — Explore 3-5 key user flows by interacting with navigation, forms, buttons, and dynamic elements 4. **Document findings** — For each feature record: - User interaction steps - Relevant UI elements and their locators (data-testid, role, text) - Expected outcomes and assertions 5. **Close browser** — Use `browser_close` when exploration is complete 6. **Summarize and propose tests** — Provide a concise summary of findings and propose test cases based on discovered flows ## Exploration Tips - Start with the main navigation to understand site structure - Look for forms, modals, dropdowns, and interactive elements - Check responsive behavior if relevant - Note any loading states, error states, or edge cases - Prefer stable locators: `data-testid` > `role` > `text` > CSS selectors ## Output Format For each discovered feature: ``` ### Feature: [Name] - **URL**: /path - **Steps**: 1. Click X → 2. Fill Y → 3. Submit - **Key elements**: [locator details] - **Suggested test**: [brief test description] ```
Versions
The database has no other skills named playwright-explore-website.
Database snapshot: 13.11.2026 · package version 2bf4303f486e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100playwright-testing
UI/E2E test automation with Playwright MCP. Use when the user asks to "test the UI", "automate browser tests", "check the page", "take a screenshot", "run Playwright", "write E2E tests", or anything about browser-based testing. - 82playwright
Playwright E2E testing standards — test structure, selectors, fixtures, page objects, CI integration, and MCP runner so tests can be triggered from prompts. Load when writing, reviewing, or running Playwright specs. - 100pw-init
Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure". - 100pw-init
Set up Playwright in a project. Use when user says \"set up playwright\", \"add e2e tests\", \"configure playwright\", \"testing setup\", \"init playwright\", or \"add test infrastructure\". - 100pw-init
Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure". - 100playwright-generate-test
Generate Playwright TypeScript tests based on a scenario using Playwright MCP for real browser interaction. Use when the user wants to create an end-to-end test, generate a test from a user story, or automate a test scenario with Playwright.