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.

1.27x

Quality

62%

Does it follow best practices?

Impact

93%

1.27x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/e2e-testing-patterns/SKILL.md

The canonical home for this skill is e2e-testing-patterns in wshobson/agents

Quality

Content

46%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is rich with concrete, usable code examples for both Playwright and Cypress, which is its core strength. However, it is padded with generic testing concepts Claude already knows, lacks any sequenced workflow (notably for its stated flaky-test debugging use case), and its reference structure is broken — every referenced bundle file is missing while the content that should live in those files is inlined.

Suggestions

Remove the Core Concepts testing-pyramid material and merge the overlapping Best Practices and Common Pitfalls sections into one tight list, cutting the body to unique value only.

Add a step-by-step flaky-test debugging workflow (reproduce with retries → inspect trace/screenshot → isolate the race → fix the wait → verify with repeated runs) since debugging flaky tests is an explicit trigger in the description.

Create the referenced files (references/playwright-best-practices.md, references/cypress-best-practices.md, references/flaky-test-debugging.md, assets/e2e-testing-checklist.md, assets/selector-strategies.md, scripts/test-analyzer.ts) and move the inlined tool-specific patterns into them, leaving SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	Several sections restate generic knowledge Claude already has — the testing pyramid, 'What to Test with E2E', and a Best Practices list that is repeated nearly verbatim in Common Pitfalls — and 'When to Use This Skill' duplicates the frontmatter description, matching the 'noticeably verbose, several padded sections' anchor.	2 / 5
Actionability	Mostly executable, copy-paste-ready TypeScript covering config, page objects, fixtures, waiting strategies, network mocking, and accessibility scans, but fixtures reference undefined helpers (createTestUser/deleteTestUser, UserData/User types), keeping it below fully-executable anchor 5.	4 / 5
Workflow Clarity	The content is a topical pattern library with no sequenced process; even the flaky-test debugging use case from the description gets a loose numbered command list rather than a reproduce → trace → isolate → verify workflow with checkpoints, fitting the 'sequence present but checkpoints missing' anchor.	3 / 5
Progressive Disclosure	The Resources section clearly signals six bundle files, but none of them (references/, scripts/, assets/) exist in the bundle, and roughly 200 lines of Playwright/Cypress patterns are inlined that belong in those reference files — matching the anchor for content inlined that should be separate.	2 / 5
	Total	11 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill does and when to use it, with recognizable trigger terms and a distinct E2E-testing niche. Its main weaknesses are outcome-fluff in the capability list and slightly thin coverage of common trigger synonyms.

Suggestions

Replace outcome-oriented filler ('catch bugs, improve confidence, and enable fast deployment') with concrete capabilities such as 'write Page Object models, mock network responses, and run cross-browser suites'.

Add natural trigger synonyms like 'browser tests', 'UI tests', or 'test automation' to broaden keyword coverage.

Sharpen the trigger boundary, e.g. 'Use for browser-level E2E tests — not unit or integration tests'.

Dimension	Reasoning	Score
Specificity	Names the domain and tools ('Master end-to-end testing with Playwright and Cypress') with a couple of concrete actions ('build reliable test suites', 'debug flaky tests'), but 'catch bugs, improve confidence, and enable fast deployment' is outcome-oriented fluff rather than distinct concrete actions, so it does not reach anchor 4.	3 / 5
Completeness	It explicitly 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 concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	'E2E tests', 'flaky tests', 'Playwright', 'Cypress', and 'testing standards' are natural phrases users would say, giving good keyword coverage; common variations like 'browser tests', 'UI tests', or 'test automation' are missing, keeping it below anchor 5.	4 / 5
Distinctiveness Conflict Risk	The E2E/Playwright/Cypress/flaky-test niche is mostly distinct with tool-specific triggers, but 'establishing testing standards' is broad enough to overlap with generic testing or unit-testing standards skills, so it is not minimal-conflict anchor 5.	4 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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
referenced_paths_exist	Referenced path issues: 6 missing	Warning

	Total	14 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/developer-essentials/skills/e2e-testing-patterns/SKILL.md
Commit: a65ce00

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.