Playwright Skill logo

Playwright Skill

Organization
LambdaTest
playwright-skill

Generates production-grade Playwright automation scripts and E2E tests in TypeScript, JavaScript, Python, Java, or C#. Supports local execution and TestMu AI cloud across 3000+ browser/OS combinations and real mobile devices. Use when the user asks to write Playwright tests, automate browsers, run cross-browser tests, test on real devices, debug flaky tests, mock APIs, or do visual regression. Triggers on: "Playwright", "E2E test", "browser test", "run on cloud", "cross-browser", "TestMu", "LambdaTest", "test my app", "test on mobile", "real device".

Overview

PublisherLambdaTest
Repositoryagent-skills
Skill nameplaywright-skill
Stars
377
Forks
74
Bundled files
13
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 13 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by LambdaTest on GitHub. Read the source before you install it.

Installation

Install the Playwright Skill AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/LambdaTest/agent-skills/tree/main/playwright-skill
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/LambdaTest/agent-skills.git /tmp/agent-skills
mkdir -p .claude/skills
cp -r /tmp/agent-skills/playwright-skill .claude/skills/playwright-skill
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Playwright Skill in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Playwright Skill on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Playwright Skill is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Playwright Test Automation

Step 1 — Determine Execution Target

Decide BEFORE writing any code:

User says...TargetAction
No cloud mention, "locally", "debug"LocalStandard Playwright config
"cloud", "TestMu", "LambdaTest", "cross-browser", "real device"CloudSee reference/cloud-integration.md
Impossible local combo (Safari on Windows, Edge on Linux)CloudSuggest TestMu AI, see reference/cloud-integration.md
"HyperExecute", "parallel at scale"HyperExecuteDefer to hyperexecute-skill
"visual regression", "screenshot comparison"SmartUIDefer to smartui-skill
AmbiguousLocalDefault local, mention cloud option

Step 2 — Detect Language

SignalLanguageDefault
"TypeScript", "TS", .ts, or no language specifiedTypeScript✅
"JavaScript", "JS", .jsJavaScript
"Python", "pytest", .pyPythonSee reference/python-patterns.md
"Java", "Maven", "Gradle", "TestNG"JavaSee reference/java-patterns.md
"C#", ".NET", "NUnit", "MSTest"C#See reference/csharp-patterns.md

Step 3 — Determine Scope

Request typeOutput
One-off quick scriptStandalone .ts file, no POM
Single test for existing projectMatch their structure and conventions
New test suite / projectFull scaffold — see scripts/scaffold-project.sh
Fix flaky testDebugging checklist — see reference/debugging-flaky.md
API mocking neededSee reference/api-mocking-visual.md
Mobile device testingSee reference/mobile-testing.md

Core Patterns — TypeScript (Default)

Selector Priority

Use in this order — stop at the first that works:

  1. getByRole('button', { name: 'Submit' }) — accessible, resilient
  2. getByLabel('Email') — form fields
  3. getByPlaceholder('Enter email') — when label missing
  4. getByText('Welcome') — visible text
  5. getByTestId('submit-btn') — last resort, needs data-testid

Never use raw CSS/XPath unless matching a third-party widget with no other option.

Assertions — Always Web-First

typescript
// ✅ Auto-retries until timeout
await expect(page.getByRole('heading')).toBeVisible();
await expect(page.getByRole('alert')).toHaveText('Saved');
await expect(page).toHaveURL('/dashboard');

// ❌ No auto-retry — races with DOM
const text = await page.textContent('.msg');
expect(text).toBe('Saved');

Anti-Patterns

❌ Don't✅ DoWhy
page.waitForTimeout(3000)await expect(locator).toBeVisible()Hard waits are flaky
expect(await el.isVisible())await expect(el).toBeVisible()No auto-retry
page.$('.btn')page.getByRole('button')Fragile selector
page.click('.submit')page.getByRole('button', {name:'Submit'}).click()Not accessible
Shared state between teststest.beforeEach for setupTests must be independent
try/catch around assertionsLet Playwright handle retriesSwallows real failures

Page Object Model

