CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/restassured-testing

Use whenever Java/JVM API tests need writing or fixing: loose assertions that let an empty 200 pass, slow sequential suites, or hand-rolled HTTP clients. Writes REST Assured given/when/then tests with status, JSON and XML path assertions, auth, JUnit 5, Maven or Gradle and CI reports.

Quality

90%

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

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

A high-quality, self-contained skill body: fully executable examples, a useful anti-patterns table, and honest limitations. The main improvement levers are trimming the repeated per-snippet citation lines and making the authoring-to-CI workflow sequence explicit with a local validation step.

Suggestions

Consolidate the repeated '(Per [restassured-usage][usage].)' citations into a single note in the References section to tighten conciseness.

Add an explicit step between Authoring and CI integration, e.g. 'Run locally first: mvn -B verify -Dapi.baseURI=...' as a validation checkpoint before wiring CI.

Consider moving the full GitHub Actions workflow YAML into a references/ file, keeping a short summary and link inline in SKILL.md.

DimensionReasoningScore

Conciseness

The body is code-first and assumes Java/JUnit competence, but repeated '(Per [restassured-usage][usage].)' citation lines after nearly every snippet and prose restating what the static imports bring into scope are minor over-explanations that could be trimmed.

4 / 5

Actionability

Everything is executable and copy-paste ready: Maven/Gradle dependency blocks, per-pattern snippets, a complete JUnit 5 integration test with env-var auth, and a full GitHub Actions workflow, covering the common cases.

5 / 5

Workflow Clarity

Sections form a coherent install-to-CI progression and the anti-patterns table maps failures to concrete fixes, but there is no explicit numbered sequence or run-locally validation checkpoint before the CI stage.

4 / 5

Progressive Disclosure

No bundle files exist; the single body is well-sectioned with a clearly labeled References section pointing one level deep to real external links. The full CI YAML and auth detail could arguably be split into a reference file, keeping this just below the ideal-split anchor.

4 / 5

Total

17

/

20

Passed

Description

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

A strong description: third-person, concrete, and explicitly triggered, with a clear what/when pair and a well-bounded JVM niche. The only weakness is keyword coverage that omits a few natural synonyms users might say.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities ('status, JSON and XML path assertions, auth, JUnit 5, Maven or Gradle and CI reports') with no noticeable coverage gaps, matching the comprehensive anchor rather than the minor-gaps level below.

5 / 5

Completeness

Both halves are explicit: 'Use whenever Java/JVM API tests need writing or fixing: loose assertions that let an empty 200 pass...' gives concrete trigger phrases for 'when', and 'Writes REST Assured given/when/then tests with...' gives a clear 'what'.

5 / 5

Trigger Term Quality

Natural terms like 'API tests', 'Java/JVM', 'REST Assured', 'JUnit 5', 'Maven or Gradle' and 'hand-rolled HTTP clients' are present, but common variations such as 'integration tests' or 'endpoint testing' are missing, so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The 'Java/JVM' scope plus the REST Assured tooling name carve a clear niche with distinct triggers, keeping overlap risk with non-JVM API-testing skills minimal.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page