Back to catalog
Human reviewedDevelopment

Skill dossier

playwright-expert

Source declaration

Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness.

The author's original description, preserved in English. It describes intent, not verified performance.

Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

A Playwright E2E testing Skill that favors role-based locators, Page Objects and auto-waiting, with a trace-based workflow for debugging flaky tests.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Writes tests with role-based selectors and Page Object classes.
  • Avoids waitForTimeout and brittle CSS class selectors.
  • Enables traces and screenshots and uses the trace viewer to debug flakiness.
  • Configures parallel runs and CI integration.

Limitations & scope

  • Needs a running application and a Playwright setup to execute tests.
  • API mocking and configuration details are in separate reference files.
  • Visual regression is a trigger term, but the file shows no example.

Relevant for

  • QA and test automation engineers
  • Frontend teams adding E2E coverage
  • Developers fighting flaky tests

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
21.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/playwright-expert/references/api-mocking.mdReference3.1 KB
skills/playwright-expert/references/configuration.mdReference3.2 KB
skills/playwright-expert/references/debugging-flaky.mdReference3.1 KB
skills/playwright-expert/references/page-object-model.mdReference3.6 KB
skills/playwright-expert/references/selectors-locators.mdReference2.7 KB
skills/playwright-expert/SKILL.mdInstruction5.6 KB

SKILL.md frontmatter

{
  "name": "playwright-expert",
  "description": "Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "quality",
    "triggers": "Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing",
    "role": "specialist",
    "scope": "testing",
    "output-format": "code",
    "related-skills": "test-master, react-expert, devops-engineer"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Identify user flows

    Analyze requirements and identify the user flows to test.

  2. 02
    Action

    Set up and write tests

    Configure Playwright and write tests with Page Objects, proper selectors and auto-waiting.

  3. 03
    Decision

    Debug with traces

    Run the test, check the trace, identify the issue, fix and verify the fix.

  4. 04
    Output

    Deliver tests and config

    Provide Page Objects, test files with assertions, fixtures and configuration recommendations.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

52 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Note

File modification is described or implemented

39 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 39 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

11 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 11 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

2 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Check which environment the tests target and keep credentials out of test code before running them.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/playwright-expert # .claude/skills/playwright-expert
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/playwright-expert/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Ask Claude Code to write a login test and confirm it uses getByRole or getByLabel, a Page Object and no waitForTimeout.

Prerequisites

  • Needs a running application and a Playwright setup to execute tests.
  • API mocking and configuration details are in separate reference files.
  • Visual regression is a trigger term, but the file shows no example.

Example prompts

Representative task

Using the playwright-expert skill, write a LoginPage page object and specs for successful login and invalid credentials, with traces on first retry, then explain how to debug a flaky run.

Inspect before use

Read the playwright-expert skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/playwright-expert/SKILL.md and its reference files. Explain its workflow, any commands it tells the agent to run, and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Gives a concrete debug loop using traces and repeat runs.
  • Clear do and do-not rules on selectors and waits.

Considerations

  • Page Object Model adds structure that may be heavy for small suites.
  • E2E tests against shared environments can create or alter data.
Research conclusion

A pragmatic guide to maintainable Playwright suites and flaky-test triage.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/playwright-expert
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.