jbvc/e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
65
65%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its domain (E2E testing with Playwright and Cypress), includes an explicit 'Use when' clause with relevant triggers, and is distinctive enough to avoid conflicts. The main weakness is that the capability descriptions lean slightly toward aspirational language ('catch bugs, improve confidence, enable fast deployment') rather than listing more concrete specific actions the skill enables.
Suggestions
Replace aspirational phrases like 'catch bugs, improve confidence, and enable fast deployment' with more concrete actions such as 'write page object models, configure test retries, set up CI integration, handle test selectors'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (end-to-end testing) and tools (Playwright, Cypress), and mentions some actions like 'build reliable test suites', 'debugging flaky tests', 'establishing testing standards', but these are somewhat high-level rather than listing multiple concrete specific actions like 'write page object models, configure test retries, set up parallel execution'. | 2 / 3 |
Completeness | Clearly answers both 'what' (build reliable test suites with Playwright and Cypress) and 'when' with an explicit 'Use when' clause covering implementing E2E tests, debugging flaky tests, and establishing testing standards. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Playwright', 'Cypress', 'E2E tests', 'flaky tests', 'testing standards', 'end-to-end testing'. These cover common variations of how users would describe their needs in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of specific frameworks (Playwright, Cypress) and the E2E testing focus creates a clear niche. Terms like 'flaky tests', 'E2E tests', and the named tools make it unlikely to conflict with unit testing, API testing, or other skill types. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a table of contents with no substance. It promises E2E testing guidance for Playwright and Cypress but provides zero concrete code, commands, selectors, or examples. The instructions read like a project plan outline rather than actionable guidance, and the entire value is deferred to a single external resource file without any meaningful overview content.
Suggestions
Add concrete, executable code examples for at least one framework (e.g., a Playwright test with proper selectors, setup, and assertions) directly in the SKILL.md.
Replace the vague 4-step instructions with specific, actionable steps including commands (e.g., `npx playwright test --trace on`) and validation checkpoints (e.g., 'verify test passes locally before pushing to CI').
Include at least one complete example of a critical user journey test (e.g., login flow) with stable selector strategies demonstrated in code.
Describe what's in the implementation-playbook.md resource so Claude knows when and why to consult it, and consider adding a quick-start section that doesn't require navigating to another file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary sections like the 'Use this skill when' and 'Do not use this skill when' lists that are somewhat obvious and don't add much actionable value. The actual instructions are very thin. | 2 / 3 |
Actionability | The instructions are entirely abstract and vague — 'Identify critical user journeys,' 'Build stable selectors,' 'Implement tests with retries' — with zero concrete code, commands, examples, or specific guidance. Despite the description mentioning Playwright and Cypress, neither tool is referenced in the content with any executable detail. | 1 / 3 |
Workflow Clarity | The four numbered steps are high-level platitudes without any specifics, validation checkpoints, or error recovery guidance. There is no concrete sequence that Claude could follow to actually accomplish anything. | 1 / 3 |
Progressive Disclosure | There is a reference to `resources/implementation-playbook.md` for detailed patterns, which is good progressive disclosure structure. However, the SKILL.md itself provides almost no useful overview content — it's too thin to serve as a meaningful entry point, and there's only one reference with no description of what's inside. | 2 / 3 |
Total | 6 / 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