Use POM for any project with more than 3 tests. Full patterns with base page, fixtures, and examples in reference/page-object-model.md.

Quick example:

typescript
// pages/login.page.ts
import { Page, Locator } from '@playwright/test';

export class LoginPage {
  readonly emailInput: Locator;
  readonly passwordInput: Locator;
  readonly submitButton: Locator;

  constructor(private page: Page) {
    this.emailInput = page.getByLabel('Email');
    this.passwordInput = page.getByLabel('Password');
    this.submitButton = page.getByRole('button', { name: 'Sign in' });
  }

  async login(email: string, password: string) {
    await this.emailInput.fill(email);
    await this.passwordInput.fill(password);
    await this.submitButton.click();
  }
}

Configuration — Local

typescript
// playwright.config.ts
import { defineConfig, devices } from '@playwright/test';

export default defineConfig({
  testDir: './tests',
  timeout: 30_000,
  retries: process.env.CI ? 2 : 0,
  workers: process.env.CI ? 1 : undefined,
  reporter: [['html'], ['list']],
  use: {
    baseURL: 'http://localhost:3000',
    trace: 'on-first-retry',
    screenshot: 'only-on-failure',
  },
  projects: [
    { name: 'chromium', use: { ...devices['Desktop Chrome'] } },
    { name: 'firefox', use: { ...devices['Desktop Firefox'] } },
    { name: 'webkit', use: { ...devices['Desktop Safari'] } },
    { name: 'mobile-chrome', use: { ...devices['Pixel 5'] } },
    { name: 'mobile-safari', use: { ...devices['iPhone 13'] } },
  ],
  webServer: {
    command: 'npm run dev',
    port: 3000,
    reuseExistingServer: !process.env.CI,
  },
});

Cloud Execution on TestMu AI

Set environment variables: LT_USERNAME, LT_ACCESS_KEY

Direct CDP connection (standard approach):

typescript
// lambdatest-setup.ts
import { chromium } from 'playwright';

const capabilities = {
  browserName: 'Chrome',
  browserVersion: 'latest',
  'LT:Options': {
    platform: 'Windows 11',
    build: 'Playwright Build',
    name: 'Playwright Test',
    user: process.env.LT_USERNAME,
    accessKey: process.env.LT_ACCESS_KEY,
    network: true,
    video: true,
    console: true,
  },
};

const browser = await chromium.connect({
  wsEndpoint: `wss://cdp.lambdatest.com/playwright?capabilities=${encodeURIComponent(JSON.stringify(capabilities))}`,
});
const context = await browser.newContext();
const page = await context.newPage();

HyperExecute project approach (for parallel cloud runs):

typescript
// Add to projects array in playwright.config.ts:
{
  name: 'chrome:latest:Windows 11@lambdatest',
  use: { viewport: { width: 1920, height: 1080 } },
},
{
  name: 'MicrosoftEdge:latest:macOS Sonoma@lambdatest',
  use: { viewport: { width: 1920, height: 1080 } },
},

Run: npx playwright test --project="chrome:latest:Windows 11@lambdatest"

Test Status Reporting (Cloud)

Tests on TestMu AI show "Completed" by default. You MUST report pass/fail:

typescript
// In afterEach or test teardown:
await page.evaluate((_) => {},
  `lambdatest_action: ${JSON.stringify({
    action: 'setTestStatus',
    arguments: { status: testInfo.status, remark: testInfo.error?.message || 'OK' },
  })}`
);

This is handled automatically when using the fixture from reference/cloud-integration.md.


Validation Workflow

After generating any test:

1. Validate config:  python scripts/validate-config.py playwright.config.ts
2. If errors → fix → re-validate
3. Run locally:      npx playwright test --project=chromium
4. If cloud:         npx playwright test --project="chrome:latest:Windows 11@lambdatest"
5. If failures → check reference/debugging-flaky.md

Quick Reference

Common Commands

