playwright-testing

Playwright E2E testing patterns, cross-browser configuration, page objects, and CI setup. Use when creating E2E specs, visual regression suites, or configuring Playwright in CI. Trigger terms: playwright, e2e, trace, page object, cross-browser

Quality

96%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

92%

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

This is a strong, well-crafted skill that provides highly actionable Playwright guidance with executable code examples, efficient use of tokens, and a clear workflow with validation checkpoints. The main weakness is in progressive disclosure: references to external files (REFERENCE.md, testing-config.md) exist but aren't verified by bundle contents and could be more prominently organized.

Suggestions

Add a clear navigation section (e.g., '## Further Reading') that consolidates all external file references (testing-config.md, REFERENCE.md) with brief descriptions of what each contains.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It avoids explaining what Playwright is or how testing frameworks work. Every section delivers concrete commands, code, or non-obvious tips without padding.	3 / 3
Actionability	Provides fully executable code examples throughout: bash commands, TypeScript test patterns, API mocking, locator strategies, and a complete playwright.config.ts. All examples are copy-paste ready.	3 / 3
Workflow Clarity	The 'Quick Workflow' section provides a clear 5-step sequence with an explicit validation checkpoint (step 4: confirm 0 failures and trace IDs) and a feedback loop (step 5: fix and re-verify). The workflow covers the write-run-debug-verify cycle well.	3 / 3
Progressive Disclosure	References testing-config.md and REFERENCE.md for advanced content, which is good structure. However, REFERENCE.md is not provided in the bundle, and the reference to it feels tacked on at the end of the config section rather than being clearly signaled in a navigation section. The skill is moderately well-organized but could better signal its external references.	2 / 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.

This is a strong skill description that concisely covers what the skill does, when to use it, and provides explicit trigger terms. It uses third-person voice appropriately, lists concrete capabilities, and is clearly distinguishable from other skills. The explicit trigger terms section is a nice touch that aids skill selection.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: E2E testing patterns, cross-browser configuration, page objects, and CI setup. These are distinct, actionable capabilities rather than vague language.	3 / 3
Completeness	Clearly answers both 'what' (Playwright E2E testing patterns, cross-browser configuration, page objects, CI setup) and 'when' (Use when creating E2E specs, visual regression suites, or configuring Playwright in CI), with explicit trigger terms listed.	3 / 3
Trigger Term Quality	Includes explicit trigger terms section with natural keywords users would say: 'playwright', 'e2e', 'trace', 'page object', 'cross-browser'. Also includes contextual terms like 'visual regression suites' and 'CI' that users would naturally mention.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to Playwright specifically, with distinct triggers like 'playwright', 'page object', 'trace', and 'cross-browser' that are unlikely to conflict with other testing or CI skills. The niche is well-defined.	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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Commit: 7a69a05

Reviewed: about 1 month 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.