e2e-testing-patterns

Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.

Quality

40%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/e2e-testing-patterns/SKILL.md

The canonical home for this skill is e2e-testing-patterns in rmyndharis/antigravity-skills

Quality

Content

43%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a thin outline that lacks the concrete, actionable content needed to be useful. While it is concise and well-scoped, the instructions are too abstract — no specific tools (e.g., Playwright, Cypress), no code examples, no commands, and no validation steps. It relies entirely on a referenced playbook file that wasn't provided in the bundle, making it impossible to verify whether the actual substance exists.

Suggestions

Add concrete, executable code examples for at least one E2E testing framework (e.g., Playwright or Cypress) showing a complete test case for a common user journey.

Expand the four instruction steps with specific commands, tool invocations, and validation checkpoints (e.g., 'Run `npx playwright test --reporter=html` and verify all tests pass before merging').

Include the `resources/implementation-playbook.md` bundle file or inline the most critical patterns so the skill is self-contained enough to be actionable without external references.

Add a feedback loop for flaky test debugging: e.g., 'If a test fails intermittently, capture traces with `--trace on`, review the trace, fix the root cause, and re-run to confirm stability.'

Dimension	Reasoning	Score
Conciseness	The content is fairly lean and doesn't over-explain concepts Claude already knows. The 'Use this skill when' and 'Do not use this skill when' sections add some bulk but are reasonable for scoping. Minor trimming possible in the bullet lists.	4 / 5
Actionability	The instructions are extremely high-level and vague — 'Build stable selectors and test data strategies' and 'Implement tests with retries, tracing, and isolation' provide no concrete code, commands, specific tool references, or executable examples. The skill reads more like an abstract outline than actionable guidance.	2 / 5
Workflow Clarity	While four numbered steps provide a rough sequence, they are poorly defined with no specifics, no validation checkpoints, and no feedback loops. Steps like 'Identify critical user journeys' and 'Build stable selectors' are too abstract to guide execution.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable one-level-deep reference. However, no bundle files were provided, so the reference is unverifiable and the SKILL.md itself contains almost no substantive content — it's essentially an empty shell pointing to a file that may not exist.	3 / 5
	Total	11 / 20 Passed

Description

36%Scale 1-5

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 description reads more like a marketing tagline than a functional skill description. It focuses on aspirational outcomes ('confidence to ship code quickly', 'catch regressions before users do') rather than concrete capabilities and trigger conditions. It lacks a 'Use when...' clause, specific tool/framework mentions, and actionable detail that would help Claude distinguish this skill from other testing-related skills.

Suggestions

Add a 'Use when...' clause with trigger terms like 'e2e tests', 'end-to-end testing', 'Playwright', 'Cypress', 'browser tests', 'test automation'.

Replace the aspirational language with concrete actions such as 'Write end-to-end tests using Playwright/Cypress, create page object models, configure test runners, set up CI test pipelines'.

Include specific file extensions or framework names to improve trigger term quality and distinctiveness (e.g., '.spec.ts', '.test.js', 'Playwright', 'Selenium').

Dimension	Reasoning	Score
Specificity	Names the domain (end-to-end test suites) but the actions are vague and aspirational ('build reliable, fast, and maintainable'). No concrete actions like 'write Playwright tests', 'configure test runners', or 'create page objects' are mentioned.	2 / 5
Completeness	Has a vague 'what' (build end-to-end test suites) but no 'when' clause at all. There is no 'Use when...' guidance, which per the rubric should cap completeness at 3, and the 'what' itself is more of a value proposition than a capability description.	2 / 5
Trigger Term Quality	Includes 'end-to-end test suites' and 'regressions' which are relevant keywords, but misses many natural terms users would say like 'e2e tests', 'Playwright', 'Cypress', 'Selenium', 'browser testing', 'integration tests', 'test automation', or specific framework names.	3 / 5
Distinctiveness Conflict Risk	Somewhat specific to end-to-end testing, which narrows the domain, but could overlap with general testing skills, unit testing skills, or CI/CD skills. The lack of specific frameworks or technologies increases overlap risk.	3 / 5
	Total	10 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/e2e-testing-patterns/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.