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.
78
70%
Does it follow best practices?
Impact
93%
1.27xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/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, 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 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
50%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 covering both Playwright and Cypress comprehensively, but is far too verbose for a SKILL.md — it reads more like a tutorial or documentation page than a concise skill reference. Significant portions explain concepts Claude already knows (testing pyramid, what E2E tests are for, generic best practices), and the content would benefit greatly from being split across the referenced files rather than inlined.
Suggestions
Cut the 'Core Concepts', 'Test Philosophy', 'Best Practices', and 'Common Pitfalls' sections entirely or reduce to 2-3 lines of project-specific conventions — Claude already knows standard E2E testing principles.
Move the detailed Playwright and Cypress pattern code into the referenced files (references/playwright-best-practices.md, references/cypress-best-practices.md) and keep only a quick-start example and pattern index in SKILL.md.
Add a clear sequential workflow for setting up E2E testing from scratch (e.g., 1. Install → 2. Configure → 3. Write first test → 4. Validate it runs → 5. Add to CI) with explicit validation checkpoints.
Remove the duplicate coverage between Playwright and Cypress sections (e.g., network mocking is shown for both) — pick one as primary or consolidate the patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Includes unnecessary sections like the testing pyramid ASCII art, explanations of what to test vs not test (Claude knows this), 'Core Concepts' and 'Test Philosophy' sections that explain basic testing knowledge, and extensive best practices/pitfalls lists that restate common knowledge. The Cypress section largely duplicates patterns already shown in Playwright. | 1 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout — complete Playwright config, Page Object Model implementation, fixtures, waiting strategies, network mocking, Cypress commands, visual regression testing, accessibility testing, and debugging commands. All examples are concrete TypeScript with realistic scenarios. | 3 / 3 |
Workflow Clarity | Individual patterns are well-demonstrated but there's no clear sequenced workflow for setting up E2E testing from scratch or a validation/verification loop. The debugging section lists tools but doesn't provide a systematic debugging workflow. For a skill involving test suite setup and CI/CD pipelines, explicit step sequences with checkpoints would be expected. | 2 / 3 |
Progressive Disclosure | References external files at the bottom (references/, assets/, scripts/) which is good, but the main file is a monolithic wall of content that should have much of its detail pushed into those referenced files. The Playwright and Cypress pattern sections are extensive inline content that could be separate files, with SKILL.md serving as a concise overview. | 2 / 3 |
Total | 8 / 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 (545 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
6e3d68c
- 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.