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. This should trigger for requests such as Add Maven dependencies; Add JSpecify nullness dependencies; Add Error Prone NullAway dependencies; Add VAVR functional dependencies; Add ArchUnit architecture testing dependencies. 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 skill description that clearly identifies its niche (Maven dependencies for code quality tools), lists specific libraries and capabilities, and provides explicit trigger guidance with example requests. The description effectively combines a 'Use when' clause with enumerated trigger phrases, making it easy for Claude to select this skill appropriately. Minor note: it uses second-person 'you' in the opening, but the rubric penalizes first/second person on specificity, though the rest of the description is functional and well-structured.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), and describes the consultative approach. Very specific about what libraries and capabilities are covered. | 3 / 3 |
Completeness | Clearly answers both 'what' (add/evaluate Maven dependencies for code quality tools with a consultative approach) and 'when' (explicit 'Use when' clause at the start, plus a 'This should trigger for' section listing specific request patterns). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'Add Maven dependencies', 'JSpecify', 'Error Prone', 'NullAway', 'VAVR', 'ArchUnit', 'nullness annotations', 'static analysis', 'functional programming', 'architecture testing'. These are terms developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche of Maven dependency management for code quality libraries (JSpecify, Error Prone, NullAway, VAVR, ArchUnit). The combination of specific library names and Maven context makes it very unlikely to conflict with other skills. | 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 has a well-structured interactive workflow with clear validation checkpoints and a defined question sequence, which is its strongest aspect. However, it defers nearly all concrete implementation details to a reference file that wasn't provided for verification, and the body contains some redundancy between the description, 'When to use' section, and 'What is covered' section. Adding at least one inline example dependency snippet would significantly improve actionability.
Suggestions
Add at least one concrete inline example of a dependency XML block (e.g., JSpecify dependency with provided scope) so the skill body is actionable even without the reference file.
Remove or consolidate the 'When to use this skill' section since it duplicates the skill description/trigger information and adds no new guidance.
Include the reference file in the bundle or inline the key question templates so the skill is self-contained enough to be evaluated and used effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary repetition — the 'When to use this skill' section duplicates the description, and the constraints section restates things that could be tighter. The 'What is covered' section adds marginal value given the workflow already covers it. | 2 / 3 |
Actionability | Provides concrete commands (`./mvnw validate`) and a clear workflow sequence, but all actual implementation details (dependency XML snippets, question templates, exact configurations) are deferred to the reference file. The skill itself contains no executable code or copy-paste-ready dependency blocks. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with an explicit validation gate (step 1: validate, stop if fails), a defined question order (JSpecify → Enhanced Compiler Analysis → VAVR → ArchUnit), implementation step, and follow-up reporting. The feedback loop for validation failure is explicit — stop and ask user to fix before proceeding. | 3 / 3 |
Progressive Disclosure | References a single detailed file (`references/111-java-maven-dependencies.md`) which is good progressive disclosure structure, but since no bundle files were provided, we cannot verify the reference exists or is well-structured. The skill body itself could benefit from at least a minimal inline example (e.g., one dependency XML snippet) rather than deferring everything to the reference. | 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.