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

Content

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 excellent, actionable Playwright code examples covering a wide range of E2E testing scenarios, which is its primary strength. However, it suffers from being a monolithic reference document that tries to cover too many topics in one file without clear workflows or progressive disclosure. It would benefit from being split into a concise overview with references to detailed sub-files, and from adding explicit step-by-step workflows with validation checkpoints.

Suggestions

Split the monolithic content into a concise SKILL.md overview with references to separate files (e.g., POM.md, FLAKY-TESTS.md, CI-CD.md, WEB3-TESTING.md) to improve progressive disclosure.

Add an explicit step-by-step workflow for common scenarios like 'setting up E2E tests for a new project' or 'diagnosing and fixing a flaky test' with validation checkpoints.

Remove the test report template section — Claude can generate markdown reports without a template — and trim the artifact management section which mostly restates basic Playwright API.

Add a brief 'when to use which pattern' decision guide at the top so Claude can quickly navigate to the relevant section rather than reading the entire document.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples, but it's quite long (~300 lines) and includes some sections that feel like padding (e.g., the test report template is a markdown template Claude could generate on its own, the wallet/Web3 testing section is domain-specific and could be a separate file). Some patterns like the artifact management section explain basic Playwright API that Claude already knows.	2 / 3
Actionability	All code examples are fully executable TypeScript/YAML with concrete, copy-paste-ready patterns. The POM example, config, CI workflow, and flaky test fixes all provide specific, working code rather than pseudocode or vague descriptions.	3 / 3
Workflow Clarity	The skill presents patterns and examples clearly but lacks explicit multi-step workflows with validation checkpoints. For example, there's no clear sequence for setting up a test suite from scratch, no feedback loop for when tests fail in CI, and the flaky test section lists fixes without a diagnostic workflow. The content reads more as a reference catalog than a guided process.	2 / 3
Progressive Disclosure	The entire skill is a monolithic wall of content with no references to supporting files, despite being long enough to warrant splitting. Sections like Web3 testing, financial flow testing, artifact management, and CI/CD could each be separate referenced files. There are no bundle files to support progressive disclosure, and the skill doesn't organize content into overview vs. detail layers.	1 / 3
	Total	8 / 12 Passed

Description

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 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 a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others.

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 in CI/CD pipelines.'

Replace topic nouns with concrete action phrases, e.g., 'Generates Playwright E2E tests using Page Object Model patterns, configures playwright.config.ts, sets up test artifact collection, and diagnoses flaky test failures.'

Include common user-facing trigger terms and file extensions like 'end-to-end tests', 'browser testing', 'test automation', '.spec.ts', 'playwright.config.ts' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Playwright E2E testing) and lists several areas (Page Object Model, configuration, CI/CD integration, artifact management, flaky test strategies), but these are topic areas rather than concrete actions. No verbs describing what the skill actually does (e.g., 'generates test files', 'configures test runners').	2 / 3
Completeness	Describes topic areas (what) at a high level but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and the 'what' 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 'E2E testing patterns', 'CI/CD integration', and 'flaky test strategies' could overlap with other testing framework skills (e.g., Cypress, Selenium). The lack of explicit triggers increases conflict risk.	2 / 3
	Total	7 / 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: ec92b52

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.