112-java-maven-plugins

Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml; Configure Maven quality plugins in pom.xml; Add Maven build lifecycle plugins for Java verification; Review Maven plugin versions and executions. Part of Plinth Toolkit

Quality

88%

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

Quality

Content

77%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.

The skill body is well-structured: an interactive question-driven workflow with strong validation gates and excellent progressive disclosure via verified one-level-deep references. Its main weakness is conciseness — the plugin catalogue and option lists recur in multiple places and could be consolidated.

Suggestions

Consolidate the plugin/profile catalogue so it appears once (e.g., in Question 3) rather than repeated in 'What is covered', the question options, and the reference-mapping list.

Tighten the question scaffolding by grouping long option lists or linking to a single canonical list, reducing token weight in the SKILL.md body.

Consider moving the full reference-mapping block into a compact table to make the conditional navigation scannable without repeating each plugin name twice.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but the plugin catalogue is repeated across 'What is covered', Question 3 options, and the reference-mapping list, and the full enumerated option set for every question adds length that could be tightened. It is mostly efficient but carries notable redundancy.	3 / 5
Actionability	Concrete commands appear ('./mvnw validate', 'mvn wrapper:wrapper'), file paths are specific, and each selected plugin maps to an exact reference file to read. The bulk of executable config is correctly delegated to the reference files, leaving the body with mostly-executable navigation and validation guidance and only minor gaps.	4 / 5
Workflow Clarity	A clear 6-step sequence includes an explicit validation checkpoint ('Run ./mvnw validate... stop if validation fails'), a Maven-wrapper gate, and a feedback loop (stop and ask the user to fix issues before proceeding) for pom.xml modifications — fully meeting the destructive/batch validation bar.	5 / 5
Progressive Disclosure	SKILL.md is a lean overview plus question flow, with 19 one-level-deep reference files (all verified present) clearly signaled by conditional mapping ('If X is selected, read references/Y.md'); no nested references and easy navigation.	5 / 5
	Total	17 / 20 Passed

Description

100%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.

The description is exemplary: it states concrete capabilities, gives multiple explicit natural-language triggers, and clearly answers both what the skill does and when to use it, all in a distinct niche. No weaknesses to address.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete tools and actions — 'enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd', 'OWASP', 'Spotless', 'Jib', 'JMH' — giving comprehensive coverage of specific capabilities rather than vague language.	5 / 5
Completeness	Both 'what' ('add or configure Maven plugins in your pom.xml — including quality tools...') and 'when' ('Use when you need to...', 'This should trigger for requests such as...') are explicitly and concretely answered with trigger phrases.	5 / 5
Trigger Term Quality	It provides five explicit natural trigger phrases users would say ('Add Maven plugins in pom.xml', 'Improve Maven plugins in pom.xml', 'Configure Maven quality plugins in pom.xml', 'Add Maven build lifecycle plugins for Java verification', 'Review Maven plugin versions and executions') plus domain keywords, giving comprehensive coverage.	5 / 5
Distinctiveness Conflict Risk	The niche is clearly scoped to Maven pom.xml plugin configuration with distinct triggers, making overlap with other skills minimal.	5 / 5
	Total	20 / 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/112-java-maven-plugins/SKILL.md
Commit: 05bf9d1

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