Name: testland/restassured-testing
Rating: 69.6 (1 reviews)
Author: testland

testland/restassured-testing

Authors REST Assured (Java) API tests using the given().when().then() BDD-style DSL - status code + JSON/XML path assertions + authentication (Basic, OAuth2, API key). Configures Maven / Gradle dependencies, runs via JUnit 5, and emits Surefire / JaCoCo reports for CI gating. Use when the project is on the JVM and wants type-safe API tests in the app's own language; for a Gherkin feature-file flow on the same JVM use karate-testing, for YAML tests on the pytest stack use tavern-testing.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

Strong, executable skill content with excellent code coverage and a useful anti-patterns table. Minor trimming of repetitive citations and an explicit CI validation/gating checkpoint would push it higher.

Suggestions

Consolidate the repeated '(Per [restassured-usage][usage].)' and '(Per [restassured-readme][readme].)' citations into a single 'Sources' note to reduce token overhead.

Add an explicit CI gating checkpoint in the CI section (e.g., fail the workflow when failsafe reports show failures, or assert required coverage via JaCoCo before merge) to match the description's promised 'CI gating'.

The description mentions JaCoCo reports but the body only covers Failsafe/Surefire JUnit XML; add a short JaCoCo snippet or note so the body delivers on the description's claims.

Dimension	Reasoning	Score
Conciseness	Mostly lean—code blocks and tables earn their place—but several 'Why it fails' explanations and repeated citations like '(Per [restassured-usage][usage].)' add minor padding that could be trimmed without losing meaning.	4 / 5
Actionability	Copy-paste-ready Maven/Gradle snippets, executable given/when/then examples covering status, JSON/XML paths, auth, and a complete JUnit 5 test plus a CI workflow—concrete and covering the common cases.	5 / 5
Workflow Clarity	Sections progress logically from install to authoring to CI, and the anti-patterns table gives corrective guidance, but there is no explicit validate-then-proceed checkpoint for the batch/CI run or report gating beyond 'always()' on artifact upload.	4 / 5
Progressive Disclosure	Well-organized single-file overview with clear section headers and inline external links to the upstream README/usage wiki at one level; no nested references, though all content is inlined rather than split into separate bundle files.	4 / 5
	Total	17 / 20 Passed

Description

88%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 high-quality description: specific, concrete, and complete with explicit trigger guidance and a clear niche. Slightly verbose but the detail is substantive rather than fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—status code and JSON/XML path assertions, authentication (Basic, OAuth2, API key), Maven/Gradle dependencies, JUnit 5 execution, and Surefire/JaCoCo reports—comprehensive and specific rather than abstract.	5 / 5
Completeness	Explicitly answers both 'what' (authors REST Assured tests with DSL, assertions, auth, deps, execution, reports) and 'when' ('Use when the project is on the JVM and its API tests miss real assertions, run too slowly, or are written by hand') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Contains natural trigger phrases like 'API tests miss real assertions, run too slowly, or are written by hand' and 'project is on the JVM', but is missing some common shorthand synonyms a user might say (e.g. 'REST tests', 'API integration tests').	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to JVM/REST Assured with explicit counterpart contrast, giving it a clear niche unlikely to trigger for non-JVM API testing skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

14 days ago

Table of Contents

Discovery Implementation Validation