Name: playwright-test
Rating: 93.6 (1 reviews)
Author: AI-Unified-Process

playwright-test

Creates Playwright browser-based end-to-end tests for Angular views using Playwright's native accessibility-first locators (getByRole, getByLabelText, getByText). Use when the user asks to "write Playwright tests", "create e2e tests", "write integration tests", "test in the browser", or mentions end-to-end testing, browser tests, or UI integration tests for this stack. Also trigger when the user references a use case (UC-*) and asks for Playwright or E2E tests.

1.00x

Quality

91%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is ai-unified-process/aiup-angular-jpa

Quality

Content

88%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.

A highly actionable, well-structured skill body with executable examples and a clear validated workflow. The main improvement opportunity is trimming a few explanatory asides to improve token efficiency.

Suggestions

Trim the Vaadin shadow-DOM comparison and other non-Angular framing; keep only the directive to use role/label/text locators.

Consider moving the assertions table and locating-elements reference into a references/ file so the SKILL.md body stays a lean overview.

Tighten the 'Important — This Is a Green-Field Decision' prose to a short checklist of files to check before scaffolding.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete code and tight sections, but a few passages over-explain (e.g. the Vaadin shadow-DOM comparison and the green-field framing) that could be trimmed without losing clarity.	4 / 5
Actionability	Provides copy-paste ready config, test examples, locator patterns, interaction snippets, an assertions table, and exact run/debug commands covering the common cases.	5 / 5
Workflow Clarity	An explicit 8-step workflow with a verification step (run tests) and a failure feedback loop (confirm servers, verify Flyway data, use --debug/--headed), plus a reconciliation checklist for pre-existing tests.	5 / 5
Progressive Disclosure	Well-organized into clear sections with well-signaled one-level references (module-layout.md, mcp-servers.md); no bundle files exist to split into, though some inline reference material (assertions/locators) could live in separate files.	4 / 5
	Total	18 / 20 Passed

Description

95%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.

A strong, third-person description that clearly states the capability and gives rich, natural trigger phrases. The only minor gap is that it describes essentially one action (create tests) with implementation detail rather than a list of distinct actions.

Dimension	Reasoning	Score
Specificity	Names the domain (Playwright e2e tests for Angular views) and concrete actions with specific locator types (getByRole, getByLabelText, getByText); falls just short of comprehensive multi-action coverage, which keeps it at 4 rather than 5.	4 / 5
Completeness	Explicitly answers both what (creates Playwright e2e tests for Angular views using accessibility-first locators) and when (a concrete 'Use when...' clause with multiple trigger phrases and an additional UC-* trigger).	5 / 5
Trigger Term Quality	Covers a comprehensive set of natural phrases users would say ('write Playwright tests', 'create e2e tests', 'write integration tests', 'test in the browser', 'end-to-end testing', 'browser tests', 'UI integration tests') plus the UC-* use case trigger.	5 / 5
Distinctiveness Conflict Risk	A clear niche (Playwright e2e for Angular on this specific stack) with distinct, stack-specific triggers minimizes overlap with other testing skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: AI-Unified-Process/marketplace
Path: aiup-angular-jpa/skills/playwright-test/SKILL.md
Commit: c3a5da3

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