playwright-pom

Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/playwright/pom/SKILL.md

Quality

Content

67%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 a model of conciseness and clean progressive-disclosure structure as a guide index, but it provides no actionable instruction itself and its two referenced guide files are missing from the bundle, leaving the links dangling.

Suggestions

Ship the referenced bundle files page-object-model.md and pom-vs-fixtures-vs-helpers.md so the index links resolve.

Add a one-line fallback telling Claude what to do if neither guide clearly matches the user's question (e.g. default to pom-vs-fixtures-vs-helpers.md).

Include a minimal concrete snippet or decision rule inline so the skill is actionable even before the linked guides are opened.

Dimension	Reasoning	Score
Conciseness	Extremely lean hub page — a one-line framing quote, a guide count, and a two-row index table; every token earns its place and no background concepts are over-explained.	5 / 5
Actionability	The body offers only file links with no concrete steps, code, or commands; it describes where guidance lives rather than instructing, and the linked files are not present in the bundle to deliver that guidance.	2 / 5
Workflow Clarity	As a simple under-50-line single-purpose skill the single action (consult the matching guide) is unambiguous via the topic table; no destructive or batch operation is present so validation checkpoints are not required, though no fallback for an ambiguous topic is given.	4 / 5
Progressive Disclosure	Structure is an ideal one-level-deep hub with a clearly signaled index table, but the two referenced files (page-object-model.md, pom-vs-fixtures-vs-helpers.md) do not exist on disk, so the references are broken despite being well organized.	4 / 5
	Total	15 / 20 Passed

Description

66%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 specific, third-person, and well-scoped to a distinct Playwright niche, with good natural trigger terms. Its main weakness is the absence of an explicit "Use when..." invocation clause, which caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing or refactoring Playwright tests and deciding how to structure page interactions."

Surface a couple more natural user phrases (e.g. "test maintainability", "refactoring Playwright tests") to broaden trigger coverage.

Clarify the invocation trigger separately from the content description so "when to use POM" is not read as merely a topic list.

Dimension	Reasoning	Score
Specificity	Lists several specific coverage areas — "when to use POM", "how to structure page objects", "when fixtures or helpers are a better fit" — naming the domain plus concrete guidance topics, with only minor gaps.	4 / 5
Completeness	The "what" is clear (POM patterns for Playwright), but there is no "Use when..." clause or equivalent explicit invocation trigger — the "when to use POM" phrasing describes content rather than telling Claude when to invoke the skill, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms a developer would say ("Page Object Model", "POM", "Playwright", "page objects", "fixtures", "helpers"); a few related phrases like "test structure" or "test maintainability" are absent.	4 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche (Playwright POM and the POM-vs-fixtures-vs-helpers decision), mostly distinct with only minor overlap risk against a general Playwright testing skill.	4 / 5
	Total	15 / 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
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: zebbern/claude-code-guide
Path: skills/playwright/pom/SKILL.md
Commit: 4eaf4ff

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