e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
80
66%
Does it follow best practices?
Impact
89%
1.27xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/developer-essentials/skills/e2e-testing-patterns/SKILL.mdQuality
Discovery
89%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 solid skill description that clearly identifies its domain (E2E testing with Playwright and Cypress) and includes an explicit 'Use when' clause with good trigger terms. Its main weakness is that the capability descriptions lean slightly toward aspirational language ('catch bugs, improve confidence, enable fast deployment') rather than listing more concrete specific actions the skill teaches.
Suggestions
Replace the aspirational phrases ('catch bugs, improve confidence, enable fast deployment') with more concrete actions like 'write page object models, configure test retries, set up CI pipelines for test execution, handle test selectors'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (end-to-end testing) and tools (Playwright, Cypress), and mentions some actions like 'build reliable test suites', 'debugging flaky tests', 'establishing testing standards', but these are somewhat high-level rather than concrete specific actions like 'write page object models' or 'configure test retries'. | 2 / 3 |
Completeness | Clearly answers both 'what' (build reliable test suites with Playwright and Cypress) and 'when' with an explicit 'Use when' clause covering implementing E2E tests, debugging flaky tests, and establishing testing standards. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'Playwright', 'Cypress', 'E2E tests', 'flaky tests', 'testing standards', 'end-to-end testing'. These cover common variations of how users would describe their needs. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on Playwright and Cypress specifically for E2E testing creates a clear niche. The mention of specific tools and 'flaky tests' makes it unlikely to conflict with unit testing, API testing, or other testing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at providing concrete, executable code examples across both Playwright and Cypress, making it highly actionable. However, it is severely bloated — explaining basic concepts Claude already knows (testing pyramid, what E2E tests are for), duplicating advice across sections (selectors, flaky tests mentioned multiple times), and cramming everything into a single monolithic file. The content would benefit greatly from aggressive trimming and splitting into referenced sub-documents.
Suggestions
Remove the 'Core Concepts' section entirely — Claude already understands testing pyramids, what E2E tests are, and what should/shouldn't be tested at the E2E level.
Split Playwright patterns, Cypress patterns, and Advanced patterns into separate referenced files (e.g., PLAYWRIGHT.md, CYPRESS.md, ADVANCED.md) with a concise overview in the main skill.
Consolidate the redundant 'Best Practices' and 'Common Pitfalls' sections — they repeat the same advice (selectors, flaky tests, independence) that's already demonstrated in the code examples.
Add a brief workflow sequence for setting up E2E testing from scratch (install → configure → write first test → run → debug → CI integration) with validation checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines. It explains concepts Claude already knows (testing pyramid, what E2E testing is, what to test vs not), includes redundant best practices sections, and covers two frameworks exhaustively when the content could be much leaner. The 'Core Concepts' section is largely unnecessary padding. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout — complete Playwright configs, Page Object Model implementations, fixture patterns, Cypress commands, network mocking, and accessibility testing. All code is concrete TypeScript, not pseudocode. | 3 / 3 |
Workflow Clarity | While individual patterns are well-demonstrated, there's no clear end-to-end workflow for setting up a test suite from scratch. The debugging section lists commands but lacks a structured troubleshooting flow with validation checkpoints. Steps are presented as isolated patterns rather than a sequenced process. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. The Playwright patterns, Cypress patterns, advanced patterns, best practices, pitfalls, and debugging could all be split into separate referenced documents. Everything is inline in one massive file with no navigation strategy. | 1 / 3 |
Total | 7 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (536 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
27a7ed9
- 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.