
playwright-explore-website
✓ Official★ 36,200by github · part of github/awesome-copilot
Automated website exploration and test case generation using Playwright. Navigates to provided URLs and systematically identifies 3-5 core features and user flows Documents UI elements, their locators, and expected outcomes for each interaction Generates test cases based on exploration findings for immediate use in testing workflows Manages browser context lifecycle automatically, closing sessions upon completion
Automated website exploration and test case generation using Playwright. Navigates to provided URLs and systematically identifies 3-5 core features and user flows Documents UI elements, their locators, and expected outcomes for each interaction Generates test cases based on exploration findings for immediate use in testing workflows Manages browser context lifecycle automatically, closing sessions upon completion
Inspect the full instructions your agent will receiveExpandCollapse
This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.
name: playwright-explore-website description: 'Website exploration for testing using Playwright MCP'
Website Exploration for Testing
Your goal is to explore the website and identify key functionalities.
Specific Instructions
- Navigate to the provided URL using the Playwright MCP Server. If no URL is provided, ask the user to provide one.
- Identify and interact with 3-5 core features or user flows.
- Document the user interactions, relevant UI elements (and their locators), and the expected outcomes.
- Close the browser context upon completion.
- Provide a concise summary of your findings.
- Propose and generate test cases based on the exploration.
npx skills add https://github.com/github/awesome-copilot --skill playwright-explore-websiteRun this in your project — your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.