playwright-master

Browser automation expert - E2E tests, web scraping, UI testing

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/playwright-master/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

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

The body is lean, executable, and well-organized with strong copy-paste-ready examples across the main use cases. Its main weakness is the absence of an explicit sequenced workflow with validation/checkpoint steps for automation runs, which caps workflow clarity.

Suggestions

Add a brief ordered workflow (e.g. navigate -> interact -> assert -> record artifacts) with an explicit validation/assertion checkpoint before teardown, so automation runs fail fast.

For the scraping example, add error handling and a verify step (e.g. assert products array is non-empty) before browser.close().

Consider splitting the page-objects and API-interception detail into a reference file once the skill grows, to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is section-driven with minimal prose and no explaining of concepts Claude already knows (e.g. what Playwright is); only minor tightening possible in the longer code blocks, fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	Concrete, copy-paste-ready TypeScript examples cover the common cases (login flow, selectors, waits, page objects, scraping) and include specific assertions, matching 'fully executable; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The content is a set of patterns rather than a sequenced workflow, and there are no validation checkpoints or feedback loops; since browser automation is a batch/automation context where the rubric requires validation to exceed 3, it is capped at 3.	3 / 5
Progressive Disclosure	Content is well organized into clearly labeled sections (Test Structure, Best Practices, Web Scraping) with no nested references and no bundle files to misplace; it is slightly over the simple-skill line so does not reach a clean 5, but structure is good.	4 / 5
	Total	16 / 20 Passed

Description

55%Weight 40%Scale 1-5

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

The description is concise and names concrete capabilities, but it omits any explicit "Use when..." trigger guidance, which caps both completeness and trigger-term quality. It is reasonably distinct but has minor overlap risk with general testing skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing E2E tests, scraping web pages, recording browser sessions, or emulating mobile browsers."

Include synonyms and file/term variations users actually say (e.g. "Playwright", "end-to-end tests", "browser testing", "crawler") to improve trigger coverage.

Tighten distinctiveness by foregrounding Playwright-specific context so it does not collide with generic test-runner skills.

Dimension	Reasoning	Score
Specificity	Names the domain (browser automation) and several concrete actions ("E2E tests, web scraping, UI testing"), with only minor coverage gaps, fitting the 'several specific actions' anchor.	4 / 5
Completeness	The description gives a clear "what" but no "when"/"Use when" guidance; per the rubric a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant natural terms like "E2E tests", "web scraping", and "UI testing", but lacks common variations/synonyms and is missing explicit user-phrase triggers; sits between generic and good coverage.	3 / 5
Distinctiveness Conflict Risk	Browser automation is a recognizable niche, but broad terms like "UI testing" overlap with general test/dev skills, so it could still trigger for the wrong skill.	3 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: TurnaboutHero/oh-my-antigravity
Path: skills/playwright-master/SKILL.md
Commit: f73e1ff

Reviewed: 15 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.