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.
89
53%
Does it follow best practices?
Impact
97%
1.00xAverage score across 9 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-batch-20251204-000554/plugins/testing/e2e-test-framework/skills/e2e-test-framework/SKILL.mdQuality
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 strong skill description that covers specific capabilities, includes explicit trigger guidance, and names concrete tools and use cases. It clearly distinguishes itself from other testing-related skills by focusing on E2E browser-based testing with named frameworks. Minor note: the description uses 'This skill enables Claude to' which is slightly indirect but not first/second person, so no penalty applies.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions and capabilities: generate E2E tests, automate browser interactions, validate user workflows, testing user registration, login flows, shopping cart functionality, cross-browser testing, and responsiveness verification on different devices. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate E2E tests using Playwright/Cypress/Selenium, automate browser interactions, validate workflows) and 'when' with an explicit 'Use this skill when...' clause listing specific trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'create E2E tests', 'generate end-to-end tests', 'browser-based testing', plus tool names (Playwright, Cypress, Selenium) and specific workflow examples (registration, login flows, shopping cart). Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to E2E/browser-based testing for web applications with specific tool mentions (Playwright, Cypress, Selenium). This is a distinct niche unlikely to conflict with unit testing, API testing, or other skill types. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%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 essentially a high-level description of what E2E testing is and when to use it, rather than actionable instructions for Claude. It lacks any executable code examples, concrete test templates, specific commands, or validation steps. The content explains concepts Claude already understands while failing to provide the specific, copy-paste-ready guidance that would make this skill useful.
Suggestions
Add complete, executable code examples for at least one framework (e.g., a full Playwright test script for user registration) instead of describing what the script 'will do'.
Remove the 'Overview', 'How It Works', and 'When to Use This Skill' sections—Claude doesn't need to be told what E2E tests are or when to use them. Replace with concrete templates and patterns.
Add a workflow with validation steps: how to run the generated tests, verify they pass, handle common failures (element not found, timeout), and iterate.
Provide framework-specific configuration snippets (e.g., playwright.config.ts, cypress.config.js) and specify default project structure expectations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what E2E tests are, what user workflows are, how test frameworks work). The 'Overview', 'How It Works', and 'When to Use This Skill' sections largely restate information from the description and each other. The 'Integration' section is vague filler. | 1 / 3 |
Actionability | There is no executable code anywhere in the skill. The examples describe what the skill 'will do' in abstract terms rather than providing actual test scripts, commands, or concrete code snippets. Claude is told to 'generate a Playwright script' but never shown what one looks like or given a template. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists three abstract steps (identify, generate, configure) with no concrete commands, validation checkpoints, or error recovery. There is no guidance on how to run tests, verify results, or handle failures. For a multi-step testing workflow, this is insufficient. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headings, which provides some structure. However, there are no references to external files, no bundle files exist, and content that could benefit from separation (e.g., framework-specific templates) is neither inline nor referenced. The structure is reasonable but the content within it is shallow. | 2 / 3 |
Total | 5 / 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 | |
- Commit
7dedb93
- 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.