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.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill e2e-testing-patterns79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
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 with excellent completeness and distinctiveness. It includes an explicit 'Use when' clause with relevant trigger scenarios and names specific frameworks. The main weakness is the somewhat vague capability description - it uses aspirational language ('Master', 'improve confidence') rather than listing concrete actions the skill enables.
Suggestions
Replace vague phrases like 'Master end-to-end testing' with specific actions such as 'Write page object models, configure test runners, handle async waits, and set up CI pipelines'
Add more concrete debugging capabilities like 'analyze test failures', 'fix race conditions', or 'implement retry strategies'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (E2E testing with Playwright/Cypress) and mentions some actions ('build reliable test suites', 'catch bugs'), but lacks concrete specific actions like 'write page object models', 'configure test runners', or 'set up CI integration'. | 2 / 3 |
Completeness | Clearly answers both what ('Master end-to-end testing with Playwright and Cypress to build reliable test suites') and when ('Use when implementing E2E tests, debugging flaky tests, or establishing testing standards') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms: 'E2E tests', 'Playwright', 'Cypress', 'flaky tests', 'testing standards'. These are terms users would naturally use when seeking help with end-to-end testing. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on E2E testing with named frameworks (Playwright, Cypress). Distinct triggers like 'flaky tests' and specific tool names make it unlikely to conflict with general testing or unit testing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive E2E testing guide with excellent, executable code examples for both Playwright and Cypress. However, it's overly long for a skill file, includes conceptual explanations Claude doesn't need (testing pyramid, what E2E is for), and lacks explicit validation workflows for test debugging. The content would benefit from being split into overview + detailed reference files.
Suggestions
Remove or significantly condense the 'Core Concepts' section - Claude understands testing fundamentals and the testing pyramid
Add an explicit debugging workflow with validation checkpoints: 1. Run in headed mode → 2. Check for timing issues → 3. Verify selectors → 4. Add trace/screenshot → 5. Isolate the failure
Split into SKILL.md (overview + quick patterns) and separate reference files for Playwright-specific and Cypress-specific detailed patterns
Remove the 'When to Use This Skill' section as it largely restates the skill description
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations Claude already knows (testing pyramid concept, what E2E testing is for) and could be tightened. The 'Core Concepts' section explaining what to test vs not test is somewhat verbose for an AI that understands testing fundamentals. | 2 / 3 |
Actionability | Excellent executable code examples throughout - complete Playwright config, Page Object Model implementation, fixtures, custom Cypress commands, and network mocking patterns are all copy-paste ready with proper TypeScript typing. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit workflow for setting up a test suite from scratch or debugging process with validation checkpoints. The debugging section lists tools but lacks a systematic troubleshooting workflow with feedback loops. | 2 / 3 |
Progressive Disclosure | References to external files (references/playwright-best-practices.md, scripts/test-analyzer.ts) are listed at the end, but the main content is a monolithic document with 400+ lines. Advanced patterns could be split into separate files with the main skill providing an overview. | 2 / 3 |
Total | 9 / 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 | |
- 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.