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), includes an explicit 'Use when' clause, and uses natural trigger terms users would employ. The main weakness is that the capability description leans slightly toward aspirational language ('catch bugs, improve confidence, enable fast deployment') rather than listing more concrete specific actions the skill enables.
Suggestions
Replace aspirational outcomes ('catch bugs, improve confidence, enable fast deployment') with more concrete actions like 'write page object models, configure test retries, set up CI integration, handle test fixtures'.
| 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 listing multiple concrete specific actions like 'write page object models, configure test retries, set up parallel execution'. | 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 keywords 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 in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of specific frameworks (Playwright, Cypress) and the E2E testing focus creates a clear niche. Terms like 'flaky tests', 'E2E tests', and the named tools make it unlikely to conflict with unit testing, API testing, or other skill types. | 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 provides excellent, executable code examples across both Playwright and Cypress, making it highly actionable. However, it is severely bloated — explaining basic testing concepts Claude already knows, duplicating guidance across frameworks, and cramming everything into a single monolithic file. The lack of progressive disclosure and the verbose conceptual sections significantly reduce its effectiveness as a skill file.
Suggestions
Remove the 'Core Concepts' section entirely (testing pyramid, what to test/not test) — Claude already knows these fundamentals. This saves ~40 lines of unnecessary context.
Split into separate files: SKILL.md as overview with quick-start examples, then PLAYWRIGHT.md and CYPRESS.md for framework-specific patterns, and ADVANCED.md for visual regression/sharding/accessibility.
Add a clear workflow sequence for setting up E2E testing from scratch: install → configure → write first test → run and validate → add to CI, with explicit validation checkpoints at each step.
Consolidate the 'Best Practices' and 'Common Pitfalls' sections — they repeat the same advice (selectors, flaky tests, independence) and could be a single concise checklist.
| 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 sequenced workflow for setting up a test suite end-to-end. The debugging section lists commands but lacks a structured troubleshooting flow with validation checkpoints. For a skill covering test suite establishment, there's no verification step to confirm tests are properly configured before running. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. The Playwright patterns, Cypress patterns, advanced patterns, and best practices could easily be split into separate referenced documents. Everything is inline in one massive file with no navigation aids or cross-references. | 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
70444e5
- 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.