111-java-maven-dependencies
Use when you need to add or evaluate Maven dependencies that improve code quality — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), or architecture testing (ArchUnit) — and want a consultative, question-driven approach that adds only what you actually need. Part of the skills-for-java project
94
92%
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 skill description that excels across all dimensions. It clearly specifies what the skill does (add/evaluate Maven dependencies for specific code quality tools), when to use it (explicit 'Use when' clause), and includes numerous natural trigger terms that developers would actually use. The specific tool names and the mention of a 'consultative, question-driven approach' make it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: 'add or evaluate Maven dependencies', 'nullness annotations (JSpecify)', 'static analysis (Error Prone + NullAway)', 'functional programming (VAVR)', 'architecture testing (ArchUnit)'. Very specific about the domain and capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('add or evaluate Maven dependencies that improve code quality' with specific tools listed) AND when ('Use when you need to...' with explicit trigger guidance). The 'Use when' clause is present and explicit. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Maven dependencies', 'code quality', 'nullness annotations', 'JSpecify', 'static analysis', 'Error Prone', 'NullAway', 'VAVR', 'ArchUnit', 'functional programming', 'architecture testing'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche: specifically Maven dependencies for code quality tools, with named libraries (JSpecify, Error Prone, NullAway, VAVR, ArchUnit). The 'consultative, question-driven approach' and 'skills-for-java project' context further distinguish it from generic dependency management skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that excels at conciseness and progressive disclosure, providing a clear consultative workflow with proper validation checkpoints. The main weakness is that actionability relies heavily on the referenced file for actual implementation details, leaving the main skill without executable examples of the dependency additions themselves.
Suggestions
Add at least one concrete XML snippet example showing how a dependency block looks when added (e.g., JSpecify dependency XML)
Include a brief example of the expected question-response flow to make the interactive nature more concrete
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, listing only what's covered without explaining what Maven, JSpecify, or other tools are. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete commands (`./mvnw validate`) and clear constraints, but lacks executable code examples for actually adding the dependencies. The actual implementation details are deferred to a reference file. | 2 / 3 |
Workflow Clarity | Clear sequence with explicit validation checkpoint (MANDATORY validate step), safety gate (stop if validation fails), and defined question order (JSpecify → Enhanced Compiler Analysis → VAVR → ArchUnit). Includes feedback loop for error recovery. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview in the main file and a single, clearly signaled reference file for detailed guidance. One-level-deep reference with clear navigation. | 3 / 3 |
Total | 11 / 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
7772a1b
- 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.