generating-end-to-end-tests
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-end-to-end-testsThis 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.
Validation
69%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 11 / 16 Passed | |
Implementation
20%This skill content is too abstract and descriptive rather than actionable. It explains what E2E testing is and describes what Claude would do, but provides no actual code examples, test templates, or concrete commands. The content would benefit greatly from executable Playwright/Cypress/Selenium snippets and specific configuration examples.
Suggestions
Add executable code examples for each framework (Playwright, Cypress, Selenium) showing actual test syntax for common workflows like login or form submission
Remove the 'How It Works' section that describes Claude's internal process - this wastes tokens explaining what Claude will figure out itself
Replace the abstract 'Example 1' and 'Example 2' descriptions with actual test code that can be copied and adapted
Add validation guidance: how to run tests, interpret failures, and debug common issues like selector problems or timing issues
| 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. The examples describe what 'the skill will' do in abstract terms rather than providing actual Playwright, Cypress, or Selenium code that Claude could use or adapt. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists steps but they are abstract process descriptions rather than actionable workflows. No validation checkpoints or error handling guidance is provided for test execution or debugging failures. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The 'Integration' section hints at other capabilities without providing references. No links to framework-specific guides or example repositories. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
100%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. The description uses proper third-person voice throughout.
| 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', plus framework names (Playwright, Cypress, Selenium) and specific use cases like 'login flows', 'shopping cart'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on E2E/browser-based testing with distinct triggers like 'E2E tests', 'end-to-end tests', and specific frameworks; unlikely to conflict with unit testing or other testing skills. | 3 / 3 |
Total | 12 / 12 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.