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

73%

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

65%

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

An admirably lean, well-structured index that appropriately defers detail to referenced guides, but it is undermined because those guide files are missing from the bundle. The body itself offers navigation rather than executable guidance.

Suggestions

Add the missing bundle files page-object-model.md and pom-vs-fixtures-vs-helpers.md (or place them under references/) so the signaled links resolve.

Include a brief one-line orienting action in the body (e.g. how to pick which guide to consult first) so the overview is minimally actionable even before opening a guide.

Verify referenced paths match actual bundle locations; dead links currently cap progressive_disclosure at 2.

Dimension	Reasoning	Score
Conciseness	The body is a lean index with no padding and no explanation of concepts Claude already knows; every token earns its place.	3 / 3
Actionability	The guide table gives concrete navigational guidance (which guide covers which topic), but the body provides no executable instruction itself and the referenced guides are not present, so key details are missing.	2 / 3
Workflow Clarity	Content is clear and well-organized for a simple index skill, but no multi-step process or sequence is described in the body — it only points to where processes would live.	2 / 3
Progressive Disclosure	Structure is sound — a one-level-deep table with well-signaled links — but the referenced files (page-object-model.md, pom-vs-fixtures-vs-helpers.md) do not exist in any bundle directory, so the promised navigation is broken.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 specific, distinctive description with strong natural trigger terms, weakened only by the absence of an explicit "Use when..." activation clause. The "when" guidance addresses internal POM-vs-fixture decisions rather than when Claude should invoke the skill.

Suggestions

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

Reframe the "when" guidance to reference user situations (mentioning Playwright tests, page objects, or test maintainability) rather than only internal design choices.

Dimension	Reasoning	Score
Specificity	"when to use POM, how to structure page objects, and when fixtures or helpers are a better fit" lists multiple concrete capability areas rather than vague abstractions.	3 / 3
Completeness	It answers what (POM patterns, structuring page objects) and offers decision guidance ("when to use POM", "when fixtures or helpers are a better fit"), but lacks an explicit "Use when..." skill-activation trigger, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Natural terms a Playwright user would say are well covered: "Page Object Model", "POM", "page objects", "fixtures", "helpers", and "Playwright".	3 / 3
Distinctiveness Conflict Risk	"Page Object Model patterns for Playwright" carves a clear, narrow niche unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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: af7d491

Reviewed: about 9 hours 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.