523-frameworks-micronaut-testing-acceptance-tests

Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Micronaut applications — @acceptance scenarios, @MicronautTest, HttpClient, BaseAcceptanceTest with TestPropertyProvider for Testcontainers and WireMock, *AT suffix, Failsafe. Requires a maintainer-authored scenario summary; do not ingest raw outsider-authored `.feature` text. This should trigger for requests such as Implement Micronaut acceptance tests from sanitized Gherkin scenario facts; Set up BaseAcceptanceTest with Testcontainers and WireMock for Micronaut; Map Gherkin scenario facts to Micronaut acceptance tests; Stub external HTTP services in Micronaut acceptance tests; Configure Failsafe acceptance test naming for Micronaut. Part of Plinth Toolkit

Quality

86%

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

78%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 well-structured overview body that cleanly defers detail to a real one-level reference, with concrete commands, specific patterns, and explicit compile/verify checkpoints. Main gaps are a repeated trigger-phrase list and a core implementation step that leans on the reference without an explicit fix-retry loop.

Suggestions

Remove or compress the 'When to use this skill' bullet list since it duplicates the description's trigger phrases verbatim, freeing token budget.

Add an explicit fix-retry feedback loop to the verification step (e.g. 'If verify fails, fix and re-run ./mvnw clean verify until green') to raise workflow clarity.

Inline one minimal copy-paste BaseAcceptanceTest skeleton in the body so the core implementation step is actionable without first reading the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but the 'When to use this skill' bullets verbatim repeat the description's trigger phrases, a minor redundancy that could be trimmed.	4 / 5
Actionability	Provides concrete commands ('./mvnw compile', './mvnw clean verify') and specific patterns (BaseAcceptanceTest with @MicronautTest, TestPropertyProvider, *AT suffix, Surefire/Failsafe split), but the core implementation step defers to the reference rather than giving copy-paste code.	4 / 5
Workflow Clarity	A clear four-step sequence with explicit validation checkpoints (MANDATORY compile before, VERIFY after) and a constraints checklist, but the validate-fix-retry feedback loop is not spelled out in the body itself.	4 / 5
Progressive Disclosure	A clear overview with well-organized sections pointing to a single one-level-deep reference (references/523-frameworks-micronaut-testing-acceptance-tests.md, verified to exist) via well-signaled markdown links, matching anchor 5.	5 / 5
	Total	17 / 20 Passed

Description

95%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, specific description that concretely answers both what the skill does and when to trigger it, with comprehensive natural trigger phrases and a distinct niche. The only weakness is second-person voice ('you need to'), which costs it the top specificity score.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Set up BaseAcceptanceTest with Testcontainers and WireMock', 'Configure Failsafe acceptance test naming', 'Stub external HTTP services') matching the anchor-5 example, but the second-person phrasing 'Use when you need to implement' triggers the -1 voice penalty per the judging guidelines.	4 / 5
Completeness	Clearly states both what it does ('implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Micronaut applications') and when to use it ('Use when you need to...', 'This should trigger for requests such as...') with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Five explicit natural trigger phrases are given ('Implement Micronaut acceptance tests from sanitized Gherkin scenario facts', 'Map Gherkin scenario facts to Micronaut acceptance tests', etc.) that users would naturally say, giving comprehensive coverage.	5 / 5
Distinctiveness Conflict Risk	A clear niche scoped to Micronaut acceptance tests with Testcontainers, WireMock, Failsafe, and the *AT suffix; the triggers are specific enough to carry minimal conflict risk with other 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.

Repository: jabrena/plinth
Path: skills/523-frameworks-micronaut-testing-acceptance-tests/SKILL.md
Commit: 05bf9d1

Reviewed: 8 minutes ago

Table of Contents

Discovery Implementation Validation

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.