playwright

Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

4.09x

Quality

92%

Does it follow best practices?

Impact

86%

4.09x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body with a clear sequenced workflow, validation checkpoints, feedback loops, and clean one-level-deep references to real bundle files. The only weakness is minor redundancy in the prerequisite/global-install and wrapper-script explanations.

Suggestions

Remove the duplicate global-install instructions — the 'npm install -g @playwright/cli@latest' block appears in both Prerequisite check and Quick start; keep it in one place and cross-reference.

Tighten the Wrapper script section: it re-explains the 'npx --package @playwright/cli playwright-cli' mechanism already implied by the prerequisite/setup sections; a one-line note plus the --help command suffices.

Collapse the prerequisite fallback so the verbatim Node/npm install steps are presented once; the current repetition inflates the token budget without adding new guidance.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and largely assumes Claude's competence, but the global-install instructions are repeated (Prerequisite check and Quick start) and the wrapper-script section re-explains the npx mechanism already shown, so it could be tightened — matching 'mostly efficient but includes some unnecessary explanation'. Not a 3 because of this verbatim redundancy.	2 / 3
Actionability	Provides fully executable, copy-paste-ready bash commands ('"$PWCLI" open', 'snapshot', 'click e15', 'fill e1 "user@example.com"') with concrete examples, matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Core workflow is a clear numbered sequence (1-5) with an explicit prerequisite validation checkpoint ('command -v npx') and a feedback loop ('When a command fails due to a missing ref, snapshot again'), matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	SKILL.md is an overview with a well-signaled References section pointing one level deep to verified bundle files (references/cli.md, references/workflows.md) and the scripts/playwright_cli.sh wrapper, matching the 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concise description that explicitly states both what the skill does (concrete browser-automation actions) and when to use it (explicit 'Use when...' trigger), with natural trigger terms and a distinct niche. Third-person/imperative voice is used correctly with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicit 'Use when the task requires...' clause answers when, and the enumerated action list answers what, satisfying the 'clearly answers both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	Covers natural terms a user would say ('automating a real browser', 'form filling', 'screenshots', 'snapshots', 'data extraction') plus the product name 'playwright-cli', giving good coverage; not the level below, which requires missing common variations.	3 / 3
Distinctiveness Conflict Risk	The niche — terminal browser automation via playwright-cli — is distinct with specific triggers, unlikely to fire for unrelated skills; it is not the level below, which still overlaps with similar skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/skills
Commit: 49f948f

Reviewed: 19 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.