CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/karate-testing

Authors Karate `.feature` files using its Gherkin-flavored DSL for HTTP API tests, leverages the `match` keyword with fuzzy validators (#number / #string / #regex / contains / arrays), runs the suite via JUnit 5 plus Maven Surefire, and produces JUnit XML for CI gating. Use when the project is on the JVM and prefers a feature-file authoring flow over Java-DSL fluent chains; for those fluent chains use restassured-testing, for the same YAML-style flow on a Python/pytest stack use tavern-testing.

76

Quality

95%

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

88%

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

A lean, actionable skill body with executable Maven, Gherkin, Java, and CI snippets and good progressive disclosure into match-reference.md. The main gap is workflow clarity around CI/test-failure gating: the pipeline uploads reports but never explicitly breaks the build on test failure.

Suggestions

Add an explicit CI validation checkpoint — e.g. note that Surefire fails the `mvn test` step on any Karate scenario failure (non-zero exit), so the report-upload is conditional (`if: always()`) rather than the gate.

In the Anti-patterns 'Skipping --bail equivalent' row, state the concrete verification step (which `-fae` / `-Dsurefire.failIfNoTests=false` flag actually gates) rather than leaving it as a pattern to explore.

Clarify how `karate-summary.xml` is consumed for CI gating beyond artifact upload — e.g. tie dorny/test-reporter's fail-on-error setting to the JUnit XML so a failed scenario fails the workflow.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence — no tutorials on what Gherkin or Maven are — and every section (Install, Authoring, Running, Reporting, CI) earns its place with executable snippets rather than prose padding.

3 / 3

Actionability

Provides copy-paste-ready Maven dependency XML, runnable .feature and Java runner examples, and a complete CI workflow YAML with real action versions, matching the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Sequences are present (author feature -> run via JUnit 5 -> CI gates via JUnit XML) but there are no explicit validation checkpoints or feedback loops; the CI section lacks a 'fail the build on test failure' verification step beyond artifact upload.

2 / 3

Progressive Disclosure

SKILL.md is a focused overview with the heavy keyword/match-modifier vocabulary correctly offloaded to references/match-reference.md (a real, one-level-deep file), well-signaled by inline links; no nested reference chains.

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, dense description: it states concrete capabilities, an explicit use-trigger tied to the JVM, and three-way routing away from sibling skills. Third person throughout with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: authors .feature files, leverages the match keyword with specific fuzzy validators (#number/#string/#regex/contains/arrays), runs via JUnit 5 + Maven Surefire, and produces JUnit XML — directly matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (authors feature files, runs via JUnit 5/Maven Surefire, produces JUnit XML) and 'when' ('Use when the project is on the JVM and prefers a feature-file authoring flow'), satisfying the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Covers natural user terms (HTTP API tests, feature-file authoring, Gherkin, match keyword, JUnit XML) plus the JVM stack cue that a user would naturally reference, giving good coverage of likely utterances.

3 / 3

Distinctiveness Conflict Risk

A clear niche (JVM + feature-file/Gherkin flow) is sharpened by explicit redirects to restassured-testing for fluent chains and tavern-testing for Python/pytest, making wrong-skill triggering unlikely.

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