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
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 strong skill description that concisely covers specific capabilities, includes natural trigger terms, explicitly states when to use it, and carves out a distinct niche around e2e testing. The added behavioral constraint ('Never changes source code logic or API without spec backing') is a nice touch that further clarifies scope and prevents misuse.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Run e2e tests', 'fix flake and outdated tests', 'identify bugs against spec'. Also includes a behavioral constraint ('Never changes source code logic or API without spec backing'). | 3 / 3 |
Completeness | Clearly answers both 'what' (run e2e tests, fix flake/outdated tests, identify bugs against spec) and 'when' (explicit 'Use when running e2e tests, debugging test failures, or fixing flaky tests'). Also includes a boundary constraint for additional clarity. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'e2e tests', 'test failures', 'flaky tests', 'debugging'. These are terms developers naturally use when dealing with end-to-end testing issues. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to e2e testing specifically, with the constraint about not changing source code logic distinguishing it from general coding or unit testing skills. The 'against spec' framing further narrows its niche. | 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 well-designed with concrete symptoms and fix rules per category, and the strict source code boundary rules provide important safety constraints. The only minor weakness is that all content is inline rather than split across files, though the overall length and organization are reasonable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. Every section earns its place—the failure taxonomy is tightly structured, fix rules are specific constraints rather than explanations, and there's no padding or explanation of concepts Claude already knows. | 3 / 3 |
Actionability | Provides concrete executable commands (playwright test invocations, grep filters), specific anti-patterns to avoid (never add arbitrary delays, never weaken assertions), exact replacement patterns (waitForTimeout → auto-waiting locators), and a structured output template. The fix rules are precise and copy-paste actionable. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit validation (re-run after fixes), a categorization checkpoint before fixing, and a structured reporting format. The fix ordering (flaky → outdated → bug) is justified. The bug category includes a TDD gate and spec-verification requirement, providing strong feedback loops. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections (Principles vs Workflow), but everything is inline in a single file. The failure taxonomy, fix rules, and workflow could benefit from being split—the Principles section alone is substantial. However, the total length is manageable and the structure is clear enough that this is a minor issue. | 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
e437c3c
- 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.