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

70%

Does it follow best practices?

Impact

93%

1.27x

Average score across 3 eval scenarios

Securityby

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.md

Quality

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 good trigger scenarios, and is distinctive enough to avoid conflicts. 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 authentication flows'.

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, actionable code examples covering both Playwright and Cypress with real-world patterns, but is severely bloated with explanatory content Claude doesn't need (testing philosophy, what to test, best practices lists). The content would benefit greatly from being split into focused reference files with a lean overview, and from removing sections that explain well-known testing concepts.

Suggestions

Remove 'Core Concepts', 'Test Philosophy', 'Best Practices' list, and 'Common Pitfalls' sections — these explain testing fundamentals Claude already knows. Keep only the concrete code patterns.

Split Playwright patterns, Cypress patterns, and Advanced patterns into separate referenced files (e.g., references/playwright-patterns.md) and keep SKILL.md as a concise overview with quick-start examples.

Add an explicit workflow section with validation steps for setting up E2E testing from scratch (e.g., 'configure → write first test → verify it passes → add to CI → verify CI passes → expand coverage').

Trim the 'When to Use This Skill' list to 2-3 primary use cases instead of 8 items.

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 lists that restate common knowledge. The 'When to Use This Skill' list is padded with obvious items.	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 patterns.	3 / 3
Workflow Clarity	Individual patterns are clearly presented but there's no overarching workflow for setting up an E2E test suite from scratch. The debugging section provides a sequence of escalating steps which is good, but there are no explicit validation checkpoints (e.g., 'verify tests pass before adding more', 'run in CI before merging'). For a skill involving test infrastructure setup, a clearer end-to-end workflow with verification steps would be expected.	2 / 3
Progressive Disclosure	References to external files are listed at the bottom (references/, assets/, scripts/) which is good, but the main file is monolithic with extensive inline content that could be split — Playwright patterns, Cypress patterns, and Advanced patterns could each be separate referenced files. The skill tries to cover too much in one file.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 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: 47823e3

Reviewed: 1 day 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.