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.
92
Quality
96%
Does it follow best practices?
Impact
75%
1.22xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 well-crafted skill description that clearly defines its scope (e2e testing), lists specific actions, includes explicit 'Use when' triggers with natural user terminology, and establishes clear boundaries. The constraint about not changing source code logic helps distinguish it from general development skills and sets appropriate expectations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Run e2e tests', 'fix flake and outdated tests', 'identify bugs against spec'. Also includes a constraint about not changing source code logic or API without spec backing. | 3 / 3 |
Completeness | Clearly 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'e2e tests', 'test failures', 'flaky tests', 'debugging'. These are common terms developers use when discussing end-to-end testing issues. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on e2e testing with distinct triggers like 'e2e tests', 'flaky tests', and 'test failures'. The constraint about not changing source code further distinguishes it from general coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides clear, actionable guidance for e2e test management. The failure taxonomy is particularly strong, giving Claude exact decision criteria. The workflow includes proper validation checkpoints and the fix rules are specific and bounded. Minor improvement possible in progressive disclosure for larger codebases.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context about what e2e testing is or how Playwright works. | 3 / 3 |
Actionability | Provides concrete, executable commands (yarn playwright test --reporter=line), specific fix patterns (replace waitForTimeout with auto-waiting locators), and copy-paste ready examples. The failure taxonomy gives exact criteria for categorization. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit validation (Step 5: Re-run and Report). The fix rules include explicit constraints ('Never add arbitrary delays', 'Never weaken assertions') and the bug fix path requires unit tests before completion - a proper feedback loop. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections (Principles vs Workflow), but everything is inline in one file. The report template at the end could be a separate reference, and there are no links to external documentation for advanced Playwright patterns. | 2 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
5342bca
- 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.