bash
npx playwright test                          # Run all tests
npx playwright test --ui                     # Interactive UI mode
npx playwright test --debug                  # Step-through debugger
npx playwright test --project=chromium       # Single browser
npx playwright test tests/login.spec.ts      # Single file
npx playwright show-report                   # Open HTML report
npx playwright codegen https://example.com   # Record test
npx playwright test --update-snapshots       # Update visual baselines

Auth State Reuse

typescript
// Save auth state once in global setup
await page.context().storageState({ path: 'auth.json' });

// Reuse in config
use: { storageState: 'auth.json' }

Visual Regression (Built-in)

typescript
await expect(page).toHaveScreenshot('homepage.png', {
  maxDiffPixelRatio: 0.01,
  animations: 'disabled',
  mask: [page.locator('.dynamic-date')],
});

Network Mocking

typescript
await page.route('**/api/users', (route) =>
  route.fulfill({ json: [{ id: 1, name: 'Mock User' }] })
);

Full mocking patterns in reference/api-mocking-visual.md.

Test Steps for Readability

typescript
test('checkout flow', async ({ page }) => {
  await test.step('Add item to cart', async () => {
    await page.goto('/products');
    await page.getByRole('button', { name: 'Add to cart' }).click();
  });

  await test.step('Complete checkout', async () => {
    await page.getByRole('link', { name: 'Cart' }).click();
    await page.getByRole('button', { name: 'Checkout' }).click();
  });
});

Reference Files

FileWhen to read
reference/cloud-integration.mdCloud execution, 3 integration patterns, parallel browsers
reference/page-object-model.mdPOM architecture, base page, fixtures, full examples
reference/mobile-testing.mdAndroid + iOS real device testing
reference/debugging-flaky.mdFlaky test checklist, common fixes
reference/api-mocking-visual.mdAPI mocking + visual regression patterns
reference/python-patterns.mdPython-specific: pytest-playwright, sync/async
reference/java-patterns.mdJava-specific: Maven, JUnit, Gradle
reference/csharp-patterns.mdC#-specific: NUnit, MSTest, .NET config
../shared/testmu-cloud-reference.mdFull device catalog, capabilities, geo-location

Advanced Playbook

For production-grade patterns, see reference/playbook.md:

SectionWhat's Inside
§1 Production ConfigMulti-project, reporters, retries, webServer
§2 Auth Fixture ReusestorageState, multi-role fixtures
§3 Page Object ModelBasePage, LoginPage with fluent API
§4 Network InterceptionMock, modify, HAR replay, block resources
§5 Visual RegressionScreenshot comparison, masks, thresholds
§6 File Upload/DownloadfileChooser, setInputFiles, download events
§7 Multi-Tab & DialogsPopup handling, alert/confirm/prompt
§8 Geolocation & EmulationLocation, timezone, locale, color scheme
§9 Custom FixturesDB seeding, API context, auto-teardown
§10 API TestingRequest context, end-to-end API+UI
§11 Accessibilityaxe-core integration, WCAG audits
§12 ShardingCI matrix sharding, report merging
§13 CI/CDGitHub Actions with artifacts
§14 Debugging ToolkitDebug, UI mode, trace viewer, codegen
§15 Debugging Table10 common problems with fixes
§16 Best Practices17-item production checklist

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Playwright Skill AI skill do?

Generates production-grade Playwright automation scripts and E2E tests in TypeScript, JavaScript, Python, Java, or C#. Supports local execution and TestMu AI cloud across 3000+ browser/OS combinations and real mobile devices. Use when the user asks to write Playwright tests, automate browsers, run cross-browser tests, test on real devices, debug flaky tests, mock APIs, or do visual regression. Triggers on: "Playwright", "E2E test", "browser test", "run on cloud", "cross-browser", "TestMu", "LambdaTest", "test my app", "test on mobile", "real device".

Why use Playwright Skill on TypingMind?

Because you install it once and use it with any model. Playwright Skill is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Playwright Skill in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/LambdaTest/agent-skills/tree/main/playwright-skill. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Playwright Skill?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Playwright Skill?

As many as you like. As long as a model supports skills, you can use Playwright Skill with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Playwright Skill AI skill free?

Yes. It is published on GitHub by LambdaTest under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