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 does and entirely omits 'when to use' guidance, which are critical for Claude to select the right skill from a large pool.

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 browser test automation, or configuring Playwright for CI/CD pipelines.'

Replace topic nouns with concrete action phrases, e.g., 'Generates Playwright E2E test files using Page Object Model patterns, configures playwright.config.ts, manages test artifacts like screenshots and traces, and provides strategies for fixing flaky tests.'

Include common user-facing trigger term variations such as 'end-to-end tests', 'browser testing', 'test automation', '.spec.ts', 'playwright.config', and 'test retries'.

Dimension	Reasoning	Score
Specificity	Names the domain (Playwright E2E testing) and lists several topic areas (Page Object Model, configuration, CI/CD integration, artifact management, flaky test strategies), but these are more like categories than concrete actions. No verbs describing what the skill actually does (e.g., 'generates tests', 'configures pipelines').	2 / 3
Completeness	Describes the 'what' at a topic level but completely lacks any 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance, and per the rubric, a missing 'Use when...' clause should cap completeness at 2, but the 'what' itself is also weak (topics rather than actions), warranting 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 mention. However, it misses common variations like 'end-to-end tests', 'browser testing', 'test automation', '.spec.ts', or 'playwright.config'.	2 / 3
Distinctiveness Conflict Risk	Mentioning 'Playwright' specifically helps distinguish it from generic testing skills, but terms like 'E2E testing', 'CI/CD integration', and 'configuration' are broad enough to overlap with other testing framework skills (e.g., Cypress, Selenium) or CI/CD-focused 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 strong code examples covering POM, configuration, flaky tests, CI/CD, and specialized domains. However, it suffers from being a monolithic reference document that could benefit significantly from splitting into focused files with a concise overview. The lack of an overarching workflow and the inclusion of domain-specific sections (Web3, financial) inline reduces its efficiency as a skill file.

Suggestions

Split domain-specific sections (Wallet/Web3, Financial Flow Testing) and reference materials (CI/CD, Artifact Management) into separate files, keeping SKILL.md as a concise overview with links.

Add an explicit workflow section at the top: 'When writing a new E2E test: 1. Create spec file in appropriate directory, 2. Create/reuse Page Object, 3. Write test with proper waits, 4. Run locally with --repeat-each=5 to verify stability, 5. Add to CI pipeline.'

Remove the Test Report Template section — it's a static template that doesn't teach Claude a pattern and could be a separate file if needed.

Trim explanatory comments in code examples (e.g., '// Bad: assumes element is ready' is useful, but some comments restate what the code already shows).

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 patterns like the test report template add bulk without strong value.	2 / 3
Actionability	Excellent actionability throughout — every section provides fully executable, copy-paste-ready TypeScript code, bash commands, and YAML configs. The flaky test patterns include concrete bad/good comparisons with real code. The CI/CD workflow is a complete GitHub Actions file.	3 / 3
Workflow Clarity	Individual sections are clear, but there's no overarching workflow tying the pieces together (e.g., 'when writing a new E2E test, follow these steps...'). The flaky test section has good diagnostic steps but lacks an explicit validation/feedback loop. The content reads more like a reference catalog than a guided workflow.	2 / 3
Progressive Disclosure	This is a monolithic wall of content with no references to supporting files and no bundle files provided. The Wallet/Web3 testing, financial flow testing, artifact management, and CI/CD sections could all be split into separate referenced files. Everything is inline with no navigation structure beyond flat headings.	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: 841beea

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