CtrlK
BlogDocsLog inGet started
Tessl Logo

522-frameworks-micronaut-testing-integration-tests

Use when you need to write or improve integration tests for Micronaut — @MicronautTest, HttpClient, TestPropertyProvider with Testcontainers, transactional test mode where appropriate, and Maven Surefire/Failsafe splits for *Test, *Tests, *IT, and *AT. This should trigger for requests such as Add Micronaut integration tests with Testcontainers; Wire dynamic datasource or broker URLs for @MicronautTest. Part of cursor-rules-java project

63

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

57%

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 with good progressive disclosure and a real validation gate, held back by repetitive constraints and abstract workflow steps that delegate the concrete guidance to the reference.

Suggestions

Collapse the redundant compile-before/stop-on-failure constraints (MANDATORY, PREREQUISITE, CRITICAL SAFETY, BLOCKING CONDITION, NO EXCEPTIONS) into a single concise checkpoint to improve conciseness.

Make workflow steps 2-3 concrete — e.g., specify which reference patterns to apply or what 'framework-aligned changes' concretely means — rather than abstract descriptions.

Integrate the compile/verify validation checkpoints directly into the numbered workflow steps so the sequence and the gating read as one flow.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the Constraints section restates the same compile-before / stop-on-failure rule five times (MANDATORY, PREREQUISITE, CRITICAL SAFETY, BLOCKING CONDITION, NO EXCEPTIONS), adding repetition that could be tightened.

2 / 3

Actionability

Concrete commands are present ('./mvnw compile', 'mvn clean verify') and a reference is clearly pointed to, but the core test-writing patterns are delegated to the reference and workflow steps 2-3 are abstract ('Apply framework-aligned changes').

2 / 3

Workflow Clarity

A clear 4-step sequence exists with explicit validation (compile gate, hard-stop on failure, verify-after), but the checkpoints live in a separate Constraints block and the steps themselves are generic rather than concrete per-step checkpoints.

2 / 3

Progressive Disclosure

The body is a concise overview that signals a single verified, one-level-deep reference (references/522-frameworks-micronaut-testing-integration-tests.md) via a markdown link, with content appropriately split between overview and detail.

3 / 3

Total

9

/

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.

A strong, specific description with explicit triggers and a clear niche, weakened only by second-person voice in the 'Use when' clause which the rubric penalizes on specificity.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('@MicronautTest, HttpClient, TestPropertyProvider with Testcontainers, transactional test mode ... Maven Surefire/Failsafe splits for *Test, *Tests, *IT, and *AT'), which would warrant a 3, but the second-person voice ('Use when you need to write or improve') triggers the rubric's voice penalty reducing specificity by 1.

2 / 3

Completeness

It clearly answers both 'what' (write/improve Micronaut integration tests with the listed features) and 'when' via explicit triggers ('Use when you need to write or improve integration tests for Micronaut', 'This should trigger for requests such as ...').

3 / 3

Trigger Term Quality

Natural trigger phrasings users would actually say are explicit ('Add Micronaut integration tests with Testcontainers; Wire dynamic datasource or broker URLs for @MicronautTest'), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Micronaut-specific scope ('integration tests for Micronaut', Surefire/Failsafe splits, TestPropertyProvider) carves a clear niche unlikely to trigger for other testing skills.

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
jabrena/cursor-rules-java
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.