generating-end-to-end-tests
This skill enables Claude to generate end-to-end (E2E) tests for web applications. It leverages Playwright, Cypress, or Selenium to automate browser interactions and validate user workflows. Use this skill when the user requests to "create E2E tests", "generate end-to-end tests", or asks for help with "browser-based testing". The skill is particularly useful for testing user registration, login flows, shopping cart functionality, and other multi-step processes within a web application. It supports cross-browser testing and can be used to verify the responsiveness of web applications on different devices.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-end-to-end-tests90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 97%
↑ 1.01xAgent success when using this skill
Validation for skill structure
Discovery
100%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 well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms users would actually say, explicitly states when to use the skill, and carves out a distinct niche in E2E browser testing that won't conflict with other testing-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'automate browser interactions', 'validate user workflows', 'testing user registration, login flows, shopping cart functionality', 'cross-browser testing', and 'verify responsiveness on different devices'. | 3 / 3 |
Completeness | Clearly answers both what (generate E2E tests using Playwright/Cypress/Selenium for browser automation) AND when with explicit 'Use this skill when...' clause listing specific trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'E2E tests', 'end-to-end tests', 'browser-based testing', 'Playwright', 'Cypress', 'Selenium', 'web applications', 'login flows', 'shopping cart', 'cross-browser testing'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on E2E/browser-based testing with distinct triggers like 'Playwright', 'Cypress', 'Selenium', and 'end-to-end tests' that are unlikely to conflict with unit testing or other testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is overly abstract and descriptive rather than actionable. It explains what Claude would do conceptually but provides no executable code examples, specific selectors, or concrete test patterns. The content wastes tokens explaining E2E testing concepts Claude already understands while failing to provide the actual implementation guidance needed.
Suggestions
Replace abstract descriptions with executable code examples for each framework (Playwright, Cypress, Selenium) showing actual test patterns with selectors and assertions
Remove the 'How It Works' and 'When to Use This Skill' sections - these describe Claude's process rather than providing actionable guidance
Add concrete test templates with placeholder selectors that can be adapted, rather than describing what a test 'will' do
Include validation steps such as how to verify tests pass, handle flaky tests, and debug failures
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what E2E tests are, what user workflows are). The 'How It Works' section describes Claude's own process unnecessarily, and 'When to Use This Skill' repeats information from the description. | 1 / 3 |
Actionability | No executable code is provided anywhere. Examples describe what 'the skill will' do abstractly rather than providing actual Playwright/Cypress/Selenium code that Claude could use or adapt. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | The examples outline steps at a high level (generate script, configure test), but lack concrete validation checkpoints, error handling, or feedback loops. No guidance on verifying test correctness or handling failures. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline in one file. References to 'other plugins' are vague. Could benefit from linking to framework-specific reference files for Playwright, Cypress, and Selenium patterns. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Reviewed
Table of Contents
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.