NEW Browse AI tools across categories — updated daily. See what's new →

Playwright Skill

Enables Claude to write and execute any Playwright automation on-the-fly - from simple page tests to complex multi-step flows.

Authorlackeyjb
Version1.0.0
LicenseMIT
Token count~3,817
UpdatedJun 5, 2026

Install

Quick install

via npx skills · works with 57+ agents
npx skills add https://github.com/lackeyjb/playwright-skill/tree/main/skills/playwright-skill
Or pick agent:
npx skills add lackeyjb/playwright-skill --skill "Playwright Skill" --agent claude-code
npx skills add lackeyjb/playwright-skill --skill "Playwright Skill" --agent cursor
npx skills add lackeyjb/playwright-skill --skill "Playwright Skill" --agent codex
npx skills add lackeyjb/playwright-skill --skill "Playwright Skill" --agent opencode
npx skills add lackeyjb/playwright-skill --skill "Playwright Skill" --agent github-copilot
npx skills add lackeyjb/playwright-skill --skill "Playwright Skill" --agent windsurf
More install options

Shorthand — useful for multi-skill repos:

npx skills add lackeyjb/playwright-skill --skill "Playwright Skill"

Manual — clone the repo and drop the folder into your agent's skills directory:

git clone https://github.com/lackeyjb/playwright-skill.git
cp -r playwright-skill/skills/playwright-skill ~/.claude/skills/
How to use: Once installed, ask your agent to "use the Playwright Skill skill" or describe what you want (e.g. "Enables Claude to write and execute any Playwright automation on-the-fly - from"). Requires Node.js 18+.

Playwright Skill

Enables Claude to write and execute any Playwright automation on-the-fly - from simple page tests to complex multi-step flows.

Playwright Skillby lackeyjb

Enables Claude to write and execute any Playwright automation on-the-fly - from simple page tests to complex multi-step flows.

npx skills add https://github.com/lackeyjb/playwright-skill --skill playwright-skillDownload ZIPGitHubIMPORTANT - Path Resolution:
This skill can be installed in different locations (plugin system, manual installation, global, or project-specific). Before executing any commands, determine the skill directory based on where you loaded this SKILL.md file, and use that path in all commands below. Replace $SKILL_DIR with the actual discovered path.

Common installation paths:

  • Plugin system: ~/.claude/plugins/marketplaces/playwright-skill/skills/playwright-skill
  • Manual global: ~/.claude/skills/playwright-skill
  • Project-specific: <project>/.claude/skills/playwright-skill

Playwright Browser Automation

General-purpose browser automation skill. I'll write custom Playwright code for any automation task you request and execute it via the universal executor.

CRITICAL WORKFLOW - Follow these steps in order:

*
Auto-detect dev servers - For localhost testing, ALWAYS run server detection FIRST:

`cd $SKILL_DIR && node -e "require('./lib/helpers').detectDevServers().then(servers => console.log(JSON.stringify(servers)))"
`
  • If 1 server found: Use it automatically, inform user
  • If multiple servers found: Ask user which one to test
  • If no servers found: Ask for URL or offer to help start dev server

*
Write scripts to /tmp - NEVER write test files to skill directory; always use /tmp/playwright-test-*.js

*
Use visible browser by default - Always use headless: false unless user specifically requests headless mode

*
Parameterize URLs - Always make URLs configurable via environment variable or constant at top of script

How It Works

  • You describe what you want to test/automate
  • I auto-detect running dev servers (or ask for URL if testing external site)

