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.

1.22x

Quality

—

Does it follow best practices?

Impact

75%

1.22x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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

A tightly written, highly actionable skill: concrete fix rules, a sequenced workflow with re-run validation, and clean organization. The report template and categorization gate make guidance unambiguous.

Dimension	Reasoning	Score
Conciseness	Lean throughout — no padding explaining what e2e tests or Playwright are; every line (taxonomy, fix rules, commands) earns its place and assumes Claude's competence.	3 / 3
Actionability	Provides executable commands ("yarn playwright test --reporter=line"), concrete locator replacements (getByRole/getByLabel/getByTestId), and a copy-paste-ready failure table and report template.	3 / 3
Workflow Clarity	Five clearly sequenced steps with a re-run/report feedback loop, validation via spec-backed categorization, and explicit ordering rules (flaky → outdated → bug).	3 / 3
Progressive Disclosure	Well-organized single-file skill with clear sections (Principles vs Workflow); no nested references and no bundle files to manage, appropriate for its size.	3 / 3
	Total	12 / 12 Passed

Description

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.

A concise, specific description that answers what, when, and the scope boundary, with natural trigger terms and low conflict risk. One minor note: "fix flake" is slightly informal but remains a recognizable user term.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Run e2e tests, fix flake and outdated tests, identify bugs against spec" — each naming a distinct capability rather than vague language.	3 / 3
Completeness	Explicitly answers what (run/fix/identify bugs) and when ("Use when running e2e tests, debugging test failures, or fixing flaky tests"), plus a guard clause, satisfying both halves.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — "running e2e tests", "debugging test failures", "fixing flaky tests" — with good variation including the colloquial "flake".	3 / 3
Distinctiveness Conflict Risk	The e2e-testing niche with the "Never changes source code logic or API without spec backing" boundary clearly distinguishes it from general testing or coding skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Commit: ff6a653

Reviewed: 1 day 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.