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

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/152-java-performance-gatling/SKILL.md

Quality

Content

71%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, concise overview that delegates detail to a single real reference file with clear navigation. Its main weakness is actionability: the body gives commands and coordinates but keeps the executable pom.xml and simulation code in the reference rather than inline.

Suggestions

Include a minimal inline pom.xml dependency/plugin snippet in the body so the core build configuration is actionable without opening the reference.

Add an explicit feedback loop in the Workflow (e.g., 'if gatling:test fails or assertions fail, adjust the simulation/injection profile and re-run') to strengthen validation for a test-execution skill.

Remove the 'When to use this skill' section or fold it into the Constraints, since its trigger phrases duplicate the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no generic explanations of Gatling or Maven); minor redundancy exists where 'When to use this skill' repeats the description's triggers and 'What is covered' overlaps the Workflow steps.	4 / 5
Actionability	Gives concrete commands ('./mvnw gatling:test', '-Dgatling.simulationClass=<FullyQualifiedClassName>', './mvnw gatling:help -Ddetail=true -Dgoal=test') and plugin coordinates, but the actual pom.xml XML and Java simulation code are deferred to the reference rather than shown inline, leaving key details out of the body.	3 / 5
Workflow Clarity	A clear 6-step sequence (Inspect → Add build config → Create simulations → Configure resources → Run → Verify reports) with a verification checkpoint in step 6; the only gap is the absence of an explicit 'if assertions fail → fix → re-run' feedback loop.	4 / 5
Progressive Disclosure	Well-organized overview with sections (What is covered, Scope, Constraints, When to use, Workflow, Reference) and a single clearly-signaled one-level-deep reference ('BEFORE APPLYING: Read the reference' plus the Reference link), confirmed to exist as references/152-java-performance-gatling.md.	5 / 5
	Total	16 / 20 Passed

Description

87%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 with explicit what/when structure and natural trigger phrases. The only notable issue is second-person voice ('you need to'), which costs it a specificity point per the rubric guidelines.

Dimension	Reasoning	Score
Specificity	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'), matching the comprehensive anchor 5, but reduced by 1 for second-person voice ('Use when you need to set up').	4 / 5
Completeness	Explicitly answers both 'what' (set up Gatling performance testing for a Java Maven project including the listed actions) and 'when' ('Use when you need to...' plus concrete trigger phrases), matching the anchor 5 example.	5 / 5
Trigger Term Quality	Provides natural trigger phrases users would say ('Add Gatling performance testing; Apply Gatling performance testing; Create a Gatling simulation; Add Gatling support; Review Gatling performance test assertions and feeders') — good coverage, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Gatling performance testing for Java Maven projects) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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/152-java-performance-gatling/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours 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.