CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

e2e-testing

Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/e2e-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

A well-structured, token-efficient overview with excellent progressive disclosure to a real, self-contained reference file. Its weaknesses are that the body itself contains no executable code or commands (details live entirely in the reference) and the Check/Fix/Code Review flow lacks explicit validation checkpoints such as confirming E2E failures actually block regressions.

Suggestions

Add one short copy-paste-ready snippet or command to the Fix section (e.g., a minimal Playwright test scaffold or the npx playwright test invocation) so the body is actionable without opening the reference file.

Strengthen the Check/Code Review sections with an explicit validation checkpoint, e.g. 'Confirm E2E failures block the PR merge in CI; if they are report-only, flag the workflow as non-enforcing.'

Trim the opening explanatory sentence about what E2E tests catch (a concept Claude already knows) and drop the duplicated 'Rule page' URL to reclaim tokens.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and directive ('Test critical user journeys', 'Use data-testid attributes'), with only minor trims available: the opening sentence 'E2E tests catch integration issues that unit tests miss...' explains a concept Claude already knows, and the trailing 'Rule page' URL duplicates frontmatter metadata. This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than 5, but is well above the noticeably-verbose level 2.

4 / 5

Actionability

The body offers specific but incomplete guidance: 'Add E2E tests for critical user journeys using Playwright or Cypress' names tools, and Quick Reference items like 'data-testid attributes' and 'Page Object Model' are concrete practices, but no executable code, commands, or examples appear in the body — all of that is deferred to references/rule.md. This matches 'some concrete guidance but incomplete; missing key details' rather than 4's 'concrete code or commands with minor gaps'.

3 / 5

Workflow Clarity

The Check → Fix → Code Review sections give a recognizable task structure ('Review this project for E2E test coverage...', 'Flag exact gaps where the rule is not automatically verified'), but the sequence between the Check/Fix/Explain/Code Review modes is implicit and there are no validation checkpoints (e.g., 'run the suite in CI and confirm it blocks the merge on failure'). This matches 'steps listed but validation gaps; checkpoints missing or implicit' rather than 4, which requires most checkpoints present.

3 / 5

Progressive Disclosure

The body is a concise overview that defers all implementation detail to a single clearly signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and the file exists in the bundle with no nested references beyond it. Sections (Quick Reference, Check, Fix, Explain, Code Review) are well organized and easy to navigate, matching the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

15

/

20

Passed

Description

70%Weight 40%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.

A solid description with an explicit 'Use when...' trigger, good natural keywords, and a clear niche anchored to E2E testing. Its main weaknesses are that the 'what' is expressed as a review focus rather than distinct concrete capabilities, and common trigger synonyms ('E2E', tool names) are missing.

DimensionReasoningScore

Specificity

The description names the domain and a couple of concrete actions — 'reviewing CI coverage, automated checks, or test strategy' — plus a focus directive ('Focus on whether the rule is continuously verified'), but does not enumerate several distinct actions, so it matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It falls short of 4 because all verbs collapse into a single 'reviewing' action rather than several specific capabilities, and is above 2 because the domain and actions are concrete, not generic.

3 / 5

Completeness

Both parts are present: 'Use when reviewing CI coverage, automated checks, or test strategy...' gives an explicit when, and 'reviewing... Focus on whether the rule is continuously verified, not just documented' gives a what. It matches anchor 4 ('when' present, 'what' could be more explicit) rather than 5 because the what is a review focus rather than a crisp capability statement like 'Flags gaps where E2E coverage is not enforced in CI'. Not 3 since the when clause is fully explicit.

4 / 5

Trigger Term Quality

Good natural-term coverage: 'CI coverage', 'automated checks', 'test strategy', 'end-to-end testing', 'verified'. A few common variations are missing — the 'E2E' abbreviation users commonly say, tool names like Playwright/Cypress, and 'test coverage' — matching the 'good keyword coverage; a few natural terms missing' anchor. Not 5 because synonyms and abbreviations are absent; not 3 because coverage clearly goes beyond a single keyword.

4 / 5

Distinctiveness Conflict Risk

The scope is anchored to a specific niche — 'related to Implement end-to-end testing' — keeping it distinct from generic testing or CI skills, though broad triggers like 'automated checks' and 'test strategy' create minor overlap risk with adjacent testing/CI skills, matching anchor 4. Not 5 because those generic terms could fire for other verification-related skills; not 3 because the E2E anchor keeps it mostly distinct.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/e2e-testing/SKILL.md

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.