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
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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 clearly defines its scope around Playwright E2E testing with specific capabilities, explicit 'Use when' guidance, and well-chosen trigger terms. It covers both the 'what' and 'when' comprehensively while maintaining a distinct identity that would not easily conflict with other testing-related skills. The description is concise yet thorough, using third-person voice appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: E2E testing patterns, cross-browser configuration, page objects, and CI setup. These are distinct, concrete capabilities within the Playwright domain. | 3 / 3 |
Completeness | Clearly answers both 'what' (Playwright E2E testing patterns, cross-browser configuration, page objects, CI setup) and 'when' (creating E2E specs, visual regression suites, configuring Playwright in CI) with explicit trigger terms listed separately. | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 'playwright', 'e2e', 'trace', 'page object', 'cross-browser'. Also includes contextual terms like 'E2E specs', 'visual regression suites', and 'CI' which are commonly used by developers. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around Playwright specifically. Terms like 'playwright', 'page object', 'trace', and 'cross-browser' are specific enough to avoid conflicts with generic testing or other test framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that delivers dense, actionable Playwright guidance without unnecessary explanation. It covers commands, test patterns, configuration, locator strategy, and debugging workflow with executable examples throughout. The progressive disclosure is well-handled with clear pointers to external references for project-specific and advanced content.
| 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 | Fully executable code examples throughout: bash commands, TypeScript test patterns, config files, API mocking, and locator strategies are all copy-paste ready with realistic examples. | 3 / 3 |
Workflow Clarity | The 'Write → Run → Debug → Verify' workflow is clearly sequenced with an explicit validation checkpoint (step 4: confirm show-report shows 0 failures and trace IDs) and a feedback loop (step 5: fix and re-verify). | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with clear references to external files: project-specific config links to testing-config.md, and advanced config/MCP tools are pointed to REFERENCE.md. References are one level deep and well-signaled. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%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
18c6f2c
- Reviewed
Table of Contents
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.