Name: e2e-testing
Rating: 59.2 (1 reviews)
Author: affaan-m

e2e-testing

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

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/e2e-testing/SKILL.md

The canonical home for this skill is e2e-testing in affaan-m/ECC

Quality

Content

72%Weight 40%Scale 1-5

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

The content is highly actionable and mostly lean, dominated by executable examples that cover common Playwright E2E cases. Its weaknesses are the lack of an explicit multi-step workflow with validation checkpoints and the absence of progressive disclosure into separate reference files.

Suggestions

Add an explicit flaky-test debugging loop with a validation checkpoint, e.g. 'After applying a fix, re-run with `--repeat-each=10` to confirm stability before unquarantining.'

Move the larger reference blocks (CI/CD workflow, test report template, wallet/web3 and financial-flow examples) into separate files under references/ and link to them from SKILL.md to improve progressive disclosure.

Trim the marketing opener and any redundant section intros so every remaining token earns its place, pushing conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is overwhelmingly executable code with terse labels and assumes Claude's Playwright competence, but the marketing opener 'Comprehensive Playwright patterns for building stable, fast, and maintainable E2E test suites.' and a few exhaustive sections could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready TypeScript, YAML, and bash covering the common cases — a complete POM class, test structure, playwright.config.ts, CI workflow, wallet mock, and trade-execution test — with no real gaps.	5 / 5
Workflow Clarity	The body is a pattern catalog rather than a sequenced workflow; the flaky-test section has an implicit quarantine → identify → diagnose/fix flow, but there are no explicit validation checkpoints or feedback loops (e.g. re-run to confirm a fix).	3 / 5
Progressive Disclosure	Section headers give good in-file structure, but with no bundle files the entire ~320-line reference (CI/CD YAML, test report template, wallet/web3, financial flows) is inlined in SKILL.md rather than split into one-level-deep reference files.	3 / 5
	Total	15 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 is specific and uses natural trigger terms within a distinct Playwright E2E niche, but it omits any explicit 'when to use' guidance, which caps completeness. Adding a 'Use when...' clause with synonyms would lift the weaker dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when writing or debugging Playwright E2E tests, setting up Page Object Model, configuring CI/CD test pipelines, or fixing flaky tests.'

Add natural synonyms users might say — 'end-to-end tests', 'browser tests', 'test automation', '.spec.ts' — to broaden trigger term coverage.

Reframe the area list slightly toward concrete actions (e.g. 'structure tests with the Page Object Model', 'configure retries and reporters', 'diagnose and quarantine flaky tests') to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	The description enumerates several concrete capability areas — 'Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies' — naming the domain plus multiple specific sub-topics, though they are areas rather than crisp actions, leaving minor coverage gaps.	4 / 5
Completeness	It gives a clear 'what' but contains no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	It includes natural terms users actually say ('Playwright', 'E2E testing', 'Page Object Model', 'CI/CD', 'flaky tests'), giving good keyword coverage, but misses common synonyms like 'end-to-end tests', 'browser tests', or 'test automation'.	4 / 5
Distinctiveness Conflict Risk	'Playwright E2E testing' is a clear, fairly distinct niche with minimal conflict risk, though the absence of explicit trigger phrases and possible overlap with a broader testing skill keeps it just below a 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/e2e-testing/SKILL.md
Commit: d8409a4

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.