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. Part of the skills-for-java project
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/112-java-maven-plugins/SKILL.mdQuality
Discovery
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.
This is a strong skill description that excels across all dimensions. It opens with an explicit 'Use when' trigger, enumerates a comprehensive list of specific Maven plugins and categories, and uses natural terminology that Java developers would search for. The only minor weakness is the trailing 'Part of the skills-for-java project' which adds no selection value, and the description is somewhat long, but the content is substantive rather than padded.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: Maven plugins, 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). Very detailed enumeration of capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (add/configure Maven plugins across many categories) and 'when' (opens with 'Use when you need to add or configure Maven plugins in your pom.xml'). The explicit 'Use when...' clause is present and well-defined. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Maven plugins', 'pom.xml', specific tool names like 'jacoco', 'spotbugs', 'pmd', 'OWASP', 'Spotless', 'Jib', 'JMH', 'surefire', 'failsafe', 'enforcer', plus domain terms like 'security scanning', 'code formatting', 'benchmarking'. These are exactly the terms a Java developer would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — focuses specifically on Maven plugin configuration in pom.xml with a comprehensive list of specific tools. The niche is clear (Java/Maven build configuration) and unlikely to conflict with other skills due to the specificity of the tooling mentioned. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a thin overview/entry point that delegates nearly all actionable content to a reference file. While the progressive disclosure and safety constraints are well-structured, the skill itself lacks any concrete executable guidance—no XML snippets, no example plugin configurations, no step-by-step workflow beyond 'validate first.' It would benefit significantly from at least one concrete example and a clearer enumeration of the interactive workflow steps.
Suggestions
Add at least one concrete XML snippet showing a plugin configuration example (e.g., Maven Enforcer or Surefire) so the skill has some actionable content on its own.
Enumerate the full step-by-step interactive workflow (e.g., Step 1: Analyze existing config, Step 2: Present options, Step 3: User selects, Step 4: Apply changes, Step 5: Validate) rather than just referencing 'Step 1' and deferring the rest.
Include a brief example of the 'question-driven process' showing what questions Claude should ask and how to handle responses, making the interactive nature concrete rather than abstract.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably concise but includes some unnecessary elements like the full enumerated list of plugins and profiles that could be more compact. The 'What is covered' section is essentially a table of contents that adds moderate value but takes up space. | 2 / 3 |
Actionability | The skill provides no concrete code, XML snippets, or executable commands beyond mentioning `./mvnw validate`. All actual configuration guidance is deferred to the reference file. There are no examples of plugin configurations, no XML templates, and no copy-paste ready content. | 1 / 3 |
Workflow Clarity | There is a clear validation checkpoint (run `./mvnw validate` before changes, stop if it fails) and a stated sequence (Step 1: analyze existing config first). However, the full multi-step workflow is not spelled out in this file—it's deferred to the reference. The validation step is explicit which is good, but the overall process is incomplete here. | 2 / 3 |
Progressive Disclosure | The skill serves as a clear overview with a well-signaled one-level-deep reference to the detailed guide. The structure is clean with constraints, when-to-use, and a single reference link. This is appropriate progressive disclosure for a skill that delegates detailed configurations to a reference file. | 3 / 3 |
Total | 8 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
9ec21dd
- 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.