playwright-skill

Automates browser interactions and end-to-end testing of web applications with Playwright.

1|Updated Aug 7, 2025
One-click install
npx skills add https://github.com/zzafergok/arktos --skill playwright-skill-zzafergok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-skill
Source: https://github.com/zzafergok/arktos/tree/main/.agent/skills/playwright-skill
Command: npx skills add https://github.com/zzafergok/arktos --skill playwright-skill-zzafergok

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright.

What problem does it solve? Manually verifying web application behavior across pages, forms, and screen sizes is slow and error-prone. This Skill automates browser-based testing so you can validate user flows, catch console errors, and check responsive layouts without repetitive manual clicking. ## Core Features & Use Cases - Browser Automation: Launch Chromium, navigate pages, fill forms, click elements, and take screenshots using Playwright scripts. - E2E Flow Testing: Test login flows, form submissions, file uploads, and long-running operations with robust waiting strategies like waitForURL and waitForSelector. - Quality Checks: Detect broken links, monitor console errors, and capture screenshots across desktop, tablet, and mobile viewports. - Use Case: After starting your dev server, ask the AI to test the login flow at localhost:3000 — it detects the port, writes a test script to /tmp, runs it, and confirms the redirect to the dashboard. ## Quick Start Use Playwright to test the login flow on my local dev server and take a screenshot of the dashboard.

Frequently Asked Questions about playwright-skill

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

FAQPage Schema
How do I test a login flow with Playwright?▼

Launch Chromium, navigate to the login page, fill the email and password inputs with page.fill, click the submit button, then use page.waitForURL to confirm the redirect to the dashboard. This validates the full authentication flow end to end.

How to check responsive design across devices with Playwright?▼

Use page.setViewportSize to iterate over desktop (1440x900), tablet (768x1024), and mobile (375x667) dimensions, taking a full-page screenshot at each size. This reveals layout breakage across common device widths.

What selectors are most reliable in Playwright tests?▼

The most robust selectors are data-testid attributes and ARIA role locators like page.getByRole. Label and text selectors work well for forms, while raw CSS selectors like button[type="submit"] are more fragile when markup changes.

Why are fixed timeouts bad in Playwright scripts?▼

Fixed waits like page.waitForTimeout(3000) make tests fragile because page load times vary. Prefer state-based waits such as waitForSelector, waitForURL, waitForLoadState('networkidle'), or waitForResponse, which proceed as soon as the condition is met.

Does Playwright support detecting broken links on a page?▼

Yes. Collect all anchor elements with page.locator('a[href^="http"]'), then send HEAD requests via page.request.head for each href. Links returning non-OK responses or throwing errors are reported as broken with their status codes.

Can Playwright monitor console errors during page load?▼

Yes. Attach a listener with page.on('console') and filter messages where msg.type() equals 'error'. After navigation and a short wait, the collected array reveals any JavaScript console errors the page produced.