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/Cypress), includes an explicit 'Use when' clause with relevant triggers, and is distinctive enough to avoid conflicts. The 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 enables.
Suggestions
Replace aspirational phrases like 'catch bugs, improve confidence, and enable fast deployment' with more concrete actions such as '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 far too verbose—explaining basic testing concepts Claude already knows, covering two frameworks exhaustively in one file, and lacking any progressive disclosure structure. The content would benefit greatly from being trimmed to essential patterns and split into referenced sub-files.
Suggestions
Remove the 'Core Concepts' section entirely (testing pyramid, what to test vs not) as Claude already knows these fundamentals, and trim the 'When to Use This Skill' list.
Split Playwright and Cypress patterns into separate referenced files (e.g., PLAYWRIGHT.md and CYPRESS.md) with SKILL.md serving as a concise overview pointing to each.
Add an explicit workflow with validation steps for setting up E2E testing from scratch (e.g., 1. Configure → 2. Write first test → 3. Run and verify → 4. Add to CI → 5. Validate CI results).
Consolidate the 'Best Practices' and 'Common Pitfalls' sections into a single compact checklist, removing redundant advice that appears in both.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines. It explains concepts Claude already knows well (testing pyramid, what E2E testing is, what to test vs not test). The 'When to Use This Skill' and 'Core Concepts' sections are largely unnecessary padding. Many patterns are exhaustively shown for both Playwright and Cypress when one focused framework would suffice. | 1 / 3 |
Actionability | The code examples are concrete, executable, and copy-paste ready. Configuration files, page objects, fixtures, custom commands, and debugging commands are all fully specified with real TypeScript code that could be directly used in a project. | 3 / 3 |
Workflow Clarity | Individual patterns are clearly presented, but there's no overarching workflow for setting up a test suite from scratch. The debugging section provides a sequence of escalating steps, but there are no validation checkpoints or feedback loops for the overall process of writing and maintaining E2E tests (e.g., run tests → check results → fix flaky tests → re-run). | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files and no bundle files. The content covers Playwright config, page objects, fixtures, waiting strategies, network mocking, Cypress config, custom commands, intercepts, visual regression, sharding, accessibility, best practices, pitfalls, and debugging all in one file. Much of this should be split into separate reference files. | 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
112197c
- 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.