152-java-performance-gatling

Use when you need to set up Gatling performance testing for a Java Maven project — including adding Gatling dependencies and the Gatling Maven plugin, creating Java simulations, running gatling:test, configuring a simulation class, and reviewing generated reports. This should trigger for requests such as Add Gatling performance testing; Apply Gatling performance testing; Create a Gatling simulation; Add Gatling support. Part of cursor-rules-java project

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

The body is a well-organized, concise overview with excellent progressive disclosure to a real reference file, but its standalone actionability and workflow clarity are held back because the executable code and an explicit error-recovery feedback loop are deferred or absent.

Suggestions

Add a short, copy-paste-ready pom.xml dependency/plugin snippet (or a one-line pointer to the exact reference section) so the build configuration is actionable without loading the full reference.

Insert an explicit feedback checkpoint in the workflow — e.g. after running gatling:test, 'If assertions fail or compilation errors occur, fix the simulation/pom and re-run before reviewing reports' — to add the validate→fix→retry loop.

Tighten the mild redundancy between the 'What is covered in this Skill?' list and the 'Workflow' steps so the body does not state the same six items twice.

Dimension	Reasoning	Score
Conciseness	The body is a lean overview that assumes Claude's competence — it does not explain what Gatling or Maven is, gives concrete commands and paths, and defers detail to the reference file, so every token earns its place.	3 / 3
Actionability	It provides concrete commands ('./mvnw gatling:test', '-Dgatling.simulationClass=<FullyQualifiedClassName>') and specific plugin coordinates, but the actual copy-paste-ready pom.xml and Java simulation code live in the reference rather than the body, leaving the body's guidance incomplete for build configuration.	2 / 3
Workflow Clarity	The six-step Workflow is clearly sequenced and ends with a verification step (Step 6: 'Verify reports and next steps'), but there is no explicit validate→fix→retry feedback loop for error recovery, which the top anchor requires.	2 / 3
Progressive Disclosure	It is a clear overview that signals a single one-level-deep reference ('see references/152-java-performance-gatling.md'), and that referenced file exists and holds the detailed guidance, examples, and constraints — content is appropriately split with easy navigation.	3 / 3
	Total	10 / 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, well-structured description that explicitly covers what the skill does and when it should trigger, with natural trigger phrases and a distinct niche. The only weakness is the second-person 'you' voice in the opening clause, which costs it the top specificity anchor.

Suggestions

Rewrite the opening in third person to avoid the second-person penalty, e.g. 'Sets up Gatling performance testing for a Java Maven project — adding Gatling dependencies...' instead of 'Use when you need to set up...'.

Preserve the 'Use when...' trigger clause but phrase it without 'you', e.g. 'Use when setting up Gatling performance testing for a Java Maven project'.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ('adding Gatling dependencies and the Gatling Maven plugin, creating Java simulations, running gatling:test, configuring a simulation class, and reviewing generated reports'), which would score 3, but 'Use when you need to set up' uses second-person voice ('you'), penalized by one level per the guideline.	2 / 3
Completeness	It clearly answers both what it does (the enumerated setup capabilities) and when to use it ('Use when you need to set up...', 'This should trigger for requests such as...'), with explicit triggers.	3 / 3
Trigger Term Quality	It provides explicit natural trigger phrases a user would actually say: 'Add Gatling performance testing; Apply Gatling performance testing; Create a Gatling simulation; Add Gatling support', giving good coverage.	3 / 3
Distinctiveness Conflict Risk	It targets a clear, narrow niche — Gatling performance testing for a Java Maven project — with distinct triggers, making conflicts with other skills unlikely.	3 / 3
	Total	11 / 12 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/cursor-rules-java
Commit: 86eb63d

Reviewed: 4 days 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.