jbvc/e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.
44
56%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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 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 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, sets up test artifact collection, and provides strategies for diagnosing and fixing flaky tests.'
Add 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 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 test files', 'configures test runners'). | 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, which per the rubric should cap completeness at 2, and since the 'what' is also weak (topics rather than actions), 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 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.
The skill excels at actionability with high-quality, executable Playwright code examples covering a wide range of patterns. However, it suffers from being a monolithic document that tries to cover too many topics inline without progressive disclosure or clear navigation. The lack of an overarching workflow sequence and the inclusion of domain-specific sections (Web3, financial flows) that could be separate files reduce its effectiveness as a quick-reference skill.
Suggestions
Restructure as a concise overview (~50-80 lines) with links to separate files for each major topic: POM patterns, configuration, flaky test strategies, CI/CD integration, and domain-specific testing (Web3/financial).
Add an explicit workflow sequence at the top showing the recommended order for setting up an E2E test suite (config → fixtures → POMs → tests → local validation → CI integration).
Remove the test report template section — Claude can generate report templates on demand without needing this in the skill.
Trim explanatory comments in code examples that state the obvious (e.g., '// Mock wallet provider', '// Skip on production — real money') to improve token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but it's quite long (~250 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 Web3/wallet testing section is domain-specific and could be a separate file). Some patterns like the basic POM explanation are things Claude already knows well. | 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, proper types, and realistic patterns (POM classes, config files, CI workflows, flaky test fixes with bad/good comparisons). | 3 / 3 |
Workflow Clarity | Individual patterns are clear, but there's no overarching workflow sequence tying the pieces together (e.g., 'set up config → write POMs → write tests → run locally → validate → integrate CI'). The flaky test section has good diagnostic steps but lacks explicit validation checkpoints. For a skill involving test suite setup and CI integration, a clearer end-to-end workflow with verification steps would be expected. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files and no layered structure. At ~250 lines covering config, POM, test structure, flaky tests, artifacts, CI/CD, Web3 testing, and financial flow testing, much of this content should be split into separate reference files with the SKILL.md serving as a concise overview with navigation links. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
100%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.
Reviewed
Table of Contents