e2e-testing

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

Quality

45%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

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 domain (Playwright E2E testing) and lists relevant topic areas, but it reads more like a table of contents than an actionable skill description. It lacks concrete action verbs describing what the skill enables Claude to do, and critically omits any 'Use when...' guidance for skill selection. Adding explicit trigger conditions and converting topic areas into concrete capabilities would significantly improve it.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about writing Playwright tests, debugging flaky E2E tests, setting up Playwright configuration, or integrating browser tests into CI/CD pipelines.'

Convert topic areas into concrete actions with verbs, e.g., 'Generates Playwright E2E tests using Page Object Model patterns, configures Playwright for CI/CD pipelines, diagnoses and fixes flaky tests, and manages test artifacts.'

Include additional natural trigger terms users might say, such as 'end-to-end tests', 'browser testing', 'test automation', 'playwright.config.ts', or 'test failures'.

Dimension	Reasoning	Score
Specificity	Names the domain (Playwright E2E testing) and lists several areas like Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. However, these are topic areas rather than concrete actions (no verbs like 'create', 'configure', 'debug').	2 / 3
Completeness	Describes what the skill covers (Playwright testing patterns and related topics) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also somewhat weak (topic listing rather than clear capabilities), this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Playwright', 'E2E testing', 'Page Object Model', 'CI/CD', and 'flaky test' that users might naturally use. However, it misses common variations like 'end-to-end tests', 'browser testing', 'test automation', 'Playwright config', or file extensions like 'playwright.config.ts'.	2 / 3
Distinctiveness Conflict Risk	Mentioning 'Playwright' specifically helps distinguish it from generic testing skills, but terms like 'E2E testing', 'CI/CD integration', and 'flaky test strategies' could overlap with other testing framework skills (e.g., Cypress, Selenium) or general CI/CD skills.	2 / 3
	Total	7 / 12 Passed

Implementation

57%

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

This skill provides highly actionable, executable Playwright patterns with excellent code examples covering POM, configuration, flaky tests, CI/CD, and specialized testing scenarios. However, it's a monolithic document that would benefit significantly from being split into focused sub-files with a concise overview as the main SKILL.md. Some content (basic POM explanation, test report template, domain-specific Web3/financial testing) adds length without proportional value for the general use case.

Suggestions

Split into multiple files: keep SKILL.md as a concise overview with quick-start patterns, and move detailed sections (POM, config, flaky tests, CI/CD, Web3) into referenced sub-files like POM.md, CONFIG.md, FLAKY-TESTS.md, CI-CD.md.

Add an explicit workflow sequence at the top: e.g., '1. Configure playwright.config.ts → 2. Create page objects → 3. Write tests → 4. Run locally and verify → 5. Set up CI/CD' with validation checkpoints between steps.

Remove or trim the test report template section — it's a static template that doesn't teach Playwright patterns and could be a separate reference file.

Trim explanatory framing (e.g., section headers like 'Common Causes & Fixes' can stand alone without the 'Flaky Test Patterns' parent heading) and remove the Web3/Financial sections unless they're core to the skill's purpose.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples, but it's quite long (~250 lines) and includes sections Claude likely doesn't need explained (basic POM pattern, what screenshots/traces are). The Wallet/Web3 and Financial Flow sections feel domain-specific and could be separate files. Some sections like the test report template add bulk without strong instructional value.	2 / 3
Actionability	Excellent actionability throughout — every section provides fully executable, copy-paste-ready TypeScript code, bash commands, and YAML configurations. The code examples are complete with imports, realistic patterns, and concrete data-testid selectors. The bad/good comparisons for flaky tests are particularly actionable.	3 / 3
Workflow Clarity	The skill presents individual patterns clearly but lacks an explicit end-to-end workflow sequence for setting up and running a test suite. There are no validation checkpoints (e.g., 'verify config works before writing tests') or feedback loops for the overall process. The flaky test section has good diagnostic steps but no structured remediation workflow.	2 / 3
Progressive Disclosure	All content is in a single monolithic file with no references to supporting files, despite the skill being comprehensive enough to warrant splitting (POM patterns, config, CI/CD, flaky test strategies, Web3 testing could each be separate). The file organization diagram at the top suggests a multi-file structure but the skill itself doesn't follow progressive disclosure principles.	1 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: affaan-m/everything-claude-code
Commit: 928076c

Reviewed: 3 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.