CtrlK
BlogDocsLog inGet started
Tessl Logo

e2e

Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.

87

1.22x
Quality

88%

Does it follow best practices?

Impact

75%

1.22x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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, actionable skill body with executable commands, an explicit ordered workflow, and validation checkpoints. Minor redundancy and the absence of any reference split keep it just shy of maximum on conciseness and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean with terse bullets and assumes Claude's knowledge of Playwright/e2e concepts; minor redundancy between the Principles fix rules and Workflow Step 4 referencing them keeps it just below fully lean.

4 / 5

Actionability

It provides copy-paste-ready commands ("yarn playwright test --reporter=line"), concrete fix techniques (getByRole, expect() web-first assertions), a failure-parsing table, and a report template, covering common cases executable as written.

5 / 5

Workflow Clarity

A clear 5-step sequence (Discover → Run → Categorize → Fix → Re-run and Report) with explicit validation checkpoints: re-running the suite, and a unit-test gate for bug fixes, plus ordered fix prioritization.

5 / 5

Progressive Disclosure

Single-file skill with well-organized sections (Principles vs Workflow) and no bundle files; structure is good and navigation is easy, but it is slightly above the simple-skill line and carries no external references, so it sits just below the top anchor.

4 / 5

Total

18

/

20

Passed

Description

87%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 strong description that concretely states capabilities, gives explicit trigger guidance, and adds a clear boundary clause to reduce misuse. Only minor room for additional trigger synonyms.

DimensionReasoningScore

Specificity

"Run e2e tests, fix flake and outdated tests, identify bugs against spec" names the e2e domain and lists several concrete actions (run, fix flake, fix outdated, identify bugs), with only minor coverage gaps, matching the anchor listing several specific actions.

4 / 5

Completeness

It explicitly answers both what ("Run e2e tests, fix flake and outdated tests, identify bugs against spec") and when ("Use when running e2e tests, debugging test failures, or fixing flaky tests") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"Use when running e2e tests, debugging test failures, or fixing flaky tests" includes natural phrases users would say, but misses some synonyms/variations, fitting the good-but-not-comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The e2e-specific niche combined with the boundary clause "Never changes source code logic or API without spec backing" gives it distinct triggers and minimal conflict risk with other testing skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.