I write custom Playwright code in /tmp/playwright-test-.js (won't clutter your project)

I execute it via: cd $SKILL_DIR && node run.js /tmp/playwright-test-.js

  • Results displayed in real-time, browser window visible for debugging
  • Test files auto-cleaned from /tmp by your OS

Setup (First Time)

`cd $SKILL_DIR
npm run setup
`

This installs Playwright and Chromium browser. Only needed once.

Execution Pattern

Step 1: Detect dev servers (for localhost testing)

`cd $SKILL_DIR && node -e "require('./lib/helpers').detectDevServers().then(s => console.log(JSON.stringify(s)))"
`

Step 2: Write test script to /tmp with URL parameter

`// /tmp/playwright-test-page.js
const { chromium } = require('playwright');

// Parameterized URL (detected or user-provided)
const TARGET_URL = 'http://localhost:3001'; // <-- Auto-detected or from user

(async () => {
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();

await page.goto(TARGET_URL);
console.log('Page loaded:', await page.title());

await page.screenshot({ path: '/tmp/screenshot.png', fullPage: true });
console.log('📸 Screenshot saved to /tmp/screenshot.png');

await browser.close();
})();
`

Step 3: Execute from skill directory

`cd $SKILL_DIR && node run.js /tmp/playwright-test-page.js
`

Common Patterns

Test a Page (Multiple Viewports)

`// /tmp/playwright-test-responsive.js
const { chromium } = require('playwright');

const TARGET_URL = 'http://localhost:3001'; // Auto-detected

(async () => {
const browser = await chromium.launch({ headless: false, slowMo: 100 });
const page = await browser.newPage();

// Desktop test
await page.setViewportSize({ width: 1920, height: 1080 });
await page.goto(TARGET_URL);
console.log('Desktop - Title:', await page.title());
await page.screenshot({ path: '/tmp/desktop.png', fullPage: true });

// Mobile test
await page.setViewportSize({ width: 375, height: 667 });
await page.screenshot({ path: '/tmp/mobile.png', fullPage: true });

await browser.close();
})();
`

Test Login Flow

`// /tmp/playwright-test-login.js
const { chromium } = require('playwright');

const TARGET_URL = 'http://localhost:3001'; // Auto-detected

(async () => {
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();

await page.goto(`${TARGET_URL}/login`);

await page.fill('input[name="email"]', '[email&#160;protected]');
await page.fill('input[name="password"]', 'password123');
await page.click('button[type="submit"]');

// Wait for redirect
await page.waitForURL('**/dashboard');
console.log('✅ Login successful, redirected to dashboard');

await browser.close();
})();
`

Fill and Submit Form

`// /tmp/playwright-test-form.js
const { chromium } = require('playwright');

const TARGET_URL = 'http://localhost:3001'; // Auto-detected

(async () => {
const browser = await chromium.launch({ headless: false, slowMo: 50 });
const page = await browser.newPage();

await page.goto(`${TARGET_URL}/contact`);

await page.fill('input[name="name"]', 'John Doe');
await page.fill('input[name="email"]', '[email&#160;protected]');
await page.fill('textarea[name="message"]', 'Test message');
await page.click('button[type="submit"]');

// Verify submission
await page.waitForSelector('.success-message');
console.log('✅ Form submitted successfully');

await browser.close();
})();
`

Check for Broken Links

`const { chromium } = require('playwright');

(async () => {
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();

await page.goto('http://localhost:3000');

const links = await page.locator('a[href^="http"]').all();
const results = { working: 0, broken: [] };

for (const link of links) {
const href = await link.getAttribute('href');
try {
const response = await page.request.head(href);
if (response.ok()) {
results.working++;
} else {
results.broken.push({ url: href, status: response.status() });
}
} catch (e) {
results.broken.push({ url: href, error: e.message });
}
}

console.log(`✅ Working links: ${results.working}`);
console.log(`❌ Broken links:`, results.broken);

await browser.close();
})();
`

Take Screenshot with Error Handling

`const { chromium } = require('playwright');

(async () => {
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();

try {
await page.goto('http://localhost:3000', {
waitUntil: 'networkidle',
timeout: 10000,
});

await page.screenshot({
path: '/tmp/screenshot.png',
fullPage: true,
});

console.log('📸 Screenshot saved to /tmp/screenshot.png');
} catch (error) {
console.error('❌ Error:', error.message);
} finally {
await browser.close();
}
})();
`

Test Responsive Design

`// /tmp/playwright-test-responsive-full.js
const { chromium } = require('playwright');

const TARGET_URL = 'http://localhost:3001'; // Auto-detected

(async () => {
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();

const viewports = [
{ name: 'Desktop', width: 1920, height: 1080 },
{ name: 'Tablet', width: 768, height: 1024 },
{ name: 'Mobile', width: 375, height: 667 },
];

for (const viewport of viewports) {
console.log(
`Testing ${viewport.name} (${viewport.width}x${viewport.height})`,
);

await page.setViewportSize({
width: viewport.width,
height: viewport.height,
});

await page.goto(TARGET_URL);
await page.waitForTimeout(1000);

await page.screenshot({
path: `/tmp/${viewport.name.toLowerCase()}.png`,
fullPage: true,
});
}

console.log('✅ All viewports tested');
await browser.close();
})();
`

Inline Execution (Simple Tasks)

For quick one-off tasks, you can execute code inline without creating files:

`# Take a quick screenshot
cd $SKILL_DIR && node run.js "
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();
await page.goto('http://localhost:3001');
await page.screenshot({ path: '/tmp/quick-screenshot.png', fullPage: true });
console.log('Screenshot saved');
await browser.close();
"
`

When to use inline vs files:

  • Inline: Quick one-off tasks (screenshot, check if element exists, get page title)
  • Files: Complex tests, responsive design checks, anything user might want to re-run

Available Helpers

Optional utility functions in lib/helpers.js:

`const helpers = require('./lib/helpers');

// Detect running dev servers (CRITICAL - use this first!)
const servers = await helpers.detectDevServers();
console.log('Found servers:', servers);

// Safe click with retry
await helpers.safeClick(page, 'button.submit', { retries: 3 });

// Safe type with clear
await helpers.safeType(page, '#username', 'testuser');

// Take timestamped screenshot
await helpers.takeScreenshot(page, 'test-result');

// Handle cookie banners
await helpers.handleCookieBanner(page);

// Extract table data
const data = await helpers.extractTableData(page, 'table.results');
`

See lib/helpers.js for full list.

Custom HTTP Headers

Configure custom headers for all HTTP requests via environment variables. Useful for:

  • Identifying automated traffic to your backend
  • Getting LLM-optimized responses (e.g., plain text errors instead of styled HTML)
  • Adding authentication tokens globally

Configuration

Single header (common case):

`PW_HEADER_NAME=X-Automated-By PW_HEADER_VALUE=playwright-skill \
cd $SKILL_DIR && node run.js /tmp/my-script.js
`

Multiple headers (JSON format):

`PW_EXTRA_HEADERS='{"X-Automated-By":"playwright-skill","X-Debug":"true"}' \
cd $SKILL_DIR && node run.js /tmp/my-script.js
`

How It Works

Headers are automatically applied when using helpers.createContext():

`const context = await helpers.createContext(browser);
const page = await context.newPage();
// All requests from this page include your custom headers
`

For scripts using raw Playwright API, use the injected getContextOptionsWithHeaders():

`const context = await browser.newContext(
getContextOptionsWithHeaders({ viewport: { width: 1920, height: 1080 } }),
);
`

Advanced Usage

For comprehensive Playwright API documentation, see API_REFERENCE.md:

  • Selectors & Locators best practices
  • Network interception & API mocking
  • Authentication & session management
  • Visual regression testing
  • Mobile device emulation
  • Performance testing
  • Debugging techniques
  • CI/CD integration

Tips

  • CRITICAL: Detect servers FIRST - Always run detectDevServers() before writing test code for localhost testing
  • Custom headers - Use PW_HEADER_NAME/PW_HEADER_VALUE env vars to identify automated traffic to your backend

Use /tmp for test files - Write to /tmp/playwright-test-.js, never to skill directory or user's project

  • Parameterize URLs - Put detected/provided URL in a TARGET_URL constant at the top of every script
  • DEFAULT: Visible browser - Always use headless: false unless user explicitly asks for headless mode
  • Headless mode - Only use headless: true when user specifically requests "headless" or "background" execution
  • Slow down: Use slowMo: 100 to make actions visible and easier to follow
  • Wait strategies: Use waitForURL, waitForSelector, waitForLoadState instead of fixed timeouts
  • Error handling: Always use try-catch for robust automation
  • Console output: Use console.log() to track progress and show what's happening

Troubleshooting

Playwright not installed:

`cd $SKILL_DIR && npm run setup
`

Module not found:
Ensure running from skill directory via run.js wrapper

Browser doesn't open:
Check headless: false and ensure display available

Element not found:
Add wait: await page.waitForSelector('.element', { timeout: 10000 })

Example Usage

`User: "Test if the marketing page looks good"

Claude: I'll test the marketing page across multiple viewports. Let me first detect running servers...
[Runs: detectDevServers()]
[Output: Found server on port 3001]
I found your dev server running on http://localhost:3001

[Writes custom automation script to /tmp/playwright-test-marketing.js with URL parameterized]
[Runs: cd $SKILL_DIR && node run.js /tmp/playwright-test-marketing.js]
[Shows results with screenshots from /tmp/]
`
`User: "Check if login redirects correctly"

Claude: I'll test the login flow. First, let me check for running servers...
[Runs: detectDevServers()]
[Output: Found servers on ports 3000 and 3001]
I found 2 dev servers. Which one should I test?
- http://localhost:3000
- http://localhost:3001

User: "Use 3001"

[Writes login automation to /tmp/playwright-test-login.js]
[Runs: cd $SKILL_DIR && node run.js /tmp/playwright-test-login.js]
[Reports: ✅ Login successful, redirected to /dashboard]
`

Notes

  • Each automation is custom-written for your specific request
  • Not limited to pre-built scripts - any browser task possible
  • Auto-detects running dev servers to eliminate hardcoded URLs
  • Test scripts written to /tmp for automatic cleanup (no clutter)
  • Code executes reliably with proper module resolution via run.js
  • Progressive disclosure - API_REFERENCE.md loaded only when advanced features needed

Related Skills

azure-ai-textanalytics-pyby microsoftClient library for Azure AI Language service NLP capabilities including sentiment, entities, key phrases, and more.dv-metadataby microsoftDataverse schema authoring via the Python SDK and Web API — tables, columns, relationships, forms, and views. Use when the user wants to define or evolve the…deploying-airflowby astronomerDeploy Airflow DAGs and projects. Use when the user wants to deploy code, push DAGs, set up CI/CD, deploy to production, or asks about deployment strategies…omni-to-snowflake-semantic-viewby exploreomniConvert an Omni Analytics topic into a Snowflake Semantic View YAML definition. Use this skill whenever someone wants to export Omni metrics to Snowflake,…flutter-platform-viewsby flutterEmbed native views and web content into Flutter apps across Android, iOS, macOS, and web platforms. Supports Android Hybrid Composition (native fidelity) and Texture Layer (Flutter performance), iOS/macOS Hybrid Composition, and web full-page or embedded multi-view modes Provides complete Dart and native code templates (Kotlin for Android, Swift for iOS/macOS, JavaScript for web) with factory registration patterns Requires decision tree upfront to determine target platform and embedding...github-scriptby githubBest practices for writing JavaScript code for GitHub Actions using github-scriptawq-quantizationby firecrawlActivation-aware weight quantization for 4-bit LLM compression with 3x speedup and minimal accuracy loss. Use when deploying large models (7B-70B) on limited…skill-creatorby microsoftGuide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating…

---

Source: https://github.com/lackeyjb/playwright-skill/tree/main/skills/playwright-skill
Author: lackeyjb
Discovered via: mcpservers.org

SKILL.md source

---
name: Playwright Skill
description: Enables Claude to write and execute any Playwright automation on-the-fly - from simple page tests to complex multi-step flows.
---

# Playwright Skill

Enables Claude to write and execute any Playwright automation on-the-fly - from simple page tests to complex multi-step flows.

# Playwright Skillby lackeyjb
Enables Claude to write and execute any Playwright automation on-the-fly - from simple page tests to complex multi-step flows.

`npx skills add https://github.com/lackeyjb/playwright-skill --skill playwright-skill`Download ZIPGitHubIMPORTANT - Path Resolution:
This skill can be installed in different locations (plugin system, manual installation, global, or project-specific). Before executing any commands, determine the skill directory based on where you loaded this SKILL.md file, and use that path in all commands below. Replace `$SKILL_DIR` with the actual discovered path.

Common installation paths:

* Plugin system: `~/.claude/plugins/marketplaces/playwright-skill/skills/playwright-skill`

* Manual global: `~/.claude/skills/playwright-skill`

* Project-specific: `<project>/.claude/skills/playwright-skill`

## Playwright Browser Automation

General-purpose browser automation skill. I'll write custom Playwright code for any automation task you request and execute it via the universal executor.

CRITICAL WORKFLOW - Follow these steps in order:

*
Auto-detect dev servers - For localhost testing, ALWAYS run server detection FIRST:

```
`cd $SKILL_DIR && node -e "require('./lib/helpers').detectDevServers().then(servers => console.log(JSON.stringify(servers)))"
`
```

* If 1 server found: Use it automatically, inform user

* If multiple servers found: Ask user which one to test

* If no servers found: Ask for URL or offer to help start dev server

*
Write scripts to /tmp - NEVER write test files to skill directory; always use `/tmp/playwright-test-*.js`

*
Use visible browser by default - Always use `headless: false` unless user specifically requests headless mode

*
Parameterize URLs - Always make URLs configurable via environment variable or constant at top of script

## How It Works

* You describe what you want to test/automate

* I auto-detect running dev servers (or ask for URL if testing external site)

* I write custom Playwright code in `/tmp/playwright-test-*.js` (won't clutter your project)

* I execute it via: `cd $SKILL_DIR && node run.js /tmp/playwright-test-*.js`

* Results displayed in real-time, browser window visible for debugging

* Test files auto-cleaned from /tmp by your OS

## Setup (First Time)

```
`cd $SKILL_DIR
npm run setup
`
```

This installs Playwright and Chromium browser. Only needed once.

## Execution Pattern

Step 1: Detect dev servers (for localhost testing)

```
`cd $SKILL_DIR && node -e "require('./lib/helpers').detectDevServers().then(s => console.log(JSON.stringify(s)))"
`
```

Step 2: Write test script to /tmp with URL parameter

```
`// /tmp/playwright-test-page.js
const { chromium } = require('playwright');

// Parameterized URL (detected or user-provided)
const TARGET_URL = 'http://localhost:3001'; // <-- Auto-detected or from user

(async () => {
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();

await page.goto(TARGET_URL);
console.log('Page loaded:', await page.title());

await page.screenshot({ path: '/tmp/screenshot.png', fullPage: true });
console.log('📸 Screenshot saved to /tmp/screenshot.png');

await browser.close();
})();
`
```

Step 3: Execute from skill directory

```
`cd $SKILL_DIR && node run.js /tmp/playwright-test-page.js
`
```

## Common Patterns

### Test a Page (Multiple Viewports)

```
`// /tmp/playwright-test-responsive.js
const { chromium } = require('playwright');

const TARGET_URL = 'http://localhost:3001'; // Auto-detected

(async () => {
const browser = await chromium.launch({ headless: false, slowMo: 100 });
const page = await browser.newPage();

// Desktop test
await page.setViewportSize({ width: 1920, height: 1080 });
await page.goto(TARGET_URL);
console.log('Desktop - Title:', await page.title());
await page.screenshot({ path: '/tmp/desktop.png', fullPage: true });

// Mobile test
await page.setViewportSize({ width: 375, height: 667 });
await page.screenshot({ path: '/tmp/mobile.png', fullPage: true });

await browser.close();
})();
`
```

### Test Login Flow

```
`// /tmp/playwright-test-login.js
const { chromium } = require('playwright');

const TARGET_URL = 'http://localhost:3001'; // Auto-detected

(async () => {
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();

await page.goto(`${TARGET_URL}/login`);

await page.fill('input[name="email"]', '[email&#160;protected]');
await page.fill('input[name="password"]', 'password123');
await page.click('button[type="submit"]');

// Wait for redirect
await page.waitForURL('**/dashboard');
console.log('✅ Login successful, redirected to dashboard');

await browser.close();
})();
`
```

### Fill and Submit Form

```
`// /tmp/playwright-test-form.js
const { chromium } = require('playwright');

const TARGET_URL = 'http://localhost:3001'; // Auto-detected

(async () => {
const browser = await chromium.launch({ headless: false, slowMo: 50 });
const page = await browser.newPage();

await page.goto(`${TARGET_URL}/contact`);

await page.fill('input[name="name"]', 'John Doe');
await page.fill('input[name="email"]', '[email&#160;protected]');
await page.fill('textarea[name="message"]', 'Test message');
await page.click('button[type="submit"]');

// Verify submission
await page.waitForSelector('.success-message');
console.log('✅ Form submitted successfully');

await browser.close();
})();
`
```

### Check for Broken Links

```
`const { chromium } = require('playwright');

(async () => {
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();

await page.goto('http://localhost:3000');

const links = await page.locator('a[href^="http"]').all();
const results = { working: 0, broken: [] };

for (const link of links) {
const href = await link.getAttribute('href');
try {
const response = await page.request.head(href);
if (response.ok()) {
results.working++;
} else {
results.broken.push({ url: href, status: response.status() });
}
} catch (e) {
results.broken.push({ url: href, error: e.message });
}
}

console.log(`✅ Working links: ${results.working}`);
console.log(`❌ Broken links:`, results.broken);

await browser.close();
})();
`
```

### Take Screenshot with Error Handling

```
`const { chromium } = require('playwright');

(async () => {
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();

try {
await page.goto('http://localhost:3000', {
waitUntil: 'networkidle',
timeout: 10000,
});

await page.screenshot({
path: '/tmp/screenshot.png',
fullPage: true,
});

console.log('📸 Screenshot saved to /tmp/screenshot.png');
} catch (error) {
console.error('❌ Error:', error.message);
} finally {
await browser.close();
}
})();
`
```

### Test Responsive Design

```
`// /tmp/playwright-test-responsive-full.js
const { chromium } = require('playwright');

const TARGET_URL = 'http://localhost:3001'; // Auto-detected

(async () => {
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();

const viewports = [
{ name: 'Desktop', width: 1920, height: 1080 },
{ name: 'Tablet', width: 768, height: 1024 },
{ name: 'Mobile', width: 375, height: 667 },
];

for (const viewport of viewports) {
console.log(
`Testing ${viewport.name} (${viewport.width}x${viewport.height})`,
);

await page.setViewportSize({
width: viewport.width,
height: viewport.height,
});

await page.goto(TARGET_URL);
await page.waitForTimeout(1000);

await page.screenshot({
path: `/tmp/${viewport.name.toLowerCase()}.png`,
fullPage: true,
});
}

console.log('✅ All viewports tested');
await browser.close();
})();
`
```

## Inline Execution (Simple Tasks)

For quick one-off tasks, you can execute code inline without creating files:

```
`# Take a quick screenshot
cd $SKILL_DIR && node run.js "
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();
await page.goto('http://localhost:3001');
await page.screenshot({ path: '/tmp/quick-screenshot.png', fullPage: true });
console.log('Screenshot saved');
await browser.close();
"
`
```

When to use inline vs files:

* Inline: Quick one-off tasks (screenshot, check if element exists, get page title)

* Files: Complex tests, responsive design checks, anything user might want to re-run

## Available Helpers

Optional utility functions in `lib/helpers.js`:

```
`const helpers = require('./lib/helpers');

// Detect running dev servers (CRITICAL - use this first!)
const servers = await helpers.detectDevServers();
console.log('Found servers:', servers);

// Safe click with retry
await helpers.safeClick(page, 'button.submit', { retries: 3 });

// Safe type with clear
await helpers.safeType(page, '#username', 'testuser');

// Take timestamped screenshot
await helpers.takeScreenshot(page, 'test-result');

// Handle cookie banners
await helpers.handleCookieBanner(page);

// Extract table data
const data = await helpers.extractTableData(page, 'table.results');
`
```

See `lib/helpers.js` for full list.

## Custom HTTP Headers

Configure custom headers for all HTTP requests via environment variables. Useful for:

* Identifying automated traffic to your backend

* Getting LLM-optimized responses (e.g., plain text errors instead of styled HTML)

* Adding authentication tokens globally

### Configuration

Single header (common case):

```
`PW_HEADER_NAME=X-Automated-By PW_HEADER_VALUE=playwright-skill \
cd $SKILL_DIR && node run.js /tmp/my-script.js
`
```

Multiple headers (JSON format):

```
`PW_EXTRA_HEADERS='{"X-Automated-By":"playwright-skill","X-Debug":"true"}' \
cd $SKILL_DIR && node run.js /tmp/my-script.js
`
```

### How It Works

Headers are automatically applied when using `helpers.createContext()`:

```
`const context = await helpers.createContext(browser);
const page = await context.newPage();
// All requests from this page include your custom headers
`
```

For scripts using raw Playwright API, use the injected `getContextOptionsWithHeaders()`:

```
`const context = await browser.newContext(
getContextOptionsWithHeaders({ viewport: { width: 1920, height: 1080 } }),
);
`
```

## Advanced Usage

For comprehensive Playwright API documentation, see API_REFERENCE.md:

* Selectors & Locators best practices

* Network interception & API mocking

* Authentication & session management

* Visual regression testing

* Mobile device emulation

* Performance testing

* Debugging techniques

* CI/CD integration

## Tips

* CRITICAL: Detect servers FIRST - Always run `detectDevServers()` before writing test code for localhost testing

* Custom headers - Use `PW_HEADER_NAME`/`PW_HEADER_VALUE` env vars to identify automated traffic to your backend

* Use /tmp for test files - Write to `/tmp/playwright-test-*.js`, never to skill directory or user's project

* Parameterize URLs - Put detected/provided URL in a `TARGET_URL` constant at the top of every script

* DEFAULT: Visible browser - Always use `headless: false` unless user explicitly asks for headless mode

* Headless mode - Only use `headless: true` when user specifically requests "headless" or "background" execution

* Slow down: Use `slowMo: 100` to make actions visible and easier to follow

* Wait strategies: Use `waitForURL`, `waitForSelector`, `waitForLoadState` instead of fixed timeouts

* Error handling: Always use try-catch for robust automation

* Console output: Use `console.log()` to track progress and show what's happening

## Troubleshooting

Playwright not installed:

```
`cd $SKILL_DIR && npm run setup
`
```

Module not found:
Ensure running from skill directory via `run.js` wrapper

Browser doesn't open:
Check `headless: false` and ensure display available

Element not found:
Add wait: `await page.waitForSelector('.element', { timeout: 10000 })`

## Example Usage

```
`User: "Test if the marketing page looks good"

Claude: I'll test the marketing page across multiple viewports. Let me first detect running servers...
[Runs: detectDevServers()]
[Output: Found server on port 3001]
I found your dev server running on http://localhost:3001

[Writes custom automation script to /tmp/playwright-test-marketing.js with URL parameterized]
[Runs: cd $SKILL_DIR && node run.js /tmp/playwright-test-marketing.js]
[Shows results with screenshots from /tmp/]
`
```

```
`User: "Check if login redirects correctly"

Claude: I'll test the login flow. First, let me check for running servers...
[Runs: detectDevServers()]
[Output: Found servers on ports 3000 and 3001]
I found 2 dev servers. Which one should I test?
- http://localhost:3000
- http://localhost:3001

User: "Use 3001"

[Writes login automation to /tmp/playwright-test-login.js]
[Runs: cd $SKILL_DIR && node run.js /tmp/playwright-test-login.js]
[Reports: ✅ Login successful, redirected to /dashboard]
`
```

## Notes

* Each automation is custom-written for your specific request

* Not limited to pre-built scripts - any browser task possible

* Auto-detects running dev servers to eliminate hardcoded URLs

* Test scripts written to `/tmp` for automatic cleanup (no clutter)

* Code executes reliably with proper module resolution via `run.js`

* Progressive disclosure - API_REFERENCE.md loaded only when advanced features needed

## Related Skills
azure-ai-textanalytics-pyby microsoftClient library for Azure AI Language service NLP capabilities including sentiment, entities, key phrases, and more.dv-metadataby microsoftDataverse schema authoring via the Python SDK and Web API — tables, columns, relationships, forms, and views. Use when the user wants to define or evolve the…deploying-airflowby astronomerDeploy Airflow DAGs and projects. Use when the user wants to deploy code, push DAGs, set up CI/CD, deploy to production, or asks about deployment strategies…omni-to-snowflake-semantic-viewby exploreomniConvert an Omni Analytics topic into a Snowflake Semantic View YAML definition. Use this skill whenever someone wants to export Omni metrics to Snowflake,…flutter-platform-viewsby flutterEmbed native views and web content into Flutter apps across Android, iOS, macOS, and web platforms. Supports Android Hybrid Composition (native fidelity) and Texture Layer (Flutter performance), iOS/macOS Hybrid Composition, and web full-page or embedded multi-view modes Provides complete Dart and native code templates (Kotlin for Android, Swift for iOS/macOS, JavaScript for web) with factory registration patterns Requires decision tree upfront to determine target platform and embedding...github-scriptby githubBest practices for writing JavaScript code for GitHub Actions using github-scriptawq-quantizationby firecrawlActivation-aware weight quantization for 4-bit LLM compression with 3x speedup and minimal accuracy loss. Use when deploying large models (7B-70B) on limited…skill-creatorby microsoftGuide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating…

---

**Source**: https://github.com/lackeyjb/playwright-skill/tree/main/skills/playwright-skill
**Author**: lackeyjb
**Discovered via**: mcpservers.org

Related skills 6

agent-browser

★ Featured Official

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use...

vercel-labs 297k
Testing & Quality

grill-me

★ Featured

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

mattpocock 192k
Testing & Quality

grill-with-docs

★ Featured

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

mattpocock 138k
Testing & Quality

minimal-run-and-audit

★ Featured

RigorPilot trusted execution and reporting skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end...

lllllllama 127k
Testing & Quality

polish

★ Featured

Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.

pbakaus 86k
Testing & Quality

critique

★ Featured

Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.

pbakaus 83k
Testing & Quality