CtrlK
BlogDocsLog inGet started
Tessl Logo

run-api-e2e-tests

Run e2e tests for the API service. Use when the user wants to run API E2E tests.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is highly actionable with copy-paste commands and a clear decision-tree workflow for targeting individual tests. Its main weakness is verbosity from repeating the long mocha command verbatim multiple times instead of showing just the varying substitution.

Suggestions

Reduce repetition: in the Examples section, show only the substituted filename portion and refer back to the parameterized command, rather than repeating the full mocha invocation verbatim.

Consider extracting the shared mocha flags (cross-env env vars, --timeout, --retries, --grep, --require, --file) into a single defined base so only the path glob differs between the src/ and enterprise/ variants.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the full mocha command is repeated verbatim in the src/ and enterprise/ sections and then again twice in Examples, which is redundant padding that could be tightened to show only the substitution.

2 / 3

Actionability

It provides fully executable, copy-paste-ready commands (the pnpm script, complete mocha invocations with env vars, glob patterns) plus concrete worked examples, matching the level-3 anchor.

3 / 3

Workflow Clarity

The specific-test flow is clearly sequenced (find file, extract name, determine location, run command) with an explicit src/ vs enterprise/ branch; running tests is non-destructive so no validation checkpoint is required to cap the score.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is a single, well-organized task with clearly labeled sections, so the level-3 simple-skill allowance applies.

3 / 3

Total

11

/

12

Passed

Description

90%

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 concise, third-person, and clearly pairs a concrete action with an explicit trigger clause, scoring well across all dimensions. Its only weak spot is specificity, since it describes a single action rather than enumerating several.

DimensionReasoningScore

Specificity

"Run e2e tests for the API service" names a concrete action and domain, but lists only a single action rather than multiple specific concrete actions, so it does not reach the level-3 anchor.

2 / 3

Completeness

It states what it does ("Run e2e tests for the API service") and an explicit "Use when the user wants to run API E2E tests" trigger, satisfying both halves of the level-3 anchor.

3 / 3

Trigger Term Quality

"run API E2E tests" and "e2e tests" are natural phrases a user would actually say when requesting this skill, matching the level-3 anchor's coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

The API e2e test niche is specific and unlikely to conflict with other skills, and the trigger is distinct rather than generic.

3 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
novuhq/novu
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.