CtrlK
BlogDocsLog inGet started
Tessl Logo

benchmark-e2e

End-to-end benchmark suite for vercel-plugin. Runs realistic projects through skill injection, launches dev servers, verifies everything works, analyzes conversation logs, and produces an improvement report for overnight self-improvement loops.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/benchmark-e2e/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The body is well-structured, actionable, and concise with clear sequencing and a genuine feedback loop. It scores consistently at 4 across dimensions, held back only by minor verbosity, lack of inline script bodies, and no external reference structure.

DimensionReasoningScore

Conciseness

The body is dense and information-rich with justified contracts and interfaces; only minor instances of over-explanation (e.g. "instead of guessing from directory listings") could be trimmed.

4 / 5

Actionability

Concrete, copy-paste-ready commands (`bun run scripts/benchmark-e2e.ts`, the overnight loop, cleanup) and explicit TypeScript contracts give mostly executable guidance, with minor gaps where referenced scripts are not shown inline.

4 / 5

Workflow Clarity

Four pipeline stages are clearly sequenced with abort-on-failure and an explicit verify checkpoint ("polls for 200 with non-empty HTML"), plus a documented Run→Read→Fix→Re-run→Compare feedback loop; minor gaps in within-run error recovery keep it just below 5.

4 / 5

Progressive Disclosure

No bundle files exist, so all content is inline, but it is well-organized into clearly headed sections (Quick Start, Pipeline Stages, Contracts, Prompt Table, Cleanup) with easy navigation; the large contracts and 9-row prompt table could arguably be externalized.

4 / 5

Total

16

/

20

Passed

Description

66%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.

The description is specific and action-rich with a clear niche, but it lacks an explicit "Use when..." trigger clause, capping completeness at 3. Trigger terms are good but could include more synonyms.

Suggestions

Add an explicit trigger clause such as "Use when running end-to-end benchmarks or overnight self-improvement loops for the vercel-plugin."

Replace the generic "verifies everything works" with a concrete action like "verifies dev servers return 200 with non-empty HTML."

Include natural synonyms (e.g. "e2e", "test suite", "CI benchmarks") to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Runs realistic projects through skill injection, launches dev servers, ... analyzes conversation logs, and produces an improvement report"), but "verifies everything works" is generic, leaving a minor coverage gap rather than comprehensive specificity.

4 / 5

Completeness

The "what" is clear and detailed, but there is no explicit "Use when..." trigger clause; the phrase "for overnight self-improvement loops" only weakly implies the "when", so completeness is capped per the missing-trigger guideline.

3 / 5

Trigger Term Quality

Natural terms like "benchmark", "end-to-end benchmark", and "dev servers" are present, giving good keyword coverage, though a few common variations (e.g. "e2e", "test suite") are absent.

4 / 5

Distinctiveness Conflict Risk

The niche (vercel-plugin e2e benchmarking, skill injection, self-improvement loops) is mostly distinct with low conflict risk, though the broad term "benchmark suite" could overlap with general testing skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

15

/

16

Passed

Repository
vercel/vercel-plugin
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.