tessl-labs/playwright-testing
Playwright E2E testing patterns — web-first assertions, user-visible locators, network interception, fixtures, authentication, and parallel execution
98
99%
Does it follow best practices?
Impact
98%
1.81xAverage score across 5 eval scenarios
Passed
No known issues
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 an excellent skill description that hits all the marks. It provides specific technical capabilities, includes natural trigger terms users would actually search for, explicitly states both what it does and when to use it, and carves out a distinct niche in the Playwright/E2E testing space with migration context.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'web-first assertions, user-visible locators, network interception, fixtures, authentication, and parallel execution' - these are all concrete, specific capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Playwright E2E testing patterns — web-first assertions, user-visible locators...') AND when ('Use when building or reviewing E2E tests with Playwright, when setting up browser testing for a web app, or when migrating from Cypress or Selenium'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'E2E tests', 'Playwright', 'browser testing', 'web app', 'Cypress', 'Selenium' - covers the tool name, testing type, and common migration scenarios. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers - specifically targets Playwright E2E testing, mentions competing tools (Cypress, Selenium) for migration scenarios, unlikely to conflict with general testing or other 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 an excellent skill document that demonstrates best practices for technical documentation. It uses the WRONG/RIGHT pattern effectively to show anti-patterns and correct approaches, provides fully executable code examples, and maintains excellent organization. The 'Why it matters' explanations are concise and add genuine value without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is highly efficient, using WRONG/RIGHT patterns that immediately show what to do without explaining basic concepts. Every section earns its place with concrete examples and brief explanations of 'why it matters' that add genuine value. | 3 / 3 |
Actionability | Every section provides fully executable TypeScript code examples that are copy-paste ready. The WRONG/RIGHT pattern makes it immediately clear what to do and what to avoid, with complete code blocks for fixtures, page objects, and configuration. | 3 / 3 |
Workflow Clarity | Multi-step processes like authentication setup are clearly sequenced with explicit file paths and dependencies. The network interception section explicitly warns to set up waitForResponse BEFORE the triggering action to avoid race conditions. The checklist provides a validation checkpoint. | 3 / 3 |
Progressive Disclosure | Content is well-organized into numbered sections with clear headings. References to official Playwright docs are provided at the end for deeper exploration. The skill is appropriately self-contained while pointing to external resources for advanced topics. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents