github/awesome-copilot · Official

playwright-explore-website

Website exploration for testing using Playwright MCP

All-time #1149 Trending #7355 First seen Feb 25, 2026
8-week activity · all time api

Installation

$ npx skills add github/awesome-copilot --skill playwright-explore-website

Summary

  • 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

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from github/awesome-copilot · top by installs.

npx skills add github/awesome-copilot

Browse all from github/awesome-copilot

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 38.8K
License LICENSE
Default branch main
Open issues 21
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents github-copilot

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 681 B
  • docs SUMMARY.md 86 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 14,708 installs

SKILL.md

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.