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; Review Gatling performance test assertions and feeders. Part of Plinth Toolkit

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

A well-structured, well-sequenced skill body with clear workflow, edge cases, and a properly signaled single reference. The main gaps are minor duplication inflating token cost and the absence of copy-paste build/simulation code in the body itself.

Suggestions

Drop the 'When to use this skill' section (it repeats the description's triggers verbatim) and merge the 'What is covered' bullets into the Workflow to remove redundancy.

Include a minimal copy-paste pom.xml snippet showing the io.gatling:gatling-maven-plugin configuration so the build setup is executable without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's intelligence, but the 'When to use this skill' section duplicates the description's trigger list verbatim and 'What is covered' overlaps the Workflow steps, so it could be tightened.	2 / 3
Actionability	It gives concrete commands ('./mvnw gatling:test', '-Dgatling.simulationClass=<FullyQualifiedClassName>', './mvnw gatling:help -Ddetail=true -Dgoal=test') and the plugin coordinate, but lacks a copy-paste pom.xml snippet or Java simulation code in the body, deferring that to the reference.	2 / 3
Workflow Clarity	A clear six-step sequence (inspect → configure → simulate → resources → run → verify) with an explicit verification checkpoint in step 6 and explicit edge-case recovery (non-Maven stops; multiple simulations pass the class flag).	3 / 3
Progressive Disclosure	The body is a concise overview that delegates detail to a single well-signaled, one-level-deep reference ('see references/152-java-performance-gatling.md'), and that referenced file exists in the bundle.	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, specific description with explicit what-and-when trigger guidance and a clear niche. The only ding is the second-person 'you' phrasing, which the rubric penalizes on specificity.

Dimension	Reasoning	Score
Specificity	It 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 anchor at 3, but the rubric penalizes second-person voice ('Use when you need to set up') by reducing specificity by 1.	2 / 3
Completeness	It explicitly answers both 'what' (the enumerated setup actions) and 'when' with explicit trigger guidance ('Use when you need to set up…', 'This should trigger for requests such as…').	3 / 3
Trigger Term Quality	Natural phrases a user would actually say are well covered ('Add Gatling performance testing', 'Apply Gatling performance testing', 'Create a Gatling simulation', 'Add Gatling support', 'Review Gatling performance test assertions and feeders').	3 / 3
Distinctiveness Conflict Risk	It carves a clear niche (Gatling performance testing for Java Maven projects) with distinct triggers, making it unlikely to fire for an unrelated skill.	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/plinth
Commit: aaee915

Reviewed: 1 day 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.