CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/e2e-suite-budget

Caps E2E suite size by computing per-test ROI - (regressions caught × value) ÷ (runtime × flake rate × maintenance) - then ranks every end-to-end test and recommends which bottom-decile ones to retire, move to a lower layer, or fix. Use when CI is slow or E2E-dominated, flaky failures are rising, or quarterly to keep suite size within maintenance capacity. For strategic unit:service:UI layer ratios use test-pyramid-balancer, for the minimal per-deploy critical-path gate use smoke-suite-gate, and for quarantining flaky tests use flaky-test-quarantine; this prunes low-signal tests by ROI.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A highly actionable, well-structured skill body with clear workflows and good progressive disclosure; the only weakness is token redundancy from restating the formula and some obvious filler.

Suggestions

State the ROI formula once in Step 2 and reference it from the Overview and Worked example instead of restating it three times.

Remove obvious filler such as 'Higher ROI = more value per cost.' that adds no information Claude doesn't already infer.

Trim the Step 4 mock output table (e.g., show 3-4 representative rows) or move the full template to a reference file to reduce inline bulk.

DimensionReasoningScore

Conciseness

Mostly efficient, but the ROI formula is restated three times (Overview, Step 2, Worked example), obvious filler like 'Higher ROI = more value per cost' appears, and the Step 4 mock table runs long with a '(10 more)' placeholder.

2 / 3

Actionability

Provides fully executable Python scoring code (Step 3), a concrete YAML budget file (Step 6), a copy-paste output template (Step 4), and a categorization table - all directly usable.

3 / 3

Workflow Clarity

A clear 7-step sequence with an explicit validation checkpoint (Step 1a) and a feedback loop that warns when >50% of tests score 0.0, catching bad-input failures early.

3 / 3

Progressive Disclosure

SKILL.md is a well-sectioned overview with anti-patterns/limitations split into a single one-level-deep, well-signaled reference file (verified to exist), giving easy navigation.

3 / 3

Total

11

/

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 strong, third-person description that names concrete actions, gives natural trigger terms, answers both what and when, and clearly disambiguates from sibling skills. No notable weaknesses.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - computing per-test ROI, ranking every end-to-end test, and recommending retire / move-to-lower-layer / fix - rather than vague abstractions.

3 / 3

Completeness

Clearly answers both what it does (ROI-based pruning) and when to use it via an explicit 'Use when...' trigger clause.

3 / 3

Trigger Term Quality

The 'Use when CI is slow or E2E-dominated, flaky failures are rising, or quarterly' clause covers natural terms a user would actually say when they need this skill.

3 / 3

Distinctiveness Conflict Risk

Has a clear E2E-ROI-pruning niche and explicitly routes adjacent intents to test-pyramid-balancer, smoke-suite-gate, and flaky-test-quarantine, minimizing wrong-skill triggering.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents