e2e-testing

Playwright E2E 测试模式、页面对象模型（POM）、配置、CI/CD 集成、产物管理以及不稳定测试（flaky test）策略。

Quality

81%

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

Quality

Content

80%Weight 40%Scale 1-3

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

The content is concise and highly actionable with executable examples throughout, but it is monolithic with no progressive disclosure to separate files, and its flaky-test workflow lacks explicit validation checkpoints.

Suggestions

Add an explicit validation checkpoint to the flaky-test workflow, e.g. 'Re-run with --repeat-each=20; only remove test.fixme once it passes 20/20.'

Split large subtopics (e.g. CI/CD integration, Web3/financial testing) into separate reference files in ./references/ and link to them from SKILL.md for progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-driven with minimal prose, assumes Claude already knows what Playwright/POM are, and avoids explaining concepts Claude knows — every section earns its place with executable code.	3 / 3
Actionability	It provides fully executable, copy-paste-ready TypeScript and YAML for POM classes, test structure, playwright.config, CI workflow, wallet mocks, and trade tests, matching the anchor for executable code and specific examples.	3 / 3
Workflow Clarity	The flaky-test section has a loose sequence (quarantine → identify via --repeat-each/--retries → diagnose causes → fix), but there are no explicit validation checkpoints such as verifying a test passes N times before un-quarantining.	2 / 3
Progressive Disclosure	No bundle files exist and the entire skill is a single ~320-line monolithic SKILL.md with clearly headed sections, but substantial subtopics (POM, CI/CD, Web3 wallet testing) that could be split into separate reference files are all inlined.	2 / 3
	Total	10 / 12 Passed

Description

82%Weight 40%Scale 1-3

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 distinctive with good natural trigger terms, but it omits any explicit 'Use when...' guidance, which caps its completeness. Adding a trigger clause would raise the strongest remaining weakness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when writing or debugging Playwright end-to-end tests, setting up page objects, or fixing flaky E2E tests.'

Consider adding natural variation terms users say (e.g. 'E2E tests', 'integration tests', 'Playwright config') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	It enumerates multiple concrete, specific capabilities — "页面对象模型（POM）、配置、CI/CD 集成、产物管理以及不稳定测试（flaky test）策略" — rather than vague language, matching the anchor that lists multiple specific concrete actions.	3 / 3
Completeness	It clearly states what the skill covers, but there is no "Use when..." clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	It includes natural terms users would actually say — "Playwright E2E 测试", "POM", "CI/CD", "flaky test" — giving good coverage of common phrasings a user would use when requesting this skill.	3 / 3
Distinctiveness Conflict Risk	The "Playwright E2E 测试" niche is specific and unlikely to overlap with unrelated skills, matching the anchor for a clear niche with distinct triggers.	3 / 3
	Total	11 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: xu-xiang/everything-claude-code-zh
Path: .agents/skills/e2e-testing/SKILL.md
Commit: dfbf946

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