e2e-testing

Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

Install with Tessl CLI

npx tessl i github:affaan-m/everything-claude-code --skill e2e-testing

What are skills?

1.58x

Quality

56%

Does it follow best practices?

Impact

92%

1.58x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/e2e-testing/SKILL.md

SKILL.md

Review

Evals

Discovery

32%

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

The description identifies the technology domain (Playwright) and lists relevant topic areas, but reads more like a table of contents than an actionable skill description. It lacks concrete actions (verbs describing what the skill does) and completely omits trigger guidance for when Claude should use it. The technical terms provide some distinctiveness but the absence of a 'Use when...' clause significantly limits its effectiveness for skill selection.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Playwright tests, browser automation, end-to-end testing with Playwright, or debugging flaky tests.'

Convert topic areas into concrete actions: 'Write Playwright E2E tests using Page Object Model, configure test runners, integrate with CI/CD pipelines, and diagnose flaky test failures.'

Include common user phrasings like 'browser tests', 'end-to-end tests', 'test automation', and 'Playwright config' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Playwright E2E testing) and lists several concepts (Page Object Model, configuration, CI/CD integration, artifact management, flaky test strategies), but these are topic areas rather than concrete actions like 'write tests', 'debug failures', or 'generate page objects'.	2 / 3
Completeness	Describes what topics the skill covers but completely lacks a 'Use when...' clause or any explicit trigger guidance. There is no indication of when Claude should select this skill over others.	1 / 3
Trigger Term Quality	Includes relevant technical terms like 'Playwright', 'E2E testing', 'Page Object Model', 'CI/CD' that users might mention, but misses common variations like 'end-to-end tests', 'browser testing', 'test automation', or 'flaky tests' as a standalone phrase.	2 / 3
Distinctiveness Conflict Risk	'Playwright' is a distinct technology that helps differentiate this skill, but 'E2E testing', 'CI/CD integration', and 'flaky test strategies' could overlap with other testing frameworks or general testing skills.	2 / 3
	Total	7 / 12 Passed

Implementation

79%

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

This is a strong, actionable skill with excellent code examples covering Playwright E2E testing comprehensively. The content is concise and assumes Claude's competence. However, it would benefit from explicit validation workflows (especially for CI/CD and critical flow testing) and better progressive disclosure by splitting into focused sub-documents.

Suggestions

Add explicit validation checkpoints to the CI/CD section, such as 'verify playwright installed correctly' and 'if tests fail in CI but pass locally, check X'

Split detailed topics (Wallet/Web3 Testing, Financial Flow Testing, Flaky Test Patterns) into separate referenced files to improve progressive disclosure

Add a troubleshooting workflow: 'If tests fail -> check trace -> review screenshot -> examine network logs -> fix and re-run'

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, presenting code examples directly without explaining what Playwright is or how testing frameworks work. Every section delivers actionable patterns without unnecessary preamble.	3 / 3
Actionability	All code examples are fully executable TypeScript/YAML with complete imports, proper syntax, and copy-paste ready patterns. The configuration, test structures, and CI/CD workflow are all concrete and immediately usable.	3 / 3
Workflow Clarity	While individual patterns are clear, the skill lacks explicit validation checkpoints and feedback loops. For example, there's no guidance on verifying test setup worked, no 'if tests fail, check X' troubleshooting flow, and the CI/CD section doesn't include validation steps before deployment.	2 / 3
Progressive Disclosure	The content is well-organized with clear sections, but it's a monolithic document (~250 lines) that could benefit from splitting detailed topics (wallet testing, CI/CD, flaky test strategies) into separate referenced files. No external file references are provided.	2 / 3
	Total	10 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Reviewed: about 20 hours 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.