CtrlK
BlogDocsLog inGet started
Tessl Logo

500-frameworks-micronaut-create-project

Use when you need to create a new Maven-based Micronaut 4.x project using SDKMAN-managed Java and Micronaut CLI tooling. This should trigger for requests such as Create a Micronaut Maven project; Bootstrap Micronaut project with SDKMAN; Generate a new Micronaut service. Part of cursor-rules-java project

75

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

85%

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

A well-organized, concise instruction skill with a clear validated workflow and clean one-level-deep reference structure. Its main gap is actionability: the body states the create step in prose while the executable commands live only in the reference.

Suggestions

Add the concrete Micronaut CLI creation command (e.g. the 'mn create-app' invocation with Maven and feature flags) directly in the Workflow's 'Create the Maven project' step so the body is copy-paste ready, keeping the reference for edge cases.

Optionally include one short representative command block for SDKMAN candidate selection (e.g. 'sdk use java <version>') so the verify-tooling step is executable from the body alone.

Trim the repeated 'When to use this skill' section, which duplicates the trigger phrases already in the description, to recover a few tokens.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence — it never explains what Micronaut, Maven, or SDKMAN are, and every section (coverage bullets, constraints, workflow) earns its tokens.

3 / 3

Actionability

Some concrete commands are present ('sdk version', './mvnw clean verify', 'mvn clean verify'), but the central creation step ('Use the Micronaut CLI to create a Maven project') defers the actual commands to the reference, leaving the key action incomplete in the body itself.

2 / 3

Workflow Clarity

A clear 4-step sequence with an explicit validation checkpoint (Step 4 'Verify and report' plus the VERIFY constraint './mvnw clean verify') and a safety gate against overwriting a non-empty target directory, matching the validation-with-feedback anchor.

3 / 3

Progressive Disclosure

The body is a concise overview with a single one-level-deep reference, clearly signaled both in Workflow step 1 and in a dedicated Reference section with a working markdown link; the referenced file exists and is substantive.

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, specific description with an explicit 'Use when...' trigger, natural trigger phrases, and a well-scoped niche that minimizes conflict risk. The only minor blemish is the vestigial 'Part of cursor-rules-java project' tag, which adds no trigger value.

DimensionReasoningScore

Specificity

Names concrete actions and specific tooling — 'create a new Maven-based Micronaut 4.x project using SDKMAN-managed Java and Micronaut CLI tooling' — matching the multiple-specific-actions anchor rather than the vague or partial anchors.

3 / 3

Completeness

Explicitly answers both what ('create a new Maven-based Micronaut 4.x project...') and when ('Use when you need to... This should trigger for requests such as...'), satisfying the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Includes natural phrases users would say — 'Create a Micronaut Maven project', 'Bootstrap Micronaut project with SDKMAN', 'Generate a new Micronaut service' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

A clear niche (Micronaut 4.x + Maven + SDKMAN-managed Java) with distinct triggers unlikely to fire for unrelated skills; the trailing 'Part of cursor-rules-java project' does not blur the niche.

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.

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.