playwright-explore-website
Website exploration for testing using Playwright MCP
Best use case
playwright-explore-website is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Website exploration for testing using Playwright MCP
Teams using playwright-explore-website should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/playwright-explore-website/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How playwright-explore-website Compares
| Feature / Agent | playwright-explore-website | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Website exploration for testing using Playwright MCP
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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.
Related Skills
website-generator
Use when the user asks to create a website, build a site, generate a landing page, or mentions B12. Trigger phrases: "create a website", "build me a site", "website for my business", "generate a landing page", "B12 website". Trigger with 'website', 'generator'.
playwright-generate-test
Generate a Playwright test based on a scenario using Playwright MCP
playwright-automation-fill-in-form
Automate filling in a form using Playwright MCP
../../../engineering-team/playwright-pro/skills/testrail/SKILL.md
No description provided.
../../../engineering-team/playwright-pro/skills/review/SKILL.md
No description provided.
../../../engineering-team/playwright-pro/skills/report/SKILL.md
No description provided.
playwright-pro
Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.
../../../engineering-team/playwright-pro/skills/migrate/SKILL.md
No description provided.
../../../engineering-team/playwright-pro/skills/generate/SKILL.md
No description provided.
../../../engineering-team/playwright-pro/skills/fix/SKILL.md
No description provided.
../../../engineering-team/playwright-pro/skills/coverage/SKILL.md
No description provided.
../../../engineering-team/playwright-pro/skills/browserstack/SKILL.md
No description provided.