playwright-tester

Drive browsers with Playwright to capture screenshots and execute end-to-end flows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cncorp/superpowers --skill playwright-tester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-tester
Source: https://github.com/cncorp/superpowers/tree/main/dot-claude/skills/playwright-tester
Command: npx skills add https://github.com/cncorp/superpowers --skill playwright-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright^1.48.0, and includes scripts (resource) components.

What problem does it solve?

Manually verifying frontend behavior, capturing screenshots, or testing complex user flows is repetitive and error-prone. This skill provides robust browser automation to streamline UI validation.

Core Features & Use Cases

  • Quick Screenshots: Capture high-quality screenshots of any URL with customizable viewports and wait times using a simple CLI command.
  • Advanced Automation: Write and execute custom JavaScript Playwright scripts for multi-step user flows, form submissions, and responsive design testing.
  • Dev Server Detection: Automatically identifies running local development servers, simplifying setup for local testing.
  • Helper Utilities: Access a library of robust helper functions for safe clicks, typing, authentication, and data extraction.
  • Use Case: When a user asks to see how a new feature looks on mobile, use this skill to take a screenshot of the page with a mobile viewport, or write a quick script to test a multi-step onboarding flow.

Quick Start

Use the playwright-tester skill to take a full-page screenshot of the admin dashboard at http://100.93.144.78:5172/admin and save it to /tmp/admin-dashboard.png.

Frequently Asked Questions about playwright-tester

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture screenshots of web pages with Playwright?

Playwright-tester automates screenshot capture by driving a browser to any URL with customizable viewport sizes and wait times. Use the CLI command to specify the URL and output path, and the skill handles browser automation to save high-quality screenshots for UI validation and debugging.

Can I automate end-to-end testing across multiple browsers?

Yes. Playwright-tester supports multi-browser execution, allowing you to write custom JavaScript scripts that run automated user flows, form submissions, and responsive design tests across configured servers. Run tests headless or headed depending on your debugging needs.

What helper utilities does Playwright-tester provide for browser automation?

The skill includes a library of robust helper functions for safe clicks, typing, authentication, and data extraction. These utilities simplify common automation patterns when writing custom Playwright scripts for complex user flows and multi-step testing.

How do I test responsive design across different viewport sizes?

Playwright-tester lets you configure custom viewport sizes and capture screenshots or run automated flows at each breakpoint. This validates how your frontend behaves on mobile, tablet, and desktop without manual testing across devices.

Does Playwright-tester detect local development servers automatically?

Yes. The skill automatically identifies running local development servers, simplifying setup for local testing. This removes the need to manually configure server URLs when testing features during development.

When should I use browser automation instead of manual UI testing?

Use browser automation when you need to verify complex user flows, validate responsive design, or capture screenshots repeatedly across different states. It eliminates repetitive manual verification and catches UI regressions early in development.