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. Part of cursor-rules-java project
85
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 description that thoroughly enumerates specific Maven plugins and categories, provides clear trigger conditions with a 'Use when' clause, and includes explicit example trigger phrases. The only minor weakness is the use of second person ('you need', 'you actually need') which slightly deviates from the preferred third-person voice, and the description is somewhat verbose, but the detail serves the purpose of disambiguation well.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: 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 with a consultative modular approach) and 'when' ('Use when you need to add or configure Maven plugins' plus explicit trigger examples 'Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml'). | 3 / 3 |
Trigger Term Quality | Includes highly natural keywords users would say: 'Maven plugins', 'pom.xml', plus specific plugin names like 'jacoco', 'spotbugs', 'OWASP', 'Jib', 'JMH', 'Spotless'. The explicit trigger phrases 'Add Maven plugins in pom.xml' and 'Improve Maven plugins in pom.xml' match natural user requests well. | 3 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to Maven plugin configuration in pom.xml with specific plugin names listed. Unlikely to conflict with other skills due to the narrow focus on Maven build configuration and the extensive enumeration of specific tools. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid interactive workflow structure with good safety constraints and validation checkpoints, making it reliable for destructive/additive operations on pom.xml. However, it lacks any concrete XML examples or copy-paste ready configurations in the main skill body, deferring everything to a reference file. The coverage list adds bulk without actionable value and could be trimmed or moved to the reference.
Suggestions
Add at least one concrete XML snippet example (e.g., a simple plugin addition) directly in the SKILL.md to improve actionability without requiring the reference file for basic cases.
Move the 'What is covered' plugin/profile listing into the reference file or condense it to a single line summary to improve conciseness.
Include a brief example of the 'question-driven flow' interaction pattern so Claude knows what questions to ask the user during step 3.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably concise but includes some unnecessary content like the full list of covered plugins/profiles which could be in the reference file, and the 'What is covered' section adds bulk without actionable value. The constraints and workflow sections are fairly tight though. | 2 / 3 |
Actionability | The skill provides a clear workflow sequence and specific commands (./mvnw validate), but lacks any concrete XML examples, code snippets, or copy-paste ready configuration. All actual implementation details are deferred to the reference file, making the skill itself more of a process description than executable guidance. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with 5 explicit steps, includes a validation checkpoint upfront (step 1), has a clear stop condition if validation fails, and follows a logical progression from analysis to implementation to summary. The feedback loop for validation failure is explicitly stated in the constraints. | 3 / 3 |
Progressive Disclosure | The skill correctly references a single external file (references/112-java-maven-plugins.md) for detailed configurations, which is good one-level-deep disclosure. However, since no bundle files were provided, we cannot verify the reference exists or is well-structured. The 'What is covered' list is inline content that could arguably be in the reference, and the skill itself is somewhat thin without the reference being available to evaluate. | 2 / 3 |
Total | 9 / 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
762cb86
- 